public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rm `which gcc` && emerge -e world
Date: Sat, 22 Oct 2005 00:48:16 -0400	[thread overview]
Message-ID: <200510220048.16429.vapier@gentoo.org> (raw)
In-Reply-To: <1129950753.4942.15.camel@TSUNAMI.MIT.EDU>

On Friday 21 October 2005 11:12 pm, Tomasz Mloduchowski wrote:
> I got sick of filling 3 almost identical bug reports

please stop doing this

we are already playing with doing this in the wrapper itself so that 
compilation is transparent

i'd wager to say the majority of packages in portage run `gcc` and `g++` 
rather than ${CTARGET}-gcc
-mike
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-10-22  4:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-22  3:12 [gentoo-dev] rm `which gcc` && emerge -e world Tomasz Mloduchowski
2005-10-22  4:48 ` Mike Frysinger [this message]
2005-10-22 14:02   ` Tomasz Mloduchowski
2005-10-22 14:21     ` Diego 'Flameeyes' Pettenò
2005-10-22 19:06     ` Mike Frysinger
2005-10-22 19:11       ` Stephen P. Becker
2005-10-22 19:15         ` Mike Frysinger
2005-10-22 12:17 ` Stephen P. Becker

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=200510220048.16429.vapier@gentoo.org \
    --to=vapier@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