From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] conversion of USE=nocxx to USE=cxx
Date: Sun, 13 Nov 2011 16:42:39 -0500 [thread overview]
Message-ID: <4EC039CF.6080309@gentoo.org> (raw)
In-Reply-To: <201111131342.43558.vapier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
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?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 230 bytes --]
next prev parent reply other threads:[~2011-11-13 21:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 18:42 [gentoo-dev] conversion of USE=nocxx to USE=cxx Mike Frysinger
2011-11-13 21:42 ` Mike Gilbert [this message]
2011-11-14 3:49 ` [gentoo-dev] " Ryan Hill
2011-11-14 15:43 ` Mike Gilbert
2011-11-14 4:37 ` [gentoo-dev] " Mike Frysinger
2011-11-14 19:00 ` Mike Gilbert
2011-11-14 20:03 ` Mike Frysinger
2011-11-14 20:42 ` Mike Gilbert
2011-11-14 17:40 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EC039CF.6080309@gentoo.org \
--to=floppym@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox