From: Christophe PEREZ <christophe.perez@novazur.com>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] Re: problem with distcc
Date: Tue, 11 Apr 2006 16:07:36 -0400 [thread overview]
Message-ID: <pan.2006.04.11.20.07.35.26586@novazur.fr> (raw)
In-Reply-To: pan.2006.04.11.19.35.57.483294@novazur.fr
Le Tue, 11 Apr 2006 15:35:57 -0400, Christophe PEREZ a écrit :
> I ask all of that because that's how I started yesterday, but stage1 build
> failed during the night...
I tried again, with
# cat stage1-060410.spec
subarch: i586
target: stage1
version_stamp: 20060410
rel_type: default
profile: default-linux/x86/2006.0
snapshot: 20060410
source_subpath: stage3-i586-2006.0
distcc_hosts: localhost 192.168.0.101 192.168.0.201 192.168.0.30 192.168.0.6
And it fails during the first compile :
>>> emerge (1 of 66) sys-devel/patch-2.5.9 to /
[...]
i586-pc-linux-gnu-gcc -c -DHAVE_CONFIG_H -Ded_PROGRAM=\"ed\" -I. -I. -O2 -march=i586 -pipe -DLINUX -D_XOPEN_SOURCE=500 getopt.c
i586-pc-linux-gnu-gcc -c -DHAVE_CONFIG_H -Ded_PROGRAM=\"ed\" -I. -I. -O2 -march=i586 -pipe -DLINUX -D_XOPEN_SOURCE=500 getopt1.c
distcc[8533] ERROR: compile /var/tmp/ccache/addext.tmp.KanelXP.8506.i on 192.168.0.101 failed with exit code 110
distcc[8506] ERROR: compile addext.c on 192.168.0.101 failed with exit code 110
make: *** [addext.o] Error 110
make: *** Waiting for unfinished jobs....
distcc[8538] ERROR: compile /var/tmp/ccache/backupfile.tmp.KanelXP.8513.i on 192.168.0.101 failed with exit code 110
distcc[8542] ERROR: compile /var/tmp/ccache/argmatch.tmp.KanelXP.8510.i on 192.168.0.101 failed with exit code 110
distcc[8537] ERROR: compile /var/tmp/ccache/getopt.tmp.KanelXP.8517.i on 192.168.0.201 failed with exit code 110
distcc[8517] ERROR: compile getopt.c on 192.168.0.201 failed with exit code 110
make: *** [getopt.o] Error 110
!!! ERROR: sys-devel/patch-2.5.9 failed.
!!! Function src_compile, Line 29, Exitcode 2
!!! emake failed
!!! If you need support, post the topmost build error, NOT this status message.
!!! catalyst: run script failed.
I'll try again without distcc for building stage1.
But, if it works, I'm curious to know the real right way to do it ?
--
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list
next prev parent reply other threads:[~2006-04-11 20:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 15:12 [gentoo-catalyst] problem with distcc Christophe PEREZ
2006-04-11 18:25 ` Chris Gianelloni
2006-04-11 19:17 ` [gentoo-catalyst] " Christophe PEREZ
2006-04-11 19:35 ` Christophe PEREZ
2006-04-11 20:07 ` Christophe PEREZ [this message]
2006-04-11 20:12 ` Andrew Gaffney
2006-04-11 20:36 ` [gentoo-catalyst] " Christophe PEREZ
2006-04-11 20:22 ` [gentoo-catalyst] " Chris Gianelloni
2006-04-11 20:39 ` [gentoo-catalyst] " Christophe PEREZ
2006-04-11 20:57 ` Christophe PEREZ
2006-04-11 21:45 ` Chris Gianelloni
2006-04-11 22:02 ` [gentoo-catalyst] " Christophe PEREZ
2006-04-12 13:48 ` Chris Gianelloni
2006-04-12 15:51 ` [gentoo-catalyst] " Christophe PEREZ
2006-04-12 20:12 ` Chris Gianelloni
2006-04-12 21:07 ` [gentoo-catalyst] " Christophe PEREZ
2006-04-12 21:34 ` Christophe PEREZ
2006-04-13 13:06 ` Chris Gianelloni
2006-04-13 13:59 ` [gentoo-catalyst] " Christophe PEREZ
2006-04-13 15:59 ` Christophe PEREZ
2006-04-11 20:01 ` Andrew Gaffney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pan.2006.04.11.20.07.35.26586@novazur.fr \
--to=christophe.perez@novazur.com \
--cc=gentoo-catalyst@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox