gmake and ports issue

Jeroen Ruigrok/asmodai asmodai at wxs.nl
Fri Sep 17 14:19:20 PDT 2004


Just to warn people,

you might see some ports go into an infinite loop.

I can reliably repeat this with building subversion-python, which needs
automake18, which needs autoconf259.

autoconf259 goes haywire at one point and does the configure step ad
infinitum.

Problem at hand is that gmake 3.80_2 for some reason I have not unraveled
sends a SIGCHLD but then decides to restart make, which is helpful to
reconsider the whole autoconf/automake file mess in the directory and thinks
it needs to be helpful to restart aclocal and such to regenerate the files
because it deems them out of date.  Yay!

Gah, of course, now I cannot reproduce it. :(
Oh wait, another problem now, it is not building it, but it is registering
its installation.  So it configures, creates the Makefiles, supposedly
builds it, but doesn't, probably triggers a SIGCHLD again, and then thinks
it can install.

On a related note, the bsd.port.mk line 6: warning "/usr/bin/relpath" line
also showed me that the make clean command doesn't work as it should
anymore, I miss a bunch of dependencies.  Also up for investigation.

Too tired to chase them up now.

-- 
Jeroen Ruigrok van der Werven <asmodai(at)wxs.nl> / asmodai / kita no mono
Free Tibet! http://www.savetibet.org/ | http://ashemedai.deviantart.com/
http://www.tendra.org/   | http://www.in-nomine.org/
Cogito, ergo sum...





More information about the Bugs mailing list