public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jon Portnoy <avenj@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-core] dev-lang/icc and dev-lang/ifc candidates for removal
Date: Tue, 10 May 2005 18:37:56 -0400	[thread overview]
Message-ID: <20050510223756.GA10756@cerberus.oppresses.us> (raw)
In-Reply-To: <1115755908.27166.12.camel@cgianelloni.nuvox.net>

On Tue, May 10, 2005 at 04:11:48PM -0400, Chris Gianelloni wrote:
> On Tue, 2005-05-10 at 20:06 +0200, Danny van Dyk wrote:
> > icc/ifc use flags:
> >  * These are scary. Using a different compiler should not be achieved
> >    by setting a useflag, neither local nor global one.
> 
> You are correct.  However, it might be necessary to patch something that
> won't compile with icc, but does compile with gcc.  I think this is the
> primary reason for the icc USE flag.
> 

Yes, it is. As far as I know the icc USE flag doesn't actually change 
your compiler anywhere (it shouldn't)

-- 
Jon Portnoy
avenj/irc.freenode.net
-- 
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2005-05-10 22:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-10  5:36 [gentoo-dev] dev-lang/icc and dev-lang/ifc candidates for removal Brian Harring
2005-05-10  6:19 ` [gentoo-dev] Re: [gentoo-core] " Danny van Dyk
2005-05-10 17:28   ` Tom Van Doorsselaere
2005-05-10 18:06     ` Danny van Dyk
2005-05-10 20:11       ` Chris Gianelloni
2005-05-10 20:20         ` Diego 'Flameeyes' Pettenò
2005-05-10 22:37         ` Jon Portnoy [this message]
2005-05-11  3:18       ` Brian Harring
2005-05-11  8:11         ` Danny van Dyk
2005-05-11  8:21           ` Brian Harring
2005-05-11  6:38       ` Andreas Fredriksson
2005-05-11 22:41   ` Karl Trygve Kalleberg
2005-05-11 23:05     ` Danny van Dyk
2005-05-16 11:07       ` Tom Van Doorsselaere
2005-05-11 21:51 ` [gentoo-dev] " Daniel Goller

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=20050510223756.GA10756@cerberus.oppresses.us \
    --to=avenj@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