New Failures in libjava Testsuite - Weird libtool Behaviour

Tue Jun 1 07:06:00 GMT 2004

On 2004年5月31日 10:50:30 -0400, Bryce McKinlay <mckinlay@redhat.com> wrote:
>> Ranjit Mathew wrote:
>> > Today's build has these new libjava testsuite failures:
> >
> > FAIL: TestEarlyGC compilation from source
> > FAIL: TestLeak compilation from source
> > FAIL: TestMultiple compilation from source
> > FAIL: TestParent compilation from source
> >
> >All of them fail because "dummy.o" is being created by
> >libtool in the ".libs" sub-folder of the testsuite
> >folder instead of the folder above it, *even when
> >explicitly being asked to create it above it via a
> >-o option* from the test script.
> >
> >Why is the generated libtool suddenly behaving like
> >this? What could have caused this behaviour? ("lt*.*"
> >in the toplevel folder haven't changed in around
> >4 weeks now.)
> >
> >
>> Actually I've been seeing these failures for a while (at least 4 weeks).
> I just xfailed them in my tree. I've been avoiding looking into them
> because I usually end up being traumatized by anything to do with
> libtool. They don't seem to happen for everyone?

Ok, this is really weird, but I have found out that
this is being caused by an explicit "--enable-shared"
on the configure line. I started seeing this from yesterday
as I had modified my configure script to add
"--enable-shared --disable-static" (as suggested by *you*
elsewhere, :-P).
I think even you're facing the same issue and you should
remove that explicit "--enable-shared" from your configure
script/command-line.
I'm another of those people "traumatised" by libtool (and
auto*), so I'll leave this for now and let someone else
with more of a clue to handle this.
Ranjit.