| 1 |
On Thu, 19 Dec 2013 10:18:55 +0100 |
| 2 |
Michał Górny <mgorny@g.o> wrote: |
| 3 |
|
| 4 |
> And that brings another issue in Gentoo -- gcc-config. AFAIR this tool |
| 5 |
> is completely insane and switches libstdc++ along with gcc version. |
| 6 |
> As a result, after switching to a gcc version with different C++ ABI, |
| 7 |
> installed software gets broken. And you can't really fix it without |
| 8 |
> going through the broken-system state or some hackery. |
| 9 |
|
| 10 |
This hasn't been true for a while now. The latest version of libstdc++ is |
| 11 |
always used, no matter what version is selected. I can't remember when this |
| 12 |
was changed but we've gone through a couple GCC stabilizations since. |
| 13 |
|
| 14 |
I have no opinion on how to support C++-11, except that it can't be globally |
| 15 |
enabled. We have to support compilers that predate the standard. |
| 16 |
|
| 17 |
I wouldn't like any pkg-config hackery like ICU tried to pull a while back, but |
| 18 |
now that we have a version of gcc that at least understands the flag in |
| 19 |
stable at least it wouldn't instantly break everything. |
| 20 |
|
| 21 |
|
| 22 |
-- |
| 23 |
Ryan Hill psn: dirtyepic_sk |
| 24 |
gcc-porting/toolchain/wxwidgets @ gentoo.org |
| 25 |
|
| 26 |
47C3 6D62 4864 0E49 8E9E 7F92 ED38 BD49 957A 8463 |
Archives