| 1 |
On 11/13/2011 01:42 PM, Mike Frysinger wrote: |
| 2 |
> now that we have USE=cxx, and base/make.defaults has USE=cxx, i'd like to |
| 3 |
> migrate gcc away from USE=nocxx. |
| 4 |
> |
| 5 |
> since this can be a pickle, i'd propose toolchain.eclass grow the checks: |
| 6 |
> - use cxx && use nocxx && die |
| 7 |
> - use !cxx && use !nocxx && die |
| 8 |
> |
| 9 |
> this way when i do cut over from USE=nocxx to USE=cxx, we don't end up with |
| 10 |
> users missing C++ compilers simply because they have old make.conf settings |
| 11 |
> that started out with: |
| 12 |
> USE="-* ..." |
| 13 |
> |
| 14 |
> there are other ebuilds in the tree now that have USE=nocxx, but i'll take |
| 15 |
> care of converting them. |
| 16 |
> -mike |
| 17 |
|
| 18 |
www-client/google-chrome has RDEPEND=">=sys-devel/gcc-4.4.0[-nocxx]" to |
| 19 |
ensure that we have a recent version of libstdc++. We basically need to |
| 20 |
match Ubuntu LTS since that is what Google builds with. |
| 21 |
|
| 22 |
If I understand you correctly, you are just going to add a "cxx" use |
| 23 |
flag to gcc for some transitional period? If so, I can simply switch it |
| 24 |
at some point after you add the new flag? |
Archives