From: Alan W. I. <ir...@be...> - 2002-12-27 08:42:02
|
On Fri, 27 Dec 2002, Maurice LeBrun wrote: > I'm getting this waaay too often: > > gmake[1]: *** No rule to make target `COPYING', needed by `all-am'. Stop. > > I just got it again, after a clean checkout, in the shared lib build phase. > Could we just take it out? To be stopped short of a build because of this > after messing with this stuff nearly all day is driving me *nuts*. Sure. I meant to do this anyhow as per discussion. Remove it from doc_DATA in the top-level Makefile.am. I am a little surprised you don't have COPYING though. ./bootstrap.sh creates it on my machine if there is not a file by that name in the top-level directory. Alan email: ir...@be... phone: 250-727-2902 FAX: 250-721-7715 snail-mail: Dr. Alan W. Irwin Department of Physics and Astronomy, University of Victoria, P.O. Box 3055, Victoria, British Columbia, Canada, V8W 3P6 __________________________ Linux-powered astrophysics __________________________ |
From: Maurice L. <mj...@ga...> - 2002-12-27 19:37:42
|
Alan W. Irwin writes: > On Fri, 27 Dec 2002, Maurice LeBrun wrote: > > > I'm getting this waaay too often: > > > > gmake[1]: *** No rule to make target `COPYING', needed by `all-am'. Stop. > > > > I just got it again, after a clean checkout, in the shared lib build phase. > > Could we just take it out? To be stopped short of a build because of this > > after messing with this stuff nearly all day is driving me *nuts*. > > Sure. I meant to do this anyhow as per discussion. Remove it from doc_DATA > in the top-level Makefile.am. > > I am a little surprised you don't have COPYING though. ./bootstrap.sh > creates it on my machine if there is not a file by that name in the > top-level directory. It didn't, or in the build process got blown away somehow. I know it sounds farfetched but in the clear light of day :) I'm looking at my command line history and everything checks out but COPYING is missing (this is on IRIX). Matter of fact, I've been suffering through lots of niggling little problems that I haven't been documenting just because I've already spent more time on this than intended. Lots of problems in the approach you mentioned of doing ./bootstrap.sh on one machine and then tar'ing up the distribution and trying to build it on another machine. I suspect other people will run up against this too so we'll get more & detailed error reports. To get rid of all those problems I just put the latest auto{conf,make},libtools on all those platforms. Anyway back to it. I will try to document detailed failure scenarios if I have the time. -- Maurice LeBrun mj...@ga... Research Organization for Information Science and Technology of Japan (RIST) |
From: Maurice L. <mj...@ga...> - 2002-12-27 20:02:58
|
Maurice LeBrun writes: > Alan W. Irwin writes: > > I am a little surprised you don't have COPYING though. ./bootstrap.sh > > creates it on my machine if there is not a file by that name in the > > top-level directory. > > It didn't, or in the build process got blown away somehow. I know it sounds > farfetched but in the clear light of day :) I'm looking at my command line > history and everything checks out but COPYING is missing (this is on IRIX). Using a fresh checkout, bootstrap.sh does not create a top level COPYING in my configuration on either of Linux, OSF1, or IRIX. -- Maurice LeBrun mj...@ga... Research Organization for Information Science and Technology of Japan (RIST) |