| View previous topic :: View next topic |
| Author |
Message |
AntonWert Apprentice

Joined: 06 Mar 2005 Posts: 177
|
Posted: Wed Mar 09, 2005 8:41 pm Post subject: big problems with distcc |
|
|
I have a very big problem with distcc, but im shure there is a simpe answer
i have an "old" pentium and a "new" p4
now i want to use distcc to compile on the p4
on both mashines the same gcc 3.3 is installed
everything works fine, but all ebuilds chrash on the same point, when distcc wants to compile on the p4
on the "old" mashine this is in the log:
...
## ----------- ##
## Core tests. ##
## ----------- ##
configure:1397: checking build system type
configure:1415: result: i686-pc-linux-gnu
configure:1423: checking host system type
configure:1437: result: i586-pc-linux-gnu
configure:1445: checking target system type
configure:1459: result: i586-pc-linux-gnu
configure:1495: checking for i586-pc-linux-gnu-gcc
configure:1511: found /usr/lib/distcc/bin/i586-pc-linux-gnu-gcc
configure:1521: result: i586-pc-linux-gnu-gcc
configure:1803: checking for C compiler version
configure:1806: i586-pc-linux-gnu-gcc --version </dev/null >&5
i586-pc-linux-gnu-gcc (GCC) 3.3.5 (Gentoo Linux 3.3.5-r1, ssp-3.3.2-3, pie-8.7.7.1)
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
configure:1809: $? = 0
configure:1811: i586-pc-linux-gnu-gcc -v </dev/null >&5
Reading specs from /usr/lib/gcc-lib/i586-pc-linux-gnu/3.3.5/specs
Configured with: /var/tmp/portage/gcc-3.3.5-r1/work/gcc-3.3.5/configure --enable-version-specific-runtime-libs --prefix=/usr --bindir=/usr/i586-pc-linux-gnu/gcc-bin/3.3.5 --includedir=/usr/lib/gcc-lib/i586-pc-linux-gnu/3.3.5/include --datadir=/usr/share/gcc-data/i586-pc-linux-gnu/3.3.5 --mandir=/usr/share/gcc-data/i586-pc-linux-gnu/3.3.5/man --infodir=/usr/share/gcc-data/i586-pc-linux-gnu/3.3.5/info --with-gxx-include-dir=/usr/lib/gcc-lib/i586-pc-linux-gnu/3.3.5/include/g++-v3 --host=i586-pc-linux-gnu --disable-altivec --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --with-system-zlib --disable-checking --disable-werror --disable-libunwind-exceptions --disable-multilib --disable-libgcj --enable-languages=c,c++,f77 --enable-shared --enable-threads=posix
Thread model: posix
gcc version 3.3.5 (Gentoo Linux 3.3.5-r1, ssp-3.3.2-3, pie-8.7.7.1)
configure:1814: $? = 0
configure:1816: i586-pc-linux-gnu-gcc -V </dev/null >&5
i586-pc-linux-gnu-gcc: `-V' option must have argument
distcc[12443] ERROR: compile (null) on localhost failed
configure:1819: $? = 1
configure:1843: checking for C compiler default output
configure:1846: i586-pc-linux-gnu-gcc -O2 -mcpu=i586 -fomit-frame-pointer -pipe conftest.c >&5
configure:1849: $? = 0
configure:1895: result: a.out
configure:1900: checking whether the C compiler works
configure:1906: ./a.out
configure:1909: $? = 0
configure:1926: result: yes
configure:1933: checking whether we are cross compiling
configure:1935: result: no
configure:1938: checking for suffix of executables
configure:1940: i586-pc-linux-gnu-gcc -o conftest -O2 -mcpu=i586 -fomit-frame-pointer -pipe conftest.c >&5
configure:1943: $? = 0
configure:1968: result:
configure:1974: checking for suffix of object files
configure:1996: i586-pc-linux-gnu-gcc -c -O2 -mcpu=i586 -fomit-frame-pointer -pipe conftest.c >&5
distcc[12483] ERROR: compile conftest.c on 192.168.1.9/2 failed with exit code 110
configure:1999: $? = 110
configure: failed program was:
| #line 1979 "configure"
| /* confdefs.h. */
|
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:2013: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
...
with the "verbose" mode i get a file-not-found error on the p4 (not found: i586-pc-linux-gnu, but there is a i686-pc-linux-gnu)
where is my bug??? |
|
| Back to top |
|
 |
TheX Guru


Joined: 31 Jul 2004 Posts: 349 Location: .de
|
Posted: Wed Mar 09, 2005 9:31 pm Post subject: |
|
|
this looks to me, as if you have not set the distccd correctly.
make sure that /etc/conf.d/distccd is set correctly .
for example you should have set
| Code: |
DISTCCD_OPTS="${DISTCCD_OPTS} --allow 192.168.1.0/24"
DISTCCD_NICE="1"
|
on the p4 machine.
and on the slow machine you should have to set the used hosts with
| Code: | | distcc-config --set-hosts 192.168.1.9 192.168.slow.machine |
(if 192.168.1.9 is the ip of the p4)
TheX |
|
| Back to top |
|
 |
AntonWert Apprentice

Joined: 06 Mar 2005 Posts: 177
|
Posted: Thu Mar 10, 2005 6:04 am Post subject: |
|
|
| TheX wrote: | this looks to me, as if you have not set the distccd correctly.
make sure that /etc/conf.d/distccd is set correctly .
for example you should have set
| Code: |
DISTCCD_OPTS="${DISTCCD_OPTS} --allow 192.168.1.0/24"
DISTCCD_NICE="1"
|
on the p4 machine.
and on the slow machine you should have to set the used hosts with
| Code: | | distcc-config --set-hosts 192.168.1.9 192.168.slow.machine |
(if 192.168.1.9 is the ip of the p4)
TheX |
well my settings differ a little bit, but i think they are also ok:
| Code: |
DISTCCD_OPTS="${DISTCCD_OPTS} --allow 192.168.1.7"
# 192.168.1.7 is the ip of the slow machine
DISTCCD_NICE="1"
|
and:
| Code: | | distcc-config --set-hosts 192.168.1.9 |
here i have only ihe ip of the fast machine, do i need the own too? |
|
| Back to top |
|
 |
TheX Guru


Joined: 31 Jul 2004 Posts: 349 Location: .de
|
|
| Back to top |
|
 |
ruben Guru

Joined: 04 Jul 2003 Posts: 462
|
Posted: Thu Mar 10, 2005 7:15 pm Post subject: |
|
|
Using only the other host (the p4) for compiling is just fine. The problem is what you saw with the verbose mode. The architecture of a P4 is a i686-pc-linux-gnu, while the old pentium is a i586-pc-linux-gnu, so i guess that it can't find the compiler.... although i don't remember having the same problem when doing just the same thing like you're doing now.
I guess you should check whether you have that executable on the old pentium and see if you have it on the P4. If you don't have it on the P4, then you can probably copy the necessary directories from the old pentium to some place in the P4, and then adjust /etc/init.d/distccd on the P4 so that it can find those executables in its path.
Hope this helps... |
|
| Back to top |
|
 |
rhumbliner n00b


Joined: 15 Nov 2004 Posts: 59 Location: Las Vegas
|
Posted: Mon Mar 14, 2005 1:46 pm Post subject: Same Distcc Problem |
|
|
I seem to be having a similar distcc problem. The odd thing is my distcc configuration used to work just fine. I have an old, slow i386 laptop that I built Gentoo on using distcc to speed the process up. The distcc server is an i686 but this never was a problem in the past. I just tried to run 'emerge -uD world' on my laptop and get the following error:
Could not run/locate "i386-pc-linux-gnu-gcc"
distcc[8336] ERROR: compile main.c on 192.168.0.11 failed
Any idea what's changed?
Thanks,
Tom |
|
| Back to top |
|
 |
jnicol n00b


Joined: 29 Jan 2003 Posts: 73 Location: Seattle, WA
|
Posted: Tue Mar 22, 2005 10:39 pm Post subject: |
|
|
Same here, this has recently stopped working.
Trying to compile for a P1-MMX, using P2 and P3 hosts. This used to work, but now dies with error 110 (compiler not found). Neither the p2 nor p3 has these files that the P1 does:
| Code: | /usr/bin/i586-pc-linux-gnu-gcc
/usr/lib/ccache/bin/i586-pc-linux-gnu-gcc
/usr/lib/distcc/bin/i586-pc-linux-gnu-gcc
/usr/i586-pc-linux-gnu/gcc-bin/3.3.5/i586-pc-linux-gnu-gcc-3.3.5
/usr/i586-pc-linux-gnu/gcc-bin/3.3.5/i586-pc-linux-gnu-gcc
|
So... why did this stop working, and how can I fix it? Can I just copy these files over? There doesn't seem to be a decent cross-compiling faq on gentoo.org.
[EDIT]
OK, I don't know why this stopped working, but here's my solution:
| Code: | | # CC="gcc" CXX="c++" emerge package |
Seems to work... |
|
| Back to top |
|
 |
3nd3r n00b


Joined: 25 Aug 2004 Posts: 38 Location: /dev/null
|
Posted: Sun Apr 10, 2005 7:10 am Post subject: |
|
|
| nobody figure this out yet? |
|
| Back to top |
|
 |
ali3nx l33t


Joined: 21 Sep 2003 Posts: 722 Location: Winnipeg, Canada
|
Posted: Sun Apr 10, 2005 7:16 am Post subject: |
|
|
you might check that all the distccd versions match. the current x86 and ~x86 distcc versions are incompatible and produce some wierd errors. I had to either pmask the newer version or keyword the older one so all hosts match. may be a related issue. _________________ Compiling Gentoo since version 1.4
Thousands of Gentoo Installs Completed
Emerged on every continent but Antarctica
Compile long and Prosper! |
|
| Back to top |
|
 |
3nd3r n00b


Joined: 25 Aug 2004 Posts: 38 Location: /dev/null
|
Posted: Sun Apr 10, 2005 7:18 am Post subject: |
|
|
I know on mine they do.
however it bitches about not being able to find i386 bla bla
however his quick fix works |
|
| Back to top |
|
 |
bigfunkymo Apprentice


Joined: 23 Jan 2004 Posts: 237
|
Posted: Thu Apr 21, 2005 8:27 pm Post subject: |
|
|
sounds like your faster computer doesn't have i386 gcc installed but rather i686 gcc... I don't really know how to get it working but I'm having similar issues myself and I think that is the cause. _________________ [No package... Grabbing a set.] |
|
| Back to top |
|
 |
step Apprentice


Joined: 16 May 2002 Posts: 198
|
Posted: Thu Apr 28, 2005 9:48 am Post subject: |
|
|
same problem here.
distcc used to work just fine.
i have 2 PC's
PC A is a fast P4 and then this PC B that is old and slow laptop.
A is 192.168.0.3 and B is 192.168.0.5
no i am trying to compile sys-devel/libtool (or any other pkg)
and it is not possible if i uncomment the FEATURES="distcc" on B
(B)
tail /var/log/distcc
exec on 192.168.0.3/10: i486-pc-linux-gnu-gcc -c -O3 -mcpu=i686 -funroll-loops -pipe conftest.c -o conftest.o
distcc[16177] (dcc_collect_child) cpp times: user 0.025996s, system 0.013997s, 926 minflt, 0 majflt
distcc[16177] cpp conftest.c on localhost completed ok
distcc[16177] 123 bytes from conftest.c compiled on 192.168.0.3 in 0.0533s, rate 2kB/s
distcc[16177] ERROR: compile conftest.c on 192.168.0.3/10 failed with exit code 110
distcc[16177] elapsed compilation time 0.064732s
distcc[16177] (dcc_exit) exit: code 110; self: 0.007998 user 0.009998 sys; children: 0.025996 user 0.013997 sys
looks like the problem is i486-pc-linux-gnu-gcc
PC A is missing this file it has i686-pc-linux-gnu-gcc
edit:
BTW, some say that the problem is in binutils? : https://forums.gentoo.org/viewtopic-t-324479.html |
|
| Back to top |
|
 |
dark blue n00b

Joined: 17 Jan 2004 Posts: 8
|
|
| Back to top |
|
 |
Bob P Advocate


Joined: 20 Oct 2004 Posts: 3355 Location: Jackass! Development Labs
|
Posted: Sat Apr 30, 2005 7:16 pm Post subject: |
|
|
i have a "Farm" comprised of a variety of x86 platfrom boxes on a LAN. the boxes include all varieties of x86 supported by gentoo, and if you follow the directions, distcc works properly in such an environment. maybe you missed a subtlety that's present in the docs:
| Gentoo distcc documentation wrote: |
Recent Portage updates have made Portage use ${CHOST}-gcc instead of gcc. This means that if you're mixing i686 machines with other types (i386, i586) you will run into problems. A workaround for this may be to export CC='gcc' CXX='c++' or to put it in /etc/make.conf, but that needs testing. If it works for you please email me, Lisa Seelye. |
i hate to say it, but this is one of those RTM situations. _________________ .
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks |
|
| Back to top |
|
 |
bigfunkymo Apprentice


Joined: 23 Jan 2004 Posts: 237
|
Posted: Sun May 01, 2005 4:49 pm Post subject: |
|
|
The biggest problem I'm having with distcc is it always fails while doing the kernel but I've pretty much given up on that for now. I've tried to migrate my systems to the hardened profile and I have one system that is running hardened-i386 since installation but I have changed CHOST to reflect an i686 system and then used
| Code: | | # emerge glibc binutils gcc && emerge world -e |
to rebuild all my binaries.
Is it possible to change a non-hardened machine to a hardened without running into problems like this? Does it require the use setting "hardened" as well as updating the make.profile link to a hardened profile? _________________ [No package... Grabbing a set.] |
|
| Back to top |
|
 |
|