distcc and ccache

AthlonRob · n00b Joined: 19 Jan 2003 Posts: 37

I'm pulling my hair out here and think I need a few pointers... :-)

I want to use distcc and ccache because I think I'm going to have to do a lot of compiling in order to get java working properly.

The first thread I found just said I needed to add CC='distcc' and CXX='distcc g++' (and the servers line) to my make.conf file... that was, unfortunately, ignored by portage. So I started getting a little more in depth. I added the CC and CXX values to the MAKEOPTS line - but that caused:

AlterEgo · Veteran Joined: 25 Apr 2002 Posts: 1619

https://forums.gentoo.org/viewtopic.php?p=92735#92735

Useful trick (compiling the kerrnel), so can can see whether disctcc actually works, without worrying about make.conf.

I also needed this tip,
and this one make make it all work smoothly.

But java: I doubt whether distcc works when compiling java.

AthlonRob · n00b Joined: 19 Jan 2003 Posts: 37

I must be completely losing my mind.

I emerged distcc

I added:

AlterEgo · Veteran Joined: 25 Apr 2002 Posts: 1619

Strange

All I can say is, it works for me.

Please go back one step, and test whether your basic distcc-setup works, by testing it during a kernel build(which is make.conf-independent).
That will at least help us to pinpoint the problem.

Code:
# make menuconfig
# make dep && make clean
# export DISTCC_HOSTS="....."
# make CC="distcc" -j3 bzImage
# make CC="distcc" -j3 modules
# make modules_install
# [copy your kernel, etc. etc.]

If this works, you know for sure distcc works. (and that's something)

Also, you can try and run the distcc-daemon (that does not work when run as root (!)) as a normal user on all machines, and tail the output for possible clues:
distccd --verbose --daemon log-file=/home/<yourname>/distccd.log
tail -f /home/<yourname>/distccd.log

AthlonRob · n00b Joined: 19 Jan 2003 Posts: 37

I'm sorry, I meant to say (hell, I said everything else...) that distcc *was* working, by itself.

I kludged it and got it working a few minutes ago, now.

Don't ask me why, 'cause I franky don't know... lol :-)

I set my MAKEOPTS line to:

AthlonRob · n00b Joined: 19 Jan 2003 Posts: 37

AlterEgo · Veteran Joined: 25 Apr 2002 Posts: 1619

Great you finally got it working

I thought it would not work for java. I'm not sure if one can do things like distcc to a java-compiler. On the other hand: why not ? (but how?)

I could not get distcc to work properly with OpenOffice.

AthlonRob · n00b Joined: 19 Jan 2003 Posts: 37

I think OpenOffice uses the java compiler too, doesn't it?

If we could just force it to use distcc instead of g++, it should be fine... I've only run in to one thing that bails out with distcc and that may be because one of my distccd servers is on GCC 3.2.0 vs 3.2.1....

I just joined the distcc mailing list... perhaps I'll ask them about working with the java compiler, too.

Rob

contigab · n00b Joined: 18 Dec 2002 Posts: 57 Location: Italy

i have made it to work in the following way:

edit file /etc/env.d/05gcc and change/add the lines
CC="distcc gcc"
CXX="distcc g++"
DISTCC_HOSTS="host1 host2 ... "

and then env-update

you may want to edit make.conf to set
MAKEOPTS="-j4" (i have 2 cpu's)

In this way the CC and GCC values are assumed to be the standard one for the distribution and they will never be overwritten.

As a drawback you have that you will ALWAYS use distcc now, in order to compile locally you have to switch back to your old 05gcc file.

By the way, profile.env (file which holds config values) is built from the files included in env.d so changing it directly is useless, it will be automatically overwritten.
_________________
Linux!

stig · Posted: Wed Feb 05, 2003 3:04 pm Post subject:

I find this thread most useful, thogh I still experience som problems making distcc work properly.

Here is a little output (relevant parts):

TwoSlick · Posted: Thu Feb 06, 2003 6:38 am Post subject:

It appears that portage has just been updated to use distcc as well as ccache features. I just tried it out, and it works GREAT, and EASILY....

Here's how to do it in a few simple steps.

1. If you modified your /etc/env.d/05gcc, change it back to it's original form, or your programs won't compile. Change the lines back to:

stig · Posted: Thu Feb 06, 2003 9:47 am Post subject:

This almost sounded like magic

I was woundering which version of protage you're talking about?
After emerging ccache, it says that:

georgz · Posted: Thu Feb 06, 2003 11:19 am Post subject: distcc doesn't work anymore

I'm abit stuck, my distcc doesn't work anymore.

stig · Posted: Thu Feb 06, 2003 12:06 pm Post subject:

I have almost the same problem - when the client connects to the server, gcc (or in your case cc) is nowhere to be found.
Here is mine:

georgz · Posted: Thu Feb 06, 2003 1:16 pm Post subject:

Works again!

On the second machine I had started distccd with /etc/init.d/distccd start.
Then it runs as user nobody.

When I start distccd as oridinary user it works fine:
/usr/bin/distccd --verbose --log-file=/tmp/distccd.log --daemon

Now the question to find out is why doesn't it work as nobody?

ccpetersen · n00b Joined: 11 Jun 2002 Posts: 25

TwoSlick · Posted: Thu Feb 06, 2003 2:58 pm Post subject:

georgz · Posted: Thu Feb 06, 2003 3:03 pm Post subject:

ccpetersen: The thing is that this is in the startup file:
[

ccpetersen · n00b Joined: 11 Jun 2002 Posts: 25

What's the output of `which gcc`?
and `gcc-config --get-bin-path`.

georgz · Posted: Thu Feb 06, 2003 3:22 pm Post subject:

ccpetersen · n00b Joined: 11 Jun 2002 Posts: 25

I can't see anything that's obviously wrong. I take it your running distcc 1.1 (~x86) not distcc 0.15. If you are running distcc 0.15 then /usr/bin/gcc shouldn't be there.

Other than that the setup you describe works here.

charlesnadeau

tuxwatcher

I was having the same reset by peer problem. I checked the syslog on the peer machine and it showed I was having permission problems in the /tmp directory. I went and deleted the existing distcc directories under /tmp on that peer, tried compiling again, and everything worked fine.

charlesnadeau

tuxwatcher

The errors I had were showing up in the /var/log/messages log on the machine distcc was trying to connect too. Emerging distcc again did not help because it didn't clear the temporary files in /tmp.