On 15/12/11 22:55, Martin Costabel wrote: > On 15/12/11 22:32, Peter O'Gorman wrote: > [] >> As far as I can see libtool shouldn't be using a lockfile at all. > [] >> /sw/bin/glibtool --config | grep compiler_c_o >> >> should be yes, if not libtool will use lock files. > > It says "yes" here. In Peter D's original post, you can see that the > last successful compiler line before the "Waiting for" hang uses indeed > -c and -o. I'll send you the file in a seperate message.
There are two instances of this "Waiting for" message in /sw/bin/glibtool. It is the second one that is triggered, and it depends on the variable $lock_old_archive_extraction, which is "yes" in this case. /usr/bin/glibtool from libtool-1.5.22 does not have this second instance. -- Martin ------------------------------------------------------------------------------ 10 Tips for Better Server Consolidation Server virtualization is being driven by many needs. But none more important than the need to reduce IT complexity while improving strategic productivity. Learn More! http://www.accelacomm.com/jaw/sdnl/114/51507609/ _______________________________________________ Fink-users mailing list Fink-users@lists.sourceforge.net List archive: http://news.gmane.org/gmane.os.macosx.fink.user Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-users
