Hi Juha, * Juha Jäykkä wrote on Fri, Feb 03, 2006 at 08:12:12AM CET: > > Can you definitely rule out that it does not happen when the source is > > not on AFS (but otherwise the same system)? > > I can. I built 0.7.1-1 on both AFS and xfs, AFS fails, xfs works; then I > tried 0.7.1-3 on AFS, still fails. (Note that this is a sarge system and I > am building sid's sources, but I doubt that has any effect here.)
So, with xfs, is the `libtool' script still on a different file system than the current build directory? If no: this is definitely not a libtool issue. So > > Could you post a command line > > libtool --debug --mode=... ... > > The command is > > /bin/sh ../libtool --debug --mode=link gcc -Wall -Wmissing-prototypes ^^^^^^^^^^ this definitely rules out the lock issue. > -Wpointer-arith -Wbad-function-cast -Wmissing-declarations > -Wnested-externs -g -O2 -o bits bits.o -lresolv -pthread -lpthread &> > libtool.debug > > which shows the failure, including all output, for me please? Also > > nm object.o > > of the object that fails to link. > > I should have put this already in the first report, since this is really > fishy: > > ~> nm bits.o > 0000000000000000 r *snip* Time to get someone with knowledge about the toolchain into play. Sorry, I don't think I can help here, except for really wild guesses: play around with compiler and assembler versions to find out which tool may be responsible; maybe due to a latent file system failure it finds a wrong file? Cheers, Ralf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]