From: "Stephen P. Becker" <geoman@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rm `which gcc` && emerge -e world
Date: Sat, 22 Oct 2005 15:11:35 -0400 [thread overview]
Message-ID: <435A8EE7.406@gentoo.org> (raw)
In-Reply-To: <200510221506.43041.vapier@gentoo.org>
Mike Frysinger wrote:
> On Saturday 22 October 2005 10:02 am, Tomasz Mloduchowski wrote:
>
>>Altough geoman raised a valid point with separate distcc server, I'm
>>glad something is being done to fix this issue.
>
>
> you could also work around it by exporting CC and CXX before emerging to say
> 'i686-pc-linux-gnu-gcc' and 'i686-pc-linux-gnu-g++'
> -mike
I'm not sure that works 100% of the time.
-Steve
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-22 19:13 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
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 [this message]
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=435A8EE7.406@gentoo.org \
--to=geoman@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