This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libf2c/6288: libg2c.sl.0.0 and libobjc.sl.1.0 are linked to libgcc_s.sl in build directory after installation
- From: Alexandre Oliva <aoliva at redhat dot com>
- To: danglin at gcc dot gnu dot org
- Cc: dave dot anglin at nrc dot ca, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
- Date: 02 May 2002 11:20:52 -0300
- Subject: Re: libf2c/6288: libg2c.sl.0.0 and libobjc.sl.1.0 are linked to libgcc_s.sl in build directory after installation
- Organization: GCC Team, Red Hat
- References: <20020418032329.16212.qmail@sources.redhat.com>
On Apr 18, 2002, danglin@gcc.gnu.org wrote:
> Can't duplicate problem after reinstall of gcc 3.1. Although
> the dynamic path for libgcc_s.sl is incorrect, the embedded path
> is correctly set and should normally allow libgcc_s.sl to be
> found in the installation directory.
HP-UX is a bit confusing as for shared library paths. The location of
a shared library at link time is stored in libraries or executables
linked with it, as a fallback in case the library is not found
elsewhere.
Since we actually require LD_LIBRARY_PATH or equivalent (SHLIB_PATH,
for HP-UX) for GCC's shared libraries to be usable in general, this
should get libgcc working just fine too.
--
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 Professional serial bug killer