From: Teemu Torma <tot@trema.com>
To: Ian Lance Taylor <ian@cygnus.com>
Cc: oliva@dcc.unicamp.br, egcs@cygnus.com
Subject: Shared library runpath trouble in Solaris.
Date: Wed, 12 Nov 1997 04:01:00 -0000 [thread overview]
Message-ID: <199711121201.NAA21855@baht.labs.trema.com> (raw)
In-Reply-To: <199711111710.MAA13467@subrogation.cygnus.com>
From: Ian Lance Taylor <ian@cygnus.com>
Date: Tue, 11 Nov 1997 12:10:36 -0500
I'm just pointing out a serious problem I've seen with automatically
adding -R options. I've even described a solution which could be
implemented in collect2. What's wrong with the solution I described?
(To repeat: do the library searching in collect2, add a -R option if a
shared library will be used; I'm happy to make this a special case for
libstdc++, but I think it would also be reasonable to act otherwise).
I think this has to apply only to compiler generated search paths,
not to user specified ones.
Maybe options -nostdrunpath to disable this feature and -allstdrunpath
to do it always regardless whether a library is found or not. I can
see potential use that the run path is always there, in the case that
some library has to be replaced with os-specific/gcc-specific one.
Teemu
next prev parent reply other threads:[~1997-11-12 4:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-10 6:04 Teemu Torma
1997-11-10 8:42 ` Ian Lance Taylor
1997-11-10 9:08 ` Teemu Torma
1997-11-10 9:08 ` Ian Lance Taylor
1997-11-10 13:47 ` Alexandre Oliva
1997-11-10 13:47 ` Ian Lance Taylor
1997-11-10 18:41 ` Alexandre Oliva
1997-11-10 19:19 ` Ian Lance Taylor
1997-11-10 19:57 ` Alexandre Oliva
1997-11-11 9:10 ` Ian Lance Taylor
1997-11-11 12:28 ` Alexandre Oliva
1997-11-11 22:42 ` Alexandre Oliva
1997-11-12 4:01 ` Teemu Torma [this message]
1997-11-11 2:26 ` Swen Thuemmler
1997-11-10 10:17 ` Jeffrey A Law
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=199711121201.NAA21855@baht.labs.trema.com \
--to=tot@trema.com \
--cc=egcs@cygnus.com \
--cc=ian@cygnus.com \
--cc=oliva@dcc.unicamp.br \
/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).