| 1 |
On Mon, Oct 20, 2014 at 9:47 AM, Martin Vaeth <martin@×××××.de> wrote: |
| 2 |
> Anthony G. Basile <blueness@g.o> wrote: |
| 3 |
>>> Since gcc-4.7 there is a -std=c++11 option, do not use it {+yet+} |
| 4 |
>>> since it breaks the ABI, resulting in a non-functional system. |
| 5 |
>> |
| 6 |
>> Yes. Eventually we'll have to clear the road for this. |
| 7 |
> |
| 8 |
> Isn't Diego just starting a gcc-4.9 tinderbox run? |
| 9 |
> |
| 10 |
> It might be worth to try with -std=gnu++11 immediately: |
| 11 |
> Most API incompatibilities which I experienced in my projects |
| 12 |
> were either name clashes (with symbols not existing yet in c++98) |
| 13 |
> or other trivial things (like some "char *" returns intead of |
| 14 |
> "const char *" returns etc.); cleanly written code is likely |
| 15 |
> to be upward compatible without any issues. |
| 16 |
> |
| 17 |
|
| 18 |
Probably worth doing in general, but I think it makes sense to get rid |
| 19 |
of all the roadblocks to getting 4.9.1 working with the old ABI first. |
| 20 |
Now excuse me while I got try to reproduce a tinderbox failure... :) |
| 21 |
|
| 22 |
-- |
| 23 |
Rich |
Archives