public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dave.anglin@nrc.ca
To: gcc-gnats@gcc.gnu.org
Subject: libf2c/6288: libg2c.sl.0.0 and libobjc.sl.1.0 are linked to libgcc_s.sl in build directory after installation
Date: Sat, 13 Apr 2002 11:46:00 -0000 [thread overview]
Message-ID: <20020413183918.4719.qmail@sources.redhat.com> (raw)
>Number: 6288
>Category: libf2c
>Synopsis: libg2c.sl.0.0 and libobjc.sl.1.0 are linked to libgcc_s.sl in build directory after installation
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sat Apr 13 11:46:04 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: Dave Anglin
>Release: gcc 3.1 (prerelease)
>Organization:
>Environment:
hppa[1.1,2.0w]-hp-hpux[10,11].*
>Description:
In the process, I discovered that libg2c.sl.0.0 and
libobjc.sl.1.0 are linked to libgcc_s.sl
in the build directory after installation:
# chatr libg2c.sl.0.0
[...]
internal name:
libg2c.sl.0
shared library list:
dynamic /usr/lib/libm.2
dynamic /usr/lib/libc.2
dynamic /xxx/gnu/gcc-3.1/objdir/gcc/libgcc_s.sl
The installation/build process has incorrectly linked
against libgcc_s.sl in my build directory rather than
against the newly installed version in the installation
directory. When libgcc_s.sl is removed from the build
directory, the dynamic loader is unable to find libgcc_s.sl
and applications linked against the libraries nolonger
run.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-04-13 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-13 11:46 dave.anglin [this message]
2002-04-17 20:23 danglin
2002-05-02 7:26 Alexandre Oliva
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=20020413183918.4719.qmail@sources.redhat.com \
--to=dave.anglin@nrc.ca \
--cc=gcc-gnats@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).