This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: libjava testsuite problem under i686-pc-linux-gnu
- To: "John David Anglin" <dave at hiauly1 dot hia dot nrc dot ca>
- Subject: Re: libjava testsuite problem under i686-pc-linux-gnu
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 27 May 2001 17:51:05 -0300
- Cc: aph at cambridge dot redhat dot com (Andrew Haley), java at gcc dot gnu dot org
- Organization: GCC Team, Red Hat
- References: <200105262038.QAA15489@hiauly1.hia.nrc.ca>
On May 26, 2001, "John David Anglin" <dave@hiauly1.hia.nrc.ca> wrote:
> This suggests that libtool should look at `-B' options as well as `-L'
> options when it generates `rpath' options in the preinstall case.
Huh? What do -L and -B have to do with this?
The real problem is that libgcc_s is not a libtool library, so libtool
can't do its magic of creating an executable that can run properly in
the build directory. Presumably, setting LD_LIBRARY_PATH or
equivalent, as we already do to run tests, should get the dynamic
linker to find the correct libgcc_s. What if you run ldd with
LD_LIBRARY_PATH set?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me