michael higgins wrote:
On Thu, 16 Jun 2005 14:08:46 -0700
Zac Medico [EMAIL PROTECTED] wrote:
michael higgins wrote:
I have a couple of questions about using distcc. I have two machines. One is
significantly faster than the other, both x86 (pentium 2 and amd athlon-xp).
First, a big
On Thu, 16 Jun 2005 14:08:46 -0700
Zac Medico [EMAIL PROTECTED] wrote:
michael higgins wrote:
I have a couple of questions about using distcc. I have two machines. One
is significantly faster than the other, both x86 (pentium 2 and amd
athlon-xp).
First, a big thanks to all who
There were some changes to the tool chain which means that distcc wont
work across different x86 archs (e.g., athlon and pentium) and the devs
wont change it (marked as WONT FIX on the bug).
Hmm, I haven't heard anything about this and have been using distcc on an
x86 athlon network. Each
read the bug :) - the bug numbers in the email, or search the forums
like I did.
Are you sure its building? distcc connects to the machine in question,
but doesnt actually build anything as it cant run gcc as the toolchain
does not call it gcc internally anymore, but includes i[3456]86 in the
read the bug :) - the bug numbers in the email, or search the forums
like I did.
What a pain. I'm sure the change was meant to solve another problem, but
it's unfortunate that it broke distcc in the process.
Are you sure its building? distcc connects to the machine in question,
but doesnt
michael higgins wrote:
I have a couple of questions about using distcc. I have two machines. One is
significantly faster than the other, both x86 (pentium 2 and amd athlon-xp).
I've followed the http://www.gentoo.org/doc/en/distcc.xml instructions for
configuring portage to use distcc.
Hi,
In order for distcc to actually work there are a few steps to make:
If you have one machine 192.168.0.1 second 192.168.0.2 and assuming
192.168.0.1 is the power
These are the things you should do on the slow machine (there may be
more, i've done it some time ago :)):
There were some changes to the tool chain which means that distcc wont
work across different x86 archs (e.g., athlon and pentium) and the devs
wont change it (marked as WONT FIX on the bug).
The workaround is to add CC-gcc and CXX=g++ to make .conf on the client,
however this may break other
8 matches
Mail list logo
