[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    Re: [gentoo-dev] impending c++11 clusterfuck?
From:       C Bergström <cbergstrom () pathscale ! com>
Date:       2015-11-30 22:49:09
Message-ID: CAOnawYqaSg1bH1U-dw3PWSuB=b_8_3J4ThViMWXNmyjs_jcxOA () mail ! gmail ! com
[Download RAW message or body]

One thing to point out.. trying to detect and using vX are just hacks
for what this really is - Adding abi (C++STL/ABI) information to the
ebuilds/packages.

To extend this - what happens when you have a compiler that isn't
compatible with the system default? When the package is merged should
some information from the toolchain like g++-48-cpp03 be inserted for
the package? The only downside I could think about is a crazy world
where libs end up being installed in.

/usr/lib64/{CPP-ABI}
/usr/lib64/g++-48-cpp03/

In this case the default system compiler could be gcc5 and then an
"alt" compiler which provides a different ABI could be used based on
some "restrict" or explicit information in the ebuild. That alt
compiler would have to build all the dependencies, but as long as it
knew about /usr/lib64/g++-48-cpp03/ and not /usr/lib64/g++-52-cpp11/
things would be ok...

If you want c++11 and 03 to exist, link together and be perfect at the
same time.. I think you're asking for trouble or the impossible.

While we're solving this problem - the same sort of "ABI" may also
help other languages suffering from similar problems like python
(Which now "fixed" their problem, but it's still not a perfect world)

Nothing is to say it won't pop up again in the future (Java?)...

[prev in list] [next in list] [prev in thread] [next in thread]