From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Pre RFC on RFC: Add compiler information to exported a Package Manger's Cached Information.
Date: Sat, 21 Feb 2015 12:18:17 -0800 [thread overview]
Message-ID: <54E8E809.8050702@gentoo.org> (raw)
In-Reply-To: <54E8AF00.20305@opensource.dyc.edu>
On 02/21/2015 08:14 AM, Anthony G. Basile wrote:
> Finally, a limitation of the above should be noted. Since the
> CFLAGS/CXXFLAGS cached are only those supplied by the user, it does not
> cover situations where the package build system or ebuild supply their
> own -std= flag. Since this information cannot and should not be cached
> by the package manager, utilities used to find any mismatches in C++ ABI
> must provide for this intelligence.
I wonder if it's feasible to force the -rpath option when using the
-std= flag, and force the real/canonical libstc++.so path into the
rpath. There's some mention of -rpath here:
http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html#AEN95
Have the -rpath information in the binaries should make it easy to
correctly resolve the library dependencies.
--
Thanks,
Zac
next prev parent reply other threads:[~2015-02-21 20:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-21 16:14 [gentoo-portage-dev] Pre RFC on RFC: Add compiler information to exported a Package Manger's Cached Information Anthony G. Basile
2015-02-21 20:18 ` Zac Medico [this message]
2015-02-22 6:22 ` Zac Medico
2015-02-22 6:30 ` Zac Medico
2015-02-25 19:51 ` Anthony G. Basile
2015-02-25 20:01 ` Anthony G. Basile
2015-02-25 20:38 ` Zac Medico
2015-02-25 23:41 ` Anthony G. Basile
2015-02-26 0:07 ` Zac Medico
2015-03-02 3:25 ` Zac Medico
2015-03-02 4:27 ` Zac Medico
2015-02-25 20:34 ` Zac Medico
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=54E8E809.8050702@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.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