From: Daniel Wagener <stelf@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Distcc advice needed
Date: Mon, 4 Jun 2012 09:48:36 +0200 [thread overview]
Message-ID: <20120604094836.804a802d.stelf@gmx.net> (raw)
In-Reply-To: <4FCB7843.6040707@gmail.com>
On Sun, 03 Jun 2012 16:44:19 +0200
Samuraiii <samurai.no.dojo@gmail.com> wrote:
> Hello friends,
> I'm in need of good advice.
> I have 3 computers running gentoo and want to utilise all of them for
> distcc compiling - the emerging computer would be everytime different.
> Two machines are amd64 and one is x86 and this appears to be problem.
> According to http://www.gentoo.org/doc/en/cross-compiling-distcc.xml I
> need to edit some symlinks and if I'm going to emerge on either amd64 or
> X86.
> The problem is that wrapper script which calls c++ gcc g++ with
> architecture prefix.
> Is there a workaroud so that I do not need to change those symliks
> everytime Im going to emerge on different arch?
>
> Thanks for reply in advance
> S
You are going to need seperate toolchains, where afaik there are only two ways to tell them apart. The first is the path you install it in, the other is the binary code itself (and that only tells you they differ, not which one is for a defined arch).
So your best choice are those symlinks im afraid.
However, you can automate this process, maybe eselect can already do that for you, have not checked that yet.
next prev parent reply other threads:[~2012-06-04 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 14:44 [gentoo-user] Distcc advice needed Samuraiii
2012-06-04 7:48 ` Daniel Wagener [this message]
2012-06-05 15:43 ` [gentoo-user] «-»: " Samuraiii
2012-06-05 16:00 ` [gentoo-user] " Michael Mol
2012-06-05 16:53 ` [gentoo-user] «-»: " Samuraiii
2012-06-05 17:44 ` [gentoo-user] " Michael Mol
2012-06-05 18:24 ` Samuraiii
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=20120604094836.804a802d.stelf@gmx.net \
--to=stelf@gmx.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