This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: New Failures in libjava Testsuite - Weird libtool Behaviour

From: Bryce McKinlay <mckinlay at redhat dot com>
To: Ranjit Mathew <rmathew at gmail dot com>
Cc: java at gcc dot gnu dot org
Date: Mon, 31 May 2004 10:50:30 -0400
Subject: Re: New Failures in libjava Testsuite - Weird libtool Behaviour
References: <c9ekl4$b5i$1@sea.gmane.org>

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?

Regards

Bryce

References:
- New Failures in libjava Testsuite - Weird libtool Behaviour
  - From: Ranjit Mathew

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]