Re: Unreviewed libjava testsuite patch for 3.0.1

[Tom Tromey <tromey at redhat dot com>]

>>>>> "Rainer" == Rainer Orth <ro@TechFak.Uni-Bielefeld.DE> writes:

Rainer> This patch
Rainer> 	http://gcc.gnu.org/ml/java/2001-06/msg00247.html
Rainer> has never been reviewed or otherwise commented upon.

Sorry about that.

I'm not sure I know enough to choose between the alternatives offered
in this message.  I CC'd Alexandre Oliva, my favorite shared library
expert, in the hopes that he can help.

As I understand it the problem is that gcj automatically links against
certain libraries, and then the test suite links against them as well.
We could modify the test suite not to do this, but then we might run
into problems when running the tests uninstalled.

Is that right?

I'm not overly concerned which particular solution we adopt, provided
that it meets our goals.  I think the biggest goal is that `make
check' should always take libraries from the build tree, and that it
should work even if libgcj has not yet been installed on the system.
Maintenance and comprehensibility are secondary; we can always add a
big comment explaining what horrible thing we did.

I'm guessing it will be easiest to adopt something like the patch you
sent.  That's because over time we'll be adding more libraries to
libgcj.spec.  configure will be picking these.  Trying to get that
information into dejagnu seems like a pain, since it is already
available to gcj more directly.

Tom