public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: sean <tech.junk@verizon.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] distcc
Date: Sun, 07 Jan 2007 15:47:41 -0500	[thread overview]
Message-ID: <45A15C6D.8050703@verizon.net> (raw)
In-Reply-To: <459EBF32.1060006@neo.rr.com>

John Blinka wrote:
> sean wrote:
>> John Blinka wrote:
>>
>>>
>>> I think this is backwards.  The cross compiler should be on the 
>>> Opteron box, since distcc is asking
>>> the Opteron box to produce 32 bit code for the P4 box.
>>>
>>
>> Check this out. Look at the line highlighted in green.
>>
>> http://www.gentoo.org/doc/en/cross-compiling-distcc.xml
> Yep, that's exactly the document I used to get cross-compiling working 
> with distcc
> on my machines.  See the paragraph near the top under the heading "Emerge
> the needed utilities".   The first sentence of this paragraph refers to 
> machines "that
> will be involved in the compiling process".   One might argue that both 
> your P4 and Opteron
> machines are "involved" since the P4 calls the compiler and the Opteron 
> does the compiling.
> But the sentence really refers to machines that will actually *do* the 
> compiling, i.e., your
> Opteron.  So you should do 2 things on the Opteron box: "emerge 
> crossdev" and
> "crossdev -t arg" where I'm guessing "arg" is i686-pc-linux-gnu for your 
> P4 box.
> The green highlighted stuff are things you do on the P4 box.  The 
> explanation for
> doing the green highlighted stuff is found at the end of the page under 
> the heading
> "Why this works".
> 
> John Blinka

Thanks John,

	Perhaps it is just me, but maybe the docs on this topic could use just 
a bit more sharpening to clear things.

			Sean
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-01-07 20:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-05 13:47 [gentoo-user] distcc sean
2007-01-05 13:54 ` sean
2007-01-05 13:54 ` Nelson, David (ED, PAR&D)
2007-01-05 14:22 ` Uwe Thiem
2007-01-05 16:47   ` sean
2007-01-05 17:45     ` John Blinka
2007-01-05 18:00       ` sean
2007-01-05 21:12         ` John Blinka
2007-01-07 20:47           ` sean [this message]
2007-01-05 18:36     ` Uwe Thiem
2007-01-06 18:57       ` Randy Barlow
2007-01-06 14:27 ` Pawel Kraszewski
2007-01-07  2:45   ` sean
2007-01-07 18:34     ` Pawel Kraszewski

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=45A15C6D.8050703@verizon.net \
    --to=tech.junk@verizon.net \
    --cc=gentoo-user@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