bug-libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libtool 2.2.10] testsuite 24 102 failed


From: Ralf Wildenhues
Subject: Re: [libtool 2.2.10] testsuite 24 102 failed
Date: Fri, 24 Sep 2010 07:03:39 +0200
User-agent: Mutt/1.5.20 (2010-08-04)

[ reordering output a bit ]

Hello Gustavo,

* Gustavo CM wrote on Fri, Sep 24, 2010 at 05:08:15AM CEST:
> I was compiling libtool at Archlinux with 'srcpac -Sb libtool' when it
> happened: some tests failed and I got the message "send it to them".

thanks for the report.  I don't think this is a bug in Libtool though
(see below for an explanation), besides the fact that the 2.2.10
testsuite wasn't as strict in avoiding broken gcj installations:

> 24. flags.at:24: testing ...
> ./flags.at:24: { test -n "$GCJ" && test "X$GCJ" != Xno; } || (exit 77)
> enable shared libraries
> ./flags.at:24: $LIBTOOL --tag=GCJ --mode=compile $compile -c $source
> stderr:
> Can't exec "/usr/bin/gcj": No such file or directory at /bin/gcj line 240.
> Couldn't exec at /bin/gcj line 240.
> stdout:
> libtool: compile:  gcj -g -O2 -c a.java 
> ./flags.at:24: exit code was 1, expected 0
> 24. flags.at:24: 24. passing GCJ flags through libtool (flags.at:24): FAILED 
> (flags.at:24)

This is a pretty clear hint that your gcj installation is not working as
expected.  It seems you inadvertently installed /usr/bin/gcj into
/bin/gcj.  Fixing this is outside the scope of Libtool, and I can't tell
you what could have caused it.


> It's my second trouble with libtool today; as I was compiling another
> package (I don't remember which... I am recompiling my entire system!) that
> requires libtool, maybe (dunno, I'm a beginner) it is useful:
> http://gcc.gnu.org/ml/gcc-patches/2008-03/msg00110.html (curiously, my
> Autoconf is 2.67, not 2.62...)

That patch you reference was for a fairly specific version
incompatibility, and shouldn't be relevant with current autotools
versions any more.  Whatever trouble you have, probably has a different
reason.  Without lots more details there's nothing we can do to help you
though.

Cheers,
Ralf



reply via email to

[Prev in Thread] Current Thread [Next in Thread]