From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] Re: problem with distcc
Date: Tue, 11 Apr 2006 16:22:25 -0400 [thread overview]
Message-ID: <1144786945.14010.43.camel@inertia.twi-31o2.org> (raw)
In-Reply-To: <pan.2006.04.11.20.07.35.26586@novazur.fr>
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
On Tue, 2006-04-11 at 16:07 -0400, Christophe PEREZ wrote:
> I'll try again without distcc for building stage1.
> But, if it works, I'm curious to know the real right way to do it ?
It works perfectly provided you have;
same compiler versions
same compiler names
What this means is for you to build a CHOST=i586-pc-linux-gnu machine,
you are *required* to have a cross-compiler that is named
i586-pc-linux-gnu-gcc on each of your distcc slaves.
--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-04-11 20:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 15:12 [gentoo-catalyst] problem with distcc Christophe PEREZ
2006-04-11 18:25 ` Chris Gianelloni
2006-04-11 19:17 ` [gentoo-catalyst] " Christophe PEREZ
2006-04-11 19:35 ` Christophe PEREZ
2006-04-11 20:07 ` Christophe PEREZ
2006-04-11 20:12 ` Andrew Gaffney
2006-04-11 20:36 ` [gentoo-catalyst] " Christophe PEREZ
2006-04-11 20:22 ` Chris Gianelloni [this message]
2006-04-11 20:39 ` Christophe PEREZ
2006-04-11 20:57 ` Christophe PEREZ
2006-04-11 21:45 ` Chris Gianelloni
2006-04-11 22:02 ` [gentoo-catalyst] " Christophe PEREZ
2006-04-12 13:48 ` Chris Gianelloni
2006-04-12 15:51 ` [gentoo-catalyst] " Christophe PEREZ
2006-04-12 20:12 ` Chris Gianelloni
2006-04-12 21:07 ` [gentoo-catalyst] " Christophe PEREZ
2006-04-12 21:34 ` Christophe PEREZ
2006-04-13 13:06 ` Chris Gianelloni
2006-04-13 13:59 ` [gentoo-catalyst] " Christophe PEREZ
2006-04-13 15:59 ` Christophe PEREZ
2006-04-11 20:01 ` Andrew Gaffney
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=1144786945.14010.43.camel@inertia.twi-31o2.org \
--to=wolf31o2@gentoo.org \
--cc=gentoo-catalyst@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