public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Greg Turner <gmt@be-evil.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] impending c++11 clusterfuck?
Date: Mon, 30 Nov 2015 10:34:37 -0800	[thread overview]
Message-ID: <CA+VB3NQqk5__DJ7t3qc7t96BrKUABjL6A28E9xYjm1X5LvH7fA@mail.gmail.com> (raw)
In-Reply-To: <565C3392.2060405@gentoo.org>

https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html
makes for pretty interesting reading on this topic.

https://youtu.be/Ic4j0ujWL-A looks interesting too.

-gmt
-gmt

Greg Turner
gmt@be-evil.net


On Mon, Nov 30, 2015 at 3:31 AM, Anthony G. Basile <blueness@gentoo.org> wrote:
> On 11/30/15 6:17 AM, Anthony G. Basile wrote:
>> different direction: what about building with
>> rpath=/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.3/ and then making sure that
>> portage respects that library file during any --depclean or
>> @preserved-rebuild?  i'm not sure how we'd
>> inject LDFLAGS=-Wl,-rpath=... consistantly and sanely into all c++ builds.
>>
>> this would solve all problems i can see: 1) gcc-config reshuffles
>> /etc/ld.so.conf.d/05gcc-<tuple>.conf but rpath takes presidence, 2) the
>> correct library symbols are guaranteed to be there in both exe and lib.
>> 3) it pro-actively guards against abi mismatches when switching gcc even
>> for other languages like fortran, java, obj-c.
>
> oh i should add that we don't support switching back and forth between
> c++98 and c++11.  which is used is an upstream choice via whatever -std=
> they add to the build system, otherwise we go with the compiler default.
>
> i'm going to play with situations like foo is built using
> c++{98,11}/gcc-4.{8,9} and links against libbar built using
> c++{98,11}/gcc-4.{8,9} and libbas similarly built using the rpath
> technique and see what kind of wierdness i might hit.  i stil think it
> will work.
>
> --
> Anthony G. Basile, Ph.D.
> Gentoo Linux Developer [Hardened]
> E-Mail    : blueness@gentoo.org
> GnuPG FP  : 1FED FAD9 D82C 52A5 3BAB  DC79 9384 FA6E F52D 4BBA
> GnuPG ID  : F52D4BBA
>
>


  reply	other threads:[~2015-11-30 18:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30  3:56 [gentoo-dev] impending c++11 clusterfuck? Gregory M. Turner
2015-11-30  4:10 ` C Bergström
2015-11-30  8:52   ` Mikhail Korolev
2015-11-30  6:42 ` Michał Górny
2015-11-30  8:07   ` Anthony G. Basile
2015-11-30  9:52     ` Michał Górny
2015-11-30 11:17       ` Anthony G. Basile
2015-11-30 11:31         ` Anthony G. Basile
2015-11-30 18:34           ` Greg Turner [this message]
2015-11-30 18:37             ` Greg Turner
2015-11-30 22:49               ` C Bergström
2015-12-01  8:59         ` Benda Xu
2015-12-01  9:03           ` Anthony G. Basile
2015-12-01 11:25         ` Michał Górny
2015-12-01 12:18           ` Anthony G. Basile
2015-12-02  2:12             ` Gregory M. Turner
2015-12-02  7:06               ` Michał Górny
2015-12-02  7:38                 ` Anthony G. Basile
2015-12-02 12:54                   ` Patrick Lauer
2015-12-02 10:00                 ` Gregory M. Turner
2015-12-02 12:57                   ` Michał Górny
2015-11-30 10:16     ` Greg Turner
2015-11-30 10:42       ` Greg Turner
2015-11-30  9:18   ` Gregory M. Turner
2015-11-30  9:58     ` Michał Górny
2015-11-30 16:48 ` Steven Lembark

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=CA+VB3NQqk5__DJ7t3qc7t96BrKUABjL6A28E9xYjm1X5LvH7fA@mail.gmail.com \
    --to=gmt@be-evil.net \
    --cc=gentoo-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