aMule Forum
English => Compilation problems => Topic started by: thedude0001 on March 18, 2005, 04:59:04 PM
-
And another problem... :D
I used to use distcc to speed up amule compilation. This worked very good for me for quite some time now, but today it chose to produce errors concernig the ed2k link handler. I use "make -j4 CC=distcc CXX=distcc" to compile. If I make clean and compile it without distcc everything works fine. If I configure --disable-ed2k everything works fine with distcc.
Here's the compiler output:
-
Hum, you can try make clean first then make, but it seems more probable to me that you are linking against a library with the wrong abi, is this possible? Maybe this compiler is old and is trying to use a newer library?
-
I did a make clean between tests (and just did it again, just to be sure, I know myself... :D ).
Originally posted by phoenix
but it seems more probable to me that you are linking against a library with the wrong abi, is this possible? Maybe this compiler is old and is trying to use a newer library?
Uhm, I'm not too sure what you are talking about, my knowledge leaves me here. :rolleyes:
distcc is not a compiler, it just distributes compilations across different hosts. You can take a look at it here: http://distcc.samba.org/
The two computers involved here are a Duron 1200 (where amule is running) and an Athlon 2400+, both have Gentoo installed and have the exact same toolchain installed (gcc 3.4.3-20050110). And I use distcc to emerge everything on these two and one other computer and never had such problems...
-
Ok, if you say both have exactly the same toolchain, forget what i said.
Isnt there a difference between the way you are compiling you wx lib in the two machines? Maybe in one place you have --use-stl and not on the other?
-
Uhm, the second machine doesn't have wx installed (and never had). And distcc doesn't need them for compilation. I use it for KDE / QT compilations distributed to hosts that don't have QT installed. Here's a bit from their homepage:
distcc is a program to distribute builds of C, C++, Objective C or Objective C++ code across several machines on a network. distcc should always generate the same results as a local build, is simple to install and use, and is usually much faster than a local compile.
distcc does not require all machines to share a filesystem, have synchronized clocks, or to have the same libraries or header files installed. They can even have different processors or operating systems, if cross-compilers are installed.
[...]
distcc sends the complete preprocessed source code across the network for each job, so all it requires of the volunteer machines is that they be running the distccd daemon, and that they have an appropriate compiler installed.
I'm not too sure about how a compiler works and where and when libraries are needed for compilation, but I think distcc should work without the libraries being present on the machines work is distributed to.