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 15:17:43 -0400 [thread overview]
Message-ID: <pan.2006.04.11.19.17.41.298610@novazur.fr> (raw)
In-Reply-To: 1144779958.14010.1.camel@inertia.twi-31o2.org
Le Tue, 11 Apr 2006 14:25:58 -0400, Chris Gianelloni a écrit :
> What do you mean that it doesn't use distcc?
Only localhost[0] is used.
> How do you know?
#
DISTCC_DIR="/sauve_loc/catalyst2/tmp/default/livecd-stage1-i586-cp20060411/var/tmp/portage/.distcc/"
distccmon-text 1 | grep -v "^$"
only gives lines like :
922 Compile pngpread.tmp.KanelXP.918.i localhost[0]
nothing else.
> Have you increased MAKEOPTS anywhere?
No :-(
Before, I had a catalyst-env.sh
(envscript="/etc/catalyst2/catalyst-env.sh") with :
export MAKEOPTS="-j7"
export LINGUAS="fr"
export LANGUAGE="FREN"
but, as it doesn't work.
I always have errors :
cd ../obj_s; i586-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I../ncurses -I/var/tmp/portage/ncurses-5.4-r6/work/ncurses-5.4/ncurses -I/var/tmp/portage/ncurses-5.4-r6/work/ncurses-5.4/ncurses/../include -I. -I../include -D_GNU_SOURCE -DNDEBUG -O2 -march=i586 -pipe -fPIC -c /var/tmp/portage/ncurses-5.4-r6/work/ncurses-5.4/ncurses/base/lib_chgat.c
distcc[13193] ERROR: compile /var/tmp/portage/ncurses-5.4-r6/work/ncurses-5.4/ncurses/tty/hashmap.c on 192.168.0.101 failed with exit code 110
make[1]: *** [../obj_s/hashmap.o] Error 110
make[1]: *** Waiting for unfinished jobs....
distcc[13246] ERROR: compile /var/tmp/ccache/lib_bkgd.tmp.KanelXP.13204.i on 192.168.0.101 failed with exit code 110
distcc[13204] ERROR: compile /var/tmp/portage/ncurses-5.4-r6/work/ncurses-5.4/ncurses/base/lib_bkgd.c on 192.168.0.101 failed with exit code 110
make[1]: *** [../obj_s/lib_bkgd.o] Error 110
make: *** [all] Error 2
!!! ERROR: sys-libs/ncurses-5.4-r6 failed.
!!! Function do_compile, Line 89, Exitcode 2
!!! make failed
!!! If you need support, post the topmost build error, NOT this status message.
seems du to distcc, no ?
That's why I removed envscript=, but I may forgot the MAKEOPTS.
What is the right way to define this MAKEOPTS ?
> Remember that the default MAKEOPTS is -j2,
> which is unlikely to distribute very far... ;]
Of course, sorry.
--
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list
next prev parent reply other threads:[~2006-04-11 19:17 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 ` Christophe PEREZ [this message]
2006-04-11 19:35 ` [gentoo-catalyst] " Christophe PEREZ
2006-04-11 20:07 ` Christophe PEREZ
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.19.17.41.298610@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