Here's a bit more info:
* Ralf Wildenhues wrote on Fri, Aug 26, 2005 at 05:27:44PM CEST:
> * Peter Kjellström wrote on Fri, Aug 26, 2005 at 05:21:27PM CEST:
> >
> > I just checked out 7046 and my configure hangs at:
> > checking for libtool-supplied linker flags...
> >
> > ps -ef f gives me:
> >
> > ...configure
> > \_ /bin/sh /home/cap/openmpi/ompi-trunk/vbuild/opal/libltdl/libtool
> > --mode=compile icc -O3 -DNDEBUG foo.c -c -o foo.o
> > \_ sleep 2
> >
> > is it just currently broken (and if so, how do I check out an older
> > revision) or did I fumble the spell?
>
> Weird. Libtool thought icc does not understand `-c -o'?
>
> Can you search and post the respective output from config.log?
Just go to $top_builddir and execute these:
$ find . -name config.log | xargs sed -n '/ supports -c -o
/{N;N;N;N;N;N;N;N;p;}'
$ ./libtool --version
Libtool version previous to 1.5.16 had a bug in the macro to detect
this; it was often wrong before. Now it should be pretty bogus.
Libtool still has a bug that might lead to the hang you describe
when both the macro detects that the compiler (seemingly or not)
does not understand "-c -o" and the source tree and the build tree
live on different mount points, so that a hard link fails.
It's on our TODO list, but as we thought it to be a very rare bug,
it had rather low priority so far.
If you have use Libtool >= 1.5.16 and still experience this issue,
one workaround is to have the build tree below the same mount point.
But I'd like to see the failure of the macro: icc understands "-c -o",
and we should be able to detect that.
Cheers,
Ralf
