public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca> To: nobody@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 l Date: Tue, 16 Apr 2002 10:26:00 -0000 [thread overview] Message-ID: <20020416172601.21765.qmail@sources.redhat.com> (raw) The following reply was made to PR libf2c/6288; it has been noted by GNATS. From: "John David Anglin" <dave@hiauly1.hia.nrc.ca> To: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org Cc: dave.anglin@nrc.ca, law@redhat.com, mark@codesourcery.com Subject: Re: libf2c/6288: libg2c.sl.0.0 and libobjc.sl.1.0 are linked to l Date: Tue, 16 Apr 2002 13:24:15 -0400 (EDT) > >Synopsis: libg2c.sl.0.0 and libobjc.sl.1.0 are linked to libgcc_s.sl > in build directory after installation The above is also true for libstdc++.sl. The result is libraries that are more or less useless unless the user manually uses chatr to enable searching with SHLIB_PATH or LD_LIBRARY_PATH under hpux 10 and 11, respectively. Alex says that libtool isn't designed to relink unless libgcc_s.sl becomes a libtool library. I can't see that happening in the near term. Thus, the simplest solution seems to be to stop building a shared libgcc under hpux 10 and 11 (32bit) until the installation issues are resolved. I don't particularly want to do this because of the issues we have had in the past in linking a static version of libgcc against libstdc++.sl. I'm not a security expert but I think that the incorrect path in the installed libraries is potentially a security issue. Does anybody have any other suggestions? I'm doing a build with a patch to config.gcc to disable building libgcc_s.sl to see if it impacts the testsuite results. Dave -- J. David Anglin dave.anglin@nrc.ca National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
next reply other threads:[~2002-04-16 17:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-16 10:26 John David Anglin [this message] 2002-04-16 13:16 law 2002-04-17 20:36 John David 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=20020416172601.21765.qmail@sources.redhat.com \ --to=dave@hiauly1.hia.nrc.ca \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).