It works for me, too. Actually, if I hit Ctrl-C and wait a while, the system recovers. I have no time now to investigate who is to blame for this,
- autoconf
- libtool
- db42
- fort77
or if it's a conspiracy between all of these, but if you
- either remove fort77
- or install g77 or another "real" fortran compiler,
the problem will go away.
I suspect this problem will appear with other autoconf-generated configure scripts, too.
The problem is quite simple, if CC is an exported env var, and a package uses libtool-1.5.x, then fort77 will fork bomb. It checks if CC is set and calls $CC if so. libtool sets CC to the name of the compiler when running these tests, so CC is fort77, so fort77 calls fort77 to compile, which then calls fort77 until you run out of processes.
I just fixed the db42 package in 10.2-gcc3.3, I forgot about it when I fixed the one in 10.3, the fix for the package is simple:
env F77=no ./configure %c
(because db42 does not actually use a fortran compiler anyway).
CC'ing this to -devel, in case some package maintainers do not know about this issue. Basically, if the package you maintain uses libtool-1.5.x and the user has fort77 installed, they will get a "system hang". This could probably be fixed in fink's fort77 package. Will look into that (sometime).
Peter -- Peter O'Gorman - http://www.pogma.com
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
