| View previous topic :: View next topic |
| Author |
Message |
ddriver
n00b
Joined: 24 Feb 2005
Posts: 67
|
 Posted: Wed Feb 25, 2015 7:01 pm Post subject: distcc stopped working mid-build |
 |
|
I am doing updates on my Raspberry Pi - a slow job. I decided to implement distcc and crossdev so that I could offload some work to my 6 core AMD x64 machine. Found some howtos and wikis and apparently got it all working.
Kicked off an emerge, and after the painfully slow extraction process it started firing compilations off to the other machine, cracking through them pretty quickly. All good I thought. However, when I returned to it a while later I found that now the compilations are taking place locally and not being distributed at all. 6 hours later it's still going - slooooooowly. The ebuild I am trying to update is gcc-4.8.3.
Is this a known issue, that something happens to stop distcc working? Any ideas where I should be looking to find the problem? |
|
| Back to top |
|
 |
szatox
Advocate
Joined: 27 Aug 2013
Posts: 3136
|
| Posted: Wed Feb 25, 2015 7:17 pm Post subject: |
|
|
| Quote: | | The ebuild I am trying to update is gcc-4.8.3. |
I think this one is the reason.
Some packages consider themselves critical* and disable ditcc to prevent breaknig your system. AFAIR glibc is another one of those. Use this time to read a book. Or take your gf out 
* really. You don't want to be stuck witohut gcc on gentoo. Or libc, whichever one you use.
Last edited by szatox on Wed Feb 25, 2015 7:18 pm; edited 1 time in total |
|
| Back to top |
|
|
eccerr0r
Watchman
Joined: 01 Jul 2004
Posts: 9679
Location: almost Mile High in the USA
|
| Posted: Wed Feb 25, 2015 7:18 pm Post subject: |
|
|
The problem is that gcc stage2/3 must run on the target platform, which can't distcc. Even on x86 with distcc this doesn't happen. Can't do much about it, though it would be nice if it were possible to say gcc is done at the end of stage 1. Best bet with Gentoo is make sure you have make options limit load, else you could be thrashing.
Gcc should be the only problematic package due to this constraint (though there are packages with makefile bugs and can only be compiled single threaded). LLVM may be another one if it isn't already.
6 hours... sounds as bad as when I first compiled gcc on a 33MHz Sparc clone with 8MB RAM...
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
| Back to top |
|
|
ddriver
n00b
Joined: 24 Feb 2005
Posts: 67
|
| Posted: Wed Feb 25, 2015 7:29 pm Post subject: |
|
|
6 hours - SO FAR! I canned the previous attempt without distcc on about 21 hours. I don't suppose it really matters how long it takes. Thanks people for the reassurance that it's only a couple of packages that will give me this issue.
And thanks for the suggestion of taking my gf out, but I don't think my wife would be too impressed about that idea. |
|
| Back to top |
|
|
|
Portage & Programming
