On Mon, 11 Nov 2002 13:47:53 +0900, "Stephen J. Turnbull" said:
Yes, but explaining what is truly happening is actually quite hard.
I've never seen any of the things you claim are "common" (and I have
seen the panic message on a number of occasions, both personally and
on xemacs-beta).
I manage to get the "can't create a binary" error out of one package or
another's configure script at least once every few months, and I've had
things not find shared libs because ldconfig hasn't been rerun, but I've
never managed to get that error out of configure for the listed reason.. ;)
I see variants of the 'disk full' and 'permissions' errors on the gtk
lists
on a fairly regular basis too, so it isn't just me being an idiot, others
do it too. ;)
------------------------------------------------------------------------
*** PANIC *** configure doesn't know how to build working executables!
*** This is most commonly due to an unforeseen environment, causing
*** configure to incorrectly compute the sequence of libraries to link.
*** Please examine the tail of config.log for runtime errors.
*** Pay special attention to the -l flags, and perhaps -I and -L.
*** Often adding or removing explicit options in the configure
*** invocation can work around this kind of problem. If so, please
*** report it as a bug to xemacs-beta(a)xemacs.org.
*** Other possible causes are inability to write to the file system
*** (bogus permissions or disk full) or a misconfiguration of the dynamic
*** linker (check /etc/ld.conf and rerun ldconfig if necessary).
------------------------------------------------------------------------
OK... I think that covers all my issues (actually, I think it covers almost
all the ways I can think of to bomb out the configure run, except for things
that are so severe that building XEmacs is the least of their worries ;)
/Valdis