public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: danglin@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libf2c/6288: libg2c.sl.0.0 and libobjc.sl.1.0 are linked to libgcc_s.sl in build directory after installation
Date: Thu, 02 May 2002 07:26:00 -0000 [thread overview]
Message-ID: <20020502142602.3051.qmail@sources.redhat.com> (raw)
The following reply was made to PR libf2c/6288; it has been noted by GNATS.
From: Alexandre Oliva <aoliva@redhat.com>
To: danglin@gcc.gnu.org
Cc: dave.anglin@nrc.ca, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: libf2c/6288: libg2c.sl.0.0 and libobjc.sl.1.0 are linked to libgcc_s.sl in build directory after installation
Date: 02 May 2002 11:20:52 -0300
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
next reply other threads:[~2002-05-02 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 7:26 Alexandre Oliva [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-17 20:23 danglin
2002-04-13 11:46 dave.anglin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020502142602.3051.qmail@sources.redhat.com \
--to=aoliva@redhat.com \
--cc=danglin@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).