public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ww@mpi-sb.mpg.de
To: gcc-gnats@gcc.gnu.org
Subject: other/6335: version specific runtime libs are not found at runtime
Date: Wed, 17 Apr 2002 05:06:00 -0000	[thread overview]
Message-ID: <20020417120152.2528.qmail@sources.redhat.com> (raw)


>Number:         6335
>Category:       other
>Synopsis:       version specific runtime libs are not found at runtime
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Apr 17 05:06:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     ww@mpi-sb.mpg.de
>Release:        3.0 - 3.0.4
>Organization:
>Environment:
At least Solaris 8 and Linux
>Description:
I use the configure option --enable-version-specific-runtime-libs together with a --prefix. The runtile libs for g++ (e.g. libstadc++.so.3) are then found at link time but not at runtime of the created binary. As a workaround I use an ugly wrapper witch adds the corresponding linker flag (e.g. for Solaris: -R/$MYPREFIX/lib/gcc-lib/sparc-sun-solaris2.8/3.0.4/), which is a real nightmare. The linker call must already posess the location of the libraries and should build it into the binary. 
>How-To-Repeat:
A gcc buit with this option fails the g++ test of the groff source with, because the simple c++ program binary does not find libstdc++.so.3 
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-04-17 12:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-17  5:06 ww [this message]
2002-12-09 13:25 ehrhardt

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=20020417120152.2528.qmail@sources.redhat.com \
    --to=ww@mpi-sb.mpg.de \
    --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).