Re: [gentoo-dev] conversion of USE=nocxx to USE=cxx
On Sunday 13 November 2011 13:42:43 Mike Frysinger wrote: now that we have USE=cxx, and base/make.defaults has USE=cxx, i'd like to migrate gcc away from USE=nocxx. http://sources.gentoo.org/eclass/toolchain.eclass?r1=1.478r2=1.479 -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] conversion of USE=nocxx to USE=cxx
On 11/13/2011 11:37 PM, Mike Frysinger wrote: On Sunday 13 November 2011 16:42:39 Mike Gilbert wrote: If I understand you correctly, you are just going to add a cxx use flag to gcc for some transitional period? If so, I can simply switch it at some point after you add the new flag? transition period: http://sources.gentoo.org/www-client/google-chrome/google-chrome-17.0.932.0_alpha108826.ebuild?r1=1.1r2=1.2 eventually you can drop the [-nocxx] dep, but it'll prob be a while. -mike Thanks. Why do I need the [-nocxx] dep at this point? Everybody is going to end up rebuilding gcc with the new use flag anyway. signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] conversion of USE=nocxx to USE=cxx
On Monday 14 November 2011 14:00:01 Mike Gilbert wrote: On 11/13/2011 11:37 PM, Mike Frysinger wrote: On Sunday 13 November 2011 16:42:39 Mike Gilbert wrote: If I understand you correctly, you are just going to add a cxx use flag to gcc for some transitional period? If so, I can simply switch it at some point after you add the new flag? transition period: http://sources.gentoo.org/www-client/google-chrome/google-chrome-17.0.932 .0_alpha108826.ebuild?r1=1.1r2=1.2 eventually you can drop the [-nocxx] dep, but it'll prob be a while. Why do I need the [-nocxx] dep at this point? Everybody is going to end up rebuilding gcc with the new use flag anyway. some people might, but not everyone. if we remove the [-nocxx], and someone where to run `emerge google-chrome -u`, portage would fail with dependency errors. i'd leave the dep in there for a while until most people have upgraded naturally. perhaps after the next gcc stabilization. -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] conversion of USE=nocxx to USE=cxx
On 11/14/2011 3:03 PM, Mike Frysinger wrote: On Monday 14 November 2011 14:00:01 Mike Gilbert wrote: On 11/13/2011 11:37 PM, Mike Frysinger wrote: On Sunday 13 November 2011 16:42:39 Mike Gilbert wrote: If I understand you correctly, you are just going to add a cxx use flag to gcc for some transitional period? If so, I can simply switch it at some point after you add the new flag? transition period: http://sources.gentoo.org/www-client/google-chrome/google-chrome-17.0.932 .0_alpha108826.ebuild?r1=1.1r2=1.2 eventually you can drop the [-nocxx] dep, but it'll prob be a while. Why do I need the [-nocxx] dep at this point? Everybody is going to end up rebuilding gcc with the new use flag anyway. some people might, but not everyone. if we remove the [-nocxx], and someone where to run `emerge google-chrome -u`, portage would fail with dependency errors. Actually, it pulls in gcc[cxx], and rebuilds gcc. There is no dependency error. We can prevent an unnecessary gcc rebuild by listing [-nocxx] first however, so I committed that. signature.asc Description: OpenPGP digital signature
[gentoo-dev] conversion of USE=nocxx to USE=cxx
now that we have USE=cxx, and base/make.defaults has USE=cxx, i'd like to migrate gcc away from USE=nocxx. since this can be a pickle, i'd propose toolchain.eclass grow the checks: - use cxx use nocxx die - use !cxx use !nocxx die this way when i do cut over from USE=nocxx to USE=cxx, we don't end up with users missing C++ compilers simply because they have old make.conf settings that started out with: USE=-* ... there are other ebuilds in the tree now that have USE=nocxx, but i'll take care of converting them. -mike signature.asc Description: This is a digitally signed message part.
Re: [gentoo-dev] conversion of USE=nocxx to USE=cxx
On 11/13/2011 01:42 PM, Mike Frysinger wrote: now that we have USE=cxx, and base/make.defaults has USE=cxx, i'd like to migrate gcc away from USE=nocxx. since this can be a pickle, i'd propose toolchain.eclass grow the checks: - use cxx use nocxx die - use !cxx use !nocxx die this way when i do cut over from USE=nocxx to USE=cxx, we don't end up with users missing C++ compilers simply because they have old make.conf settings that started out with: USE=-* ... there are other ebuilds in the tree now that have USE=nocxx, but i'll take care of converting them. -mike www-client/google-chrome has RDEPEND==sys-devel/gcc-4.4.0[-nocxx] to ensure that we have a recent version of libstdc++. We basically need to match Ubuntu LTS since that is what Google builds with. If I understand you correctly, you are just going to add a cxx use flag to gcc for some transitional period? If so, I can simply switch it at some point after you add the new flag? signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] conversion of USE=nocxx to USE=cxx
On Sunday 13 November 2011 16:42:39 Mike Gilbert wrote: If I understand you correctly, you are just going to add a cxx use flag to gcc for some transitional period? If so, I can simply switch it at some point after you add the new flag? transition period: http://sources.gentoo.org/www-client/google-chrome/google-chrome-17.0.932.0_alpha108826.ebuild?r1=1.1r2=1.2 eventually you can drop the [-nocxx] dep, but it'll prob be a while. -mike signature.asc Description: This is a digitally signed message part.
