| View previous topic :: View next topic |
| Author |
Message |
jza
Tux's lil' helper
Joined: 27 Jun 2004
Posts: 87
Location: U.S.A
|
 Posted: Sat Jul 17, 2004 7:42 pm Post subject: error using distcc during bootstrap |
 |
|
I am getting the follwing error during bootstrap: | Code: |
>>> version.h compiled successfully.
>>> Source unpacked.
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-sys-kernel_-_linux-headers-2.4.21-r1-12635.log"
open_wr: /.distcc/lock/cpu_localhost_0
open_wr: /.distcc/state/binstate_12710
unlink: /.distcc/state/binstate_12710
open_wr: /.distcc/lock/cpu_localhost_0
open_wr: /.distcc/state/binstate_12756
unlink: /.distcc/state/binstate_12756
----------------------------------------
|
I made sure that the distccd was on in both of my other systems and this is my make.conf:
| Code: |
CFLAGS="-O3 -pipe -march=pentium3 -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CXXFLAGS="${CFLAGS}"
FEATURES="distcc"
DISTCC_DIR="${PORTAGE_TMPDIR}/.distcc"
MAKEOPTS="-j3"
PORTAGE_TMPDIR=/var/tmp
USE="kde gtk -gnome dvd cdr"
|
any suggestions?[/code] |
|
| Back to top |
|
 |
Warhead
Tux's lil' helper
Joined: 09 Oct 2003
Posts: 122
Location: Verden, near Bremen, Germany
|
| Posted: Sun Jul 18, 2004 3:13 pm Post subject: |
|
|
I have the same problem. It seems, that distcc is working, since /var/log/messages on my other machines states, that they compiled distcc packages, but I get the same acces violation summary. I noticed, that PORTAGE_TMPDIR and DISTCC_DIR are not set on the problematic machine, echo $PORTAGE_TMPDIR or echo $DISTCC_DIR both return an empty line in the console. When I set the variables manually using the export command, compilation is successfull but distcc in not doing anything (no distcc packages sent to other machines).
The really strage thing is, that on my two other working machines distcc ist working, although DISTCC_DIR and PORTAGE_TMPDIR are not set on these either!!
I am more and more convinced, that this problem ist due to my machine, since it is the third computer I have installed gentoo on, and it is causing so much trouble on several issues that went on smoothly on the other computers.
Regards
Kolja
_________________
To Rome said Nero: "If to smoke you turn
I shall not cease to fiddle while you burn."
To Nero Rome replied: "Pray do your worst,
'Tis my excuse that you were fiddling first."
--Orm Pludge |
|
| Back to top |
|
|
slobba
n00b
Joined: 20 Mar 2004
Posts: 34
Location: Sydney, Australia
|
| Posted: Mon Jul 19, 2004 8:40 am Post subject: |
|
|
You could try:
| Code: |
FEATURES="-sandbox distcc"
|
in your make.conf file (note the negative sign before sandbox). I'm not sure exactly what the sandbox feature does but the turning it off removed these errors for me. |
|
| Back to top |
|
|
Warhead
Tux's lil' helper
Joined: 09 Oct 2003
Posts: 122
Location: Verden, near Bremen, Germany
|
| Posted: Mon Jul 19, 2004 2:45 pm Post subject: |
|
|
I will shurely give that a try. But it is very strange that distcc does not care about the variable set in /etc/make.conf regarding the distcc directory, isn' t it?
Is there anything else to do, after changeing the make.conf?
Regards
Kolja
_________________
To Rome said Nero: "If to smoke you turn
I shall not cease to fiddle while you burn."
To Nero Rome replied: "Pray do your worst,
'Tis my excuse that you were fiddling first."
--Orm Pludge |
|
| Back to top |
|
|
Warhead
Tux's lil' helper
Joined: 09 Oct 2003
Posts: 122
Location: Verden, near Bremen, Germany
|
| Posted: Mon Jul 19, 2004 4:28 pm Post subject: |
|
|
Setting the DISTCC_DIR manually using the 'export' command solved the problem?
But since I do not want to set the variable everytime I boot the machine by hand, I would be quite interesting, why that setting is not taken from /etc/make.conf
Regards
Kolja
_________________
To Rome said Nero: "If to smoke you turn
I shall not cease to fiddle while you burn."
To Nero Rome replied: "Pray do your worst,
'Tis my excuse that you were fiddling first."
--Orm Pludge |
|
| Back to top |
|
|
jfave
Tux's lil' helper
Joined: 28 Jul 2004
Posts: 96
Location: Jacksonville, FL
|
| Posted: Tue Aug 03, 2004 6:47 am Post subject: |
|
|
| any answer to this? just received same error |
|
| Back to top |
|
|
jnicol
n00b
Joined: 29 Jan 2003
Posts: 73
Location: Seattle, WA
|
| Posted: Fri Dec 24, 2004 4:51 pm Post subject: |
|
|
bump...
Using 2004.3-r1, and distcc, bootstrap.sh dies thusly:
| Code: |
>>> version.h compiled successfully.
>>> Source unpacked.
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE = "/tmp/sandbox-sys-kernel_-_linux-headers-2.4.21-r1-9081.log"
open_wr: /.distcc/lock/cpu_localhost_0
open_wr: /.distcc/state/binstate_9151
unlink: /.distcc/state/binstate_9151
open_wr: /.distcc/lock/cpu_localhost_0
open_wr: /.distcc/state/binstate_9197
unlink: /.distcc/state/binstate_9197
--------------------------------------------------------------------------------
|
Any thoughts? Perhaps the bootstrap script and/or the handbook need an update? I'm trying with USE="-sandbox" now...
UPDATE: "USE="-sandbox" did nothing.
UPDATE 2: I went back to make.conf and uncommented all the portage directories. I'm guessing it was PORTAGE_TMPDIR=/var/tmp that was important. I also had to:
| Code: | # mkdir /usr/local/portage
# mkdir /var/log/portage |
Now everything seems happy. |
|
| Back to top |
|
|
|
Installing Gentoo
