This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC 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: rpath and libtool == testsuite woes

From: Kean Johnston <jkj at sco dot com>
To: Alan Modra <amodra at bigpond dot net dot au>
Cc: Alexandre Oliva <aoliva at redhat dot com>, gcc at gcc dot gnu dot org
Date: Thu, 07 Aug 2003 23:48:51 -0700
Subject: Re: rpath and libtool == testsuite woes
Organization: The SCO Group
References: <20030807052955.GF27145@bubble.sa.bigpond.net.au> <orekzxiba5.fsf@free.redhat.lsd.ic.unicamp.br> <20030808030430.GL27145@bubble.sa.bigpond.net.au>

What's the proper fix for running the libjava testsuite then?
I just hacked around it..

If what you want to do is run the testsuite, configure your tree with --disable-shared so that libtool only builds static libraries. This isnt good for a production build, unless you are OK with static libraries. Personally (and this is just MY opinion), its a better way to go. I always compil with just static. That way I dont have to keep (over time) multiple versions of the .so lying around for applications that were compiled and linked against the older versions.

Kean

References:
- rpath and libtool == testsuite woes
  - From: Alan Modra
- Re: rpath and libtool == testsuite woes
  - From: Alexandre Oliva
- Re: rpath and libtool == testsuite woes
  - From: Alan Modra

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