Re: Infinite 'make' loops while building ports
On Thu, May 23, 2002 at 12:18:59PM +, J. Mallett wrote: > On Thu, May 23, 2002 at 03:46:01AM -0700, Shizuka Kudo wrote: > > You're right. The only reason it didn't show up > > several days before is that v 1.58 added the real path > > to MAKEFILE as mentioned in the commit log: > > Try with the current make(1) sources. Doesn't this push the problem back into obscurity without fixing anything? I mean, the problem is simply that MAKEFILE is defined and reserved by make(1) and its use by the ports collection conflicts and breaks ports. -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Infinite 'make' loops while building ports
On Thursday 23 May 2002 07:18 am, J. Mallett wrote: > On Thu, May 23, 2002 at 03:46:01AM -0700, Shizuka Kudo wrote: > > You're right. The only reason it didn't show up > > several days before is that v 1.58 added the real path > > to MAKEFILE as mentioned in the commit log: > > Try with the current make(1) sources. Works great for me. Thanks. Jay To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Infinite 'make' loops while building ports
On Thu, May 23, 2002 at 03:46:01AM -0700, Shizuka Kudo wrote: > You're right. The only reason it didn't show up > several days before is that v 1.58 added the real path > to MAKEFILE as mentioned in the commit log: Try with the current make(1) sources. -- [EMAIL PROTECTED] | C, MIPS, POSIX, UNIX, BSD, IRC Geek. http://www.FreeBSD.org | The Power to Serve Vote for me for FreeBSD core or the cute little bunny gets it. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Infinite 'make' loops while building ports
On Thu, 23 May 2002, Marcel Moolenaar wrote: > On Thu, May 23, 2002 at 02:33:56AM -0700, Shizuka Kudo wrote: > > > > It seems /usr/bin/make set the environment variable > > MAKEFILE to the Makefile it uses. So when you type > > make build or install, MAKEFILE is pointed to the > > port's Makefile. Workaround for me at this moment is > > to run "make build MAKEFILE=Makefile" so that > > bsd.ports.mk use the correct Makefile in WRKSRC. > > > > Is the behaviour in /usr/bin/make changed recently? > > No. This is old behaviour and I filed a PR for it many moons ago. > I have replaced all uses of MAKEFILE with MAKE_FILE in all the > makefiles that set it (and changed bsd.ports.mk as well of course) > The problem is more visible if you set WRKDIROREFIX. http://groups.google.com/groups?hl=en&lr=&threadm=3CDC0724.C9ACC64C_FreeBSD.org%40ns.sol.net&rnum=4&prev=/groups%3Fq%3Dfreebsd%2Binfinite%2Bmake%2Bloop%26hl%3Den%26lr%3D%26scoring%3Dd%26selm%3D3CDC0724.C9ACC64C_FreeBSD.org%2540ns.sol.net%26rnum%3D4 says that this is a problem in textproc/expat2 and indeed if I remove the Makefile there and do a make clean in /usr/ports it chews through the ports with the occasional error when it hits an expat dependency. Above thread states that this should be fixed by expat2 Makefile rev. 1.14. That Makefile however doesn't get updated on cvsup. If I delete it no version of it gets checked out. My Makefile is rev. 1.13 bis bald, Rolf To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Infinite 'make' loops while building ports
--- Marcel Moolenaar <[EMAIL PROTECTED]> wrote: > On Thu, May 23, 2002 at 02:33:56AM -0700, Shizuka > Kudo wrote: > > > > It seems /usr/bin/make set the environment > variable > > MAKEFILE to the Makefile it uses. So when you type > > make build or install, MAKEFILE is pointed to the > > port's Makefile. Workaround for me at this moment > is > > to run "make build MAKEFILE=Makefile" so that > > bsd.ports.mk use the correct Makefile in WRKSRC. > > > > Is the behaviour in /usr/bin/make changed > recently? > > No. This is old behaviour and I filed a PR for it > many moons ago. > I have replaced all uses of MAKEFILE with MAKE_FILE > in all the > makefiles that set it (and changed bsd.ports.mk as > well of course) > The problem is more visible if you set WRKDIROREFIX. > > -- > Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] You're right. The only reason it didn't show up several days before is that v 1.58 added the real path to MAKEFILE as mentioned in the commit log: Make ReadMakefile() operate using the realpath(3) name for the file handed to it, which means that relative paths will be expanded to absolute paths, and filenames without a path will end up with their absolute path included as well. This aids tremendously in debugging a build using our make(1) with multiple Makefile's, such as when there is a syntax error in a file in a sub-directory as per . Normally we'd end up with just "Makefile" known about the Makefile in question, which means that an error would be useless for someone trying to debug their build system, now we end up with a complete real pathname for the Makefile. So mostly this is useful in a debugging context, but possibly others too (I haven't thought of them yet, but they probably are more useful if you make Dir_FindFile use realpath(3), but that's another story). __ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Infinite 'make' loops while building ports
On Thu, May 23, 2002 at 02:33:56AM -0700, Shizuka Kudo wrote: > > It seems /usr/bin/make set the environment variable > MAKEFILE to the Makefile it uses. So when you type > make build or install, MAKEFILE is pointed to the > port's Makefile. Workaround for me at this moment is > to run "make build MAKEFILE=Makefile" so that > bsd.ports.mk use the correct Makefile in WRKSRC. > > Is the behaviour in /usr/bin/make changed recently? No. This is old behaviour and I filed a PR for it many moons ago. I have replaced all uses of MAKEFILE with MAKE_FILE in all the makefiles that set it (and changed bsd.ports.mk as well of course) The problem is more visible if you set WRKDIROREFIX. -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Infinite 'make' loops while building ports
--- Jay <[EMAIL PROTECTED]> wrote: > I should also have mentioned that other ports > install normally. I just > finished installing unzip. > > Jay > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of > the message It seems /usr/bin/make set the environment variable MAKEFILE to the Makefile it uses. So when you type make build or install, MAKEFILE is pointed to the port's Makefile. Workaround for me at this moment is to run "make build MAKEFILE=Makefile" so that bsd.ports.mk use the correct Makefile in WRKSRC. Is the behaviour in /usr/bin/make changed recently? __ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Infinite 'make' loops while building ports
I should also have mentioned that other ports install normally. I just finished installing unzip. Jay On Thursday 23 May 2002 01:28 am, Jay wrote: > I've just seen the same problem with libnet. > > The machine in question was installed via a DP1 CD yesterday. I updated it > about 1PM today to the latest -CURRENT. > > When I saw the infinite 'make' loop (about 15...30...60 minutes ago), I > deleted /usr/ports on the looping machine; resynced my CVS tree on my > server, cvsup'd to get /usr/ports back; and attempted to 'make build' > libnet. Same thing -- the infinite 'no MD5 sum' loop. > > Then I deleted the ports directory out of my CVS tree and resynced it. > While I was doing that, I also re-deleted the /usr/ports dir on the looping > machine. After resyncing /usr/ports with my fresh (finished updating 5 > minutes ago) CVS tree, I still see the same problem. > > Jay > > On Wed, May 22, 2002 at 06:21:22PM -0700, Scott Reese wrote: > > Hello, > >=20 > > I just upgraded my 4-STABLE machine to -CURRENT via source. Everything > > seemed to go smoothly and things are running fine, EXCEPT when I try to > > build *any* of the ports in the ports collection. Every time I run > > 'make' it gets stuck in an infinite loop and doesn't build the port.=20 > > Some examples: > > Are you sure you have an up-to-date ports collection? This bug was > fixed a few weeks ago. > > Kris > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Infinite 'make' loops while building ports
I've just seen the same problem with libnet. The machine in question was installed via a DP1 CD yesterday. I updated it about 1PM today to the latest -CURRENT. When I saw the infinite 'make' loop (about 15...30...60 minutes ago), I deleted /usr/ports on the looping machine; resynced my CVS tree on my server, cvsup'd to get /usr/ports back; and attempted to 'make build' libnet. Same thing -- the infinite 'no MD5 sum' loop. Then I deleted the ports directory out of my CVS tree and resynced it. While I was doing that, I also re-deleted the /usr/ports dir on the looping machine. After resyncing /usr/ports with my fresh (finished updating 5 minutes ago) CVS tree, I still see the same problem. Jay On Wed, May 22, 2002 at 06:21:22PM -0700, Scott Reese wrote: > Hello, >=20 > I just upgraded my 4-STABLE machine to -CURRENT via source. Everything > seemed to go smoothly and things are running fine, EXCEPT when I try to > build *any* of the ports in the ports collection. Every time I run > 'make' it gets stuck in an infinite loop and doesn't build the port.=20 > Some examples: Are you sure you have an up-to-date ports collection? This bug was fixed a few weeks ago. Kris To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Infinite 'make' loops while building ports
On Wed, 2002-05-22 at 18:27, Kris Kennaway wrote: > > > I just upgraded my 4-STABLE machine to -CURRENT via source. Everything > > seemed to go smoothly and things are running fine, EXCEPT when I try to > > build *any* of the ports in the ports collection. Every time I run > > 'make' it gets stuck in an infinite loop and doesn't build the port. > > Some examples: > > Are you sure you have an up-to-date ports collection? This bug was > fixed a few weeks ago. Yes, I cvsup-ed the ports collection just a few minutes prior to my first email. Should I blow away the whole ports tree and re-grab them? The relevant lines in my cvsup file are as follows: *default host=cvsup14.FreeBSD.org *default base=/usr/local/etc/cvsup *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix ports-all To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Infinite 'make' loops while building ports
On Wed, May 22, 2002 at 06:21:22PM -0700, Scott Reese wrote: > Hello, > > I just upgraded my 4-STABLE machine to -CURRENT via source. Everything > seemed to go smoothly and things are running fine, EXCEPT when I try to > build *any* of the ports in the ports collection. Every time I run > 'make' it gets stuck in an infinite loop and doesn't build the port. > Some examples: Are you sure you have an up-to-date ports collection? This bug was fixed a few weeks ago. Kris msg38705/pgp0.pgp Description: PGP signature
Infinite 'make' loops while building ports
Hello, I just upgraded my 4-STABLE machine to -CURRENT via source. Everything seemed to go smoothly and things are running fine, EXCEPT when I try to build *any* of the ports in the ports collection. Every time I run 'make' it gets stuck in an infinite loop and doesn't build the port. Some examples: sysutils/portupgrade: borges[164] # make ===> Extracting for portupgrade-20020429 >> Checksum OK for pkgtools-20020429.tar.bz2. ===> portupgrade-20020429 depends on file: /usr/local/bin/ruby - found ===> Patching for portupgrade-20020429 ===> Configuring for portupgrade-20020429 ===> Building for portupgrade-20020429 ===> Extracting for portupgrade-20020429 >> No MD5 checksum file. ===> portupgrade-20020429 depends on file: /usr/local/bin/ruby - found ===> Patching for portupgrade-20020429 ===> Configuring for portupgrade-20020429 ===> Building for portupgrade-20020429 ===> Extracting for portupgrade-20020429 >> No MD5 checksum file. ...[ad infinitum] devel/autoconf213: borges[167] # make ===> Extracting for autoconf213-2.13.000227_1 >> Checksum OK for autoconf-000227.tar.bz2. ===> autoconf213-2.13.000227_1 depends on executable: gm4 - found ===> Patching for autoconf213-2.13.000227_1 ===> Applying FreeBSD patches for autoconf213-2.13.000227_1 ===> Configuring for autoconf213-2.13.000227_1 creating cache ./config.cache checking for gm4... /usr/local/bin/gm4 checking for mawk... no checking for gawk... gawk checking for perl... /usr/bin/perl checking for a BSD compatible install... /usr/bin/install -c -o root -g wheel updating cache ./config.cache creating ./config.status creating Makefile creating testsuite/Makefile ===> Building for autoconf213-2.13.000227_1 ===> Extracting for autoconf213-2.13.000227_1 >> No MD5 checksum file. ===> autoconf213-2.13.000227_1 depends on executable: gm4 - found ===> Patching for autoconf213-2.13.000227_1 ===> Configuring for autoconf213-2.13.000227_1 creating cache ./config.cache checking for gm4... /usr/local/bin/gm4 checking for mawk... no checking for gawk... gawk checking for perl... /usr/bin/perl checking for a BSD compatible install... /usr/bin/install -c -o root -g wheel updating cache ./config.cache creating ./config.status creating Makefile creating testsuite/Makefile ===> Building for autoconf213-2.13.000227_1 ===> Extracting for autoconf213-2.13.000227_1 >> No MD5 checksum file. ...[also ad infinitum until I hit ^C] This is pretty much the case with any port I try to build. I'm sure it's due to some silly thing I missed in the upgrade process somewhere, but after hours of beating my head against a wall, I can't seem to come up with any answers. Anyone else seen this or know what to do about it? Searching Google and the archives yields nothing of any use. TIA, Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
