Thanks for help, this problem is not the one that aches me right now - and when I re-thaught it again I simply realized that it dissapeared.

BUT
Do somebody know how from distcc tell ssh which port to use to connect to remote machine - all of "my" computers use nonstandard ssh port - I know I can utilize ~/.ssh/config but how to use it for "portage" user that runs distcc from emerge?

I tried
http://en.gentoo-wiki.com/wiki/Distcc_over_SSH

But got stuck on those ports

I do not want to use distcc daemon - I prefere ssh because in that way there sits only one daemon when is Im not compilinig instead of two (open ports, resources,....)

S


On 2012-06-04 09:48, Daniel Wagener wrote:
On Sun, 03 Jun 2012 16:44:19 +0200
Samuraiii <samurai.no.d...@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.


--
Samuraiii
e-mail: samurai.no.d...@gmail.com
GnuPG key ID: 0x80C752EA (obtainable on http://pgp.mit.edu)
Full copy of public timestamp block signatures id-14969 (from 2012-06-05 12:00:10) is included in header of html.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to