* [gentoo-catalyst] problem with distcc
@ 2006-04-11 15:12 Christophe PEREZ
2006-04-11 18:25 ` Chris Gianelloni
0 siblings, 1 reply; 21+ messages in thread
From: Christophe PEREZ @ 2006-04-11 15:12 UTC (permalink / raw
To: gentoo-catalyst
Hi,
Back to the list after nearly one year (Hi chris ! :-) ).
Today, I'm trying to make another livecd.
I've tried first to build something complete, like I have done the first
time : my snapshot, my stage1 etc... But I was already stopped on stage1.
So, I tried something more "normal", using gentoo stage3 + portage
snapshot to build my livecd-stage1 :
http://mirror.datapipe.net/gentoo/releases/x86/2006.0/stages/stage3-i586-2006.0.tar.bz2
http://mirror.datapipe.net/gentoo/releases/snapshots/2006.0/portage-20060123.tar.bz2
It seems to build correctly, but it doesn't use distcc, and I'd
like a lot to use it to win time.
Version : dev-util/catalyst-2.0_rc41
/etc/catalyst2.conf :
distdir="/usr/portage/distfiles"
options="autoresume ccache kerncache pkgcache seedcache snapcache distcc"
sharedir="/usr/lib/catalyst2"
storedir="/sauve_loc/catalyst2"
snapshot_cache="/sauve_loc/catalyst2/snapshot_cache"
hash_function="md5"
digests="md5 sha1"
My livecd-stage1 :
subarch: i586
version_stamp: cp20060411
target: livecd-stage1
rel_type: default
profile: default-linux/x86/2006.0
snapshot: 20060123
source_subpath: stage3-i586-2006.0
distcc_hosts: localhost 192.168.0.101 192.168.0.201 192.168.0.30
portage_confdir: /etc/catalyst2/portage
livecd/use:
-*
X
gtk
ipv6
socks5
livecd
fbcon
ssl
a52
aac
aalib
acpi
alsa
audiofile
avi
bash-completion
bitmap-fonts
bmp
bonobo
cdb
cdparanoia
cdr
crypt
curl
dvd
dvdr
dvdread
exif
ffmpeg
flac
gif
gphoto2
gtk2
gtkhtml
hal
imagemagick
imlib
java
jpeg
libg++
libwww
mad
matroska
mmx
mng
mp3
mpeg
ncurses
odbc
ogg
oggvorbis
opengl
oss
perl
png
sdl
sox
spell
speex
sse
svga
theora
tiff
truetype
truetype-fonts
type1-fonts
unicode
usb
v4l
vorbis
wmf
xinerama
xmms
xpm
xv
xvid
linguas_fr
livecd/packages:
baselayout
livecd-tools
module-init-tools
dhcpcd
acpid
gentoo-sources
coldplug
fxload
dosfstools
ntfsprogs
nfs-utils
usbutils
pciutils
e2fsprogs
pwgen
rp-pppoe
penggy
iputils
hwsetup
pptpclient
ethtool
wireless-tools
prism54-firmware
wpa_supplicant
genkernel
less
xorg-x11
pkgconfig
aspell-fr
alsa-utils
grisbi
blackdown-jdk
openoffice-bin
ntp
ivman
xfce4
xfce4-extras
liferea
rox
gftp
gedit
gpdf
eog
gimp
gqview
grip
gaim
xbindkeys
realplayer
libstdc++-v3
mozilla-firefox
evolution
pan
xmms
mplayer
mplayerplug-in
# ls -l /sauve_loc/catalyst2/snapshots/portage-20060123.tar.bz2 /sauve_loc/catalyst2/builds/stage3-i586-2006.0.tar.bz2
-rw-r--r-- 1 root root 104713233 fév 25 16:24 /sauve_loc/catalyst2/builds/stage3-i586-2006.0.tar.bz2
-rw-r--r-- 1 root root 22597458 mar 19 10:51 /sauve_loc/catalyst2/snapshots/portage-20060123.tar.bz2
Thanks in advance.
PS : and always sorry for my bad english.
--
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-catalyst] problem with distcc
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
0 siblings, 1 reply; 21+ messages in thread
From: Chris Gianelloni @ 2006-04-11 18:25 UTC (permalink / raw
To: gentoo-catalyst
[-- Attachment #1: Type: text/plain, Size: 481 bytes --]
On Tue, 2006-04-11 at 11:12 -0400, Christophe PEREZ wrote:
> It seems to build correctly, but it doesn't use distcc, and I'd
> like a lot to use it to win time.
What do you mean that it doesn't use distcc? How do you know? Have you
increased MAKEOPTS anywhere? Remember that the default MAKEOPTS is -j2,
which is unlikely to distribute very far... ;]
--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-catalyst] Re: problem with distcc
2006-04-11 18:25 ` Chris Gianelloni
@ 2006-04-11 19:17 ` Christophe PEREZ
2006-04-11 19:35 ` Christophe PEREZ
2006-04-11 20:01 ` Andrew Gaffney
0 siblings, 2 replies; 21+ messages in thread
From: Christophe PEREZ @ 2006-04-11 19:17 UTC (permalink / raw
To: gentoo-catalyst
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
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-catalyst] Re: problem with distcc
2006-04-11 19:17 ` [gentoo-catalyst] " Christophe PEREZ
@ 2006-04-11 19:35 ` Christophe PEREZ
2006-04-11 20:07 ` Christophe PEREZ
2006-04-11 20:01 ` Andrew Gaffney
1 sibling, 1 reply; 21+ messages in thread
From: Christophe PEREZ @ 2006-04-11 19:35 UTC (permalink / raw
To: gentoo-catalyst
Le Tue, 11 Apr 2006 15:17:43 -0400, Christophe PEREZ a écrit :
> seems du to distcc, no ?
Maybe because of gcc versions ?
3.3.4 in stage3 and 3.4.5-r1 on my machines ?
So, what is the solution ?
build my own stage1/stage2/stage3 to have the same gcc ?
And, have I to disable distcc to build stage1 ?
When will I enable it ? for stage2 build ?
I ask all of that because that's how I started yesterday, but stage1 build
failed during the night...
--
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-catalyst] Re: problem with distcc
2006-04-11 19:17 ` [gentoo-catalyst] " Christophe PEREZ
2006-04-11 19:35 ` Christophe PEREZ
@ 2006-04-11 20:01 ` Andrew Gaffney
1 sibling, 0 replies; 21+ messages in thread
From: Andrew Gaffney @ 2006-04-11 20:01 UTC (permalink / raw
To: gentoo-catalyst
Christophe PEREZ wrote:
> distcc[13246] ERROR: compile /var/tmp/ccache/lib_bkgd.tmp.KanelXP.13204.i on 192.168.0.101 failed with exit code 110
This usually means that it can't find the compiler named by the client. Is the
CHOST on 192.168.0.101 different that that of the catalyst build you're doing?
If so, you need to build a cross-compiler (or just create some symlinks if it's
the same arch (all x86)).
--
Andrew Gaffney http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer Installer Project
--
gentoo-catalyst@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-catalyst] Re: problem with distcc
2006-04-11 19:35 ` Christophe PEREZ
@ 2006-04-11 20:07 ` Christophe PEREZ
2006-04-11 20:12 ` Andrew Gaffney
2006-04-11 20:22 ` [gentoo-catalyst] " Chris Gianelloni
0 siblings, 2 replies; 21+ messages in thread
From: Christophe PEREZ @ 2006-04-11 20:07 UTC (permalink / raw
To: gentoo-catalyst
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
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-catalyst] Re: problem with distcc
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
1 sibling, 1 reply; 21+ messages in thread
From: Andrew Gaffney @ 2006-04-11 20:12 UTC (permalink / raw
To: gentoo-catalyst
Christophe PEREZ wrote:
> 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
You know, it doesn't make much sense to build an up to date stage1. A stage1
install recompiles everything anyway, so why not just use the 2006.0 stage1 tarball?
As for your actual problem, it's because you're using a i586-pc-linux-gnu CHOST
for the catalyst build while (I bet) all of your distcc helpers are
i686-pc-linux-gnu. When the build is distributed, it'll look for
i586-pc-linux-gnu-gcc, which won't exist on the helpers, which will return a
code 110.
--
Andrew Gaffney http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer Installer Project
--
gentoo-catalyst@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-catalyst] Re: problem with distcc
2006-04-11 20:07 ` Christophe PEREZ
2006-04-11 20:12 ` Andrew Gaffney
@ 2006-04-11 20:22 ` Chris Gianelloni
2006-04-11 20:39 ` [gentoo-catalyst] " Christophe PEREZ
1 sibling, 1 reply; 21+ messages in thread
From: Chris Gianelloni @ 2006-04-11 20:22 UTC (permalink / raw
To: gentoo-catalyst
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
On Tue, 2006-04-11 at 16:07 -0400, Christophe PEREZ wrote:
> 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 ?
It works perfectly provided you have;
same compiler versions
same compiler names
What this means is for you to build a CHOST=i586-pc-linux-gnu machine,
you are *required* to have a cross-compiler that is named
i586-pc-linux-gnu-gcc on each of your distcc slaves.
--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-catalyst] Re: Re: problem with distcc
2006-04-11 20:12 ` Andrew Gaffney
@ 2006-04-11 20:36 ` Christophe PEREZ
0 siblings, 0 replies; 21+ messages in thread
From: Christophe PEREZ @ 2006-04-11 20:36 UTC (permalink / raw
To: gentoo-catalyst
Le Tue, 11 Apr 2006 15:12:13 -0500, Andrew Gaffney a écrit :
> You know, it doesn't make much sense to build an up to date stage1. A stage1
> install recompiles everything anyway, so why not just use the 2006.0 stage1 tarball?
I know, but :
1) as you could read, I didn't find a another solution
2) if I want a portage uptodate, I don't have another choice, no ?
> As for your actual problem, it's because you're using a i586-pc-linux-gnu CHOST
> for the catalyst build while (I bet) all of your distcc helpers are
> i686-pc-linux-gnu.
Yes.
> When the build is distributed, it'll look for
> i586-pc-linux-gnu-gcc, which won't exist on the helpers, which will return a
> code 110.
And the solution is ?
--
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-catalyst] Re: Re: problem with distcc
2006-04-11 20:22 ` [gentoo-catalyst] " Chris Gianelloni
@ 2006-04-11 20:39 ` Christophe PEREZ
2006-04-11 20:57 ` Christophe PEREZ
0 siblings, 1 reply; 21+ messages in thread
From: Christophe PEREZ @ 2006-04-11 20:39 UTC (permalink / raw
To: gentoo-catalyst
Le Tue, 11 Apr 2006 16:22:25 -0400, Chris Gianelloni a écrit :
> What this means is for you to build a CHOST=i586-pc-linux-gnu machine,
> you are *required* to have a cross-compiler that is named
> i586-pc-linux-gnu-gcc on each of your distcc slaves.
Ah, ok, so I have to find out what I have to change to have that...
I'm really not used with cross-compile.
May be I have more chance changing i586 to i686 ?
--
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-catalyst] Re: Re: problem with distcc
2006-04-11 20:39 ` [gentoo-catalyst] " Christophe PEREZ
@ 2006-04-11 20:57 ` Christophe PEREZ
2006-04-11 21:45 ` Chris Gianelloni
0 siblings, 1 reply; 21+ messages in thread
From: Christophe PEREZ @ 2006-04-11 20:57 UTC (permalink / raw
To: gentoo-catalyst
Le Tue, 11 Apr 2006 16:39:17 -0400, Christophe PEREZ a écrit :
> May be I have more chance changing i586 to i686 ?
If fact, the real question is :
What arch to choose to have the livecd working on most PCs (others than
mine) ?
(all my distcc slaves are CHOST="i686-pc-linux-gnu")
-----------------------
Le Tue, 11 Apr 2006 16:36:39 -0400, Christophe PEREZ a écrit :
>> When the build is distributed, it'll look for
>> i586-pc-linux-gnu-gcc, which won't exist on the helpers, which will return a
>> code 110.
>
> And the solution is ?
Ok, understood now (with another post), cross-compile is the solution.
--
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-catalyst] Re: Re: problem with distcc
2006-04-11 20:57 ` Christophe PEREZ
@ 2006-04-11 21:45 ` Chris Gianelloni
2006-04-11 22:02 ` [gentoo-catalyst] " Christophe PEREZ
0 siblings, 1 reply; 21+ messages in thread
From: Chris Gianelloni @ 2006-04-11 21:45 UTC (permalink / raw
To: gentoo-catalyst
[-- Attachment #1: Type: text/plain, Size: 546 bytes --]
On Tue, 2006-04-11 at 16:57 -0400, Christophe PEREZ wrote:
> Le Tue, 11 Apr 2006 16:39:17 -0400, Christophe PEREZ a écrit :
>
> > May be I have more chance changing i586 to i686 ?
>
> If fact, the real question is :
> What arch to choose to have the livecd working on most PCs (others than
> mine) ?
> (all my distcc slaves are CHOST="i686-pc-linux-gnu")
We use "x86" for the installcd and "i686" for the LiveCD.
--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-catalyst] Re: Re: Re: problem with distcc
2006-04-11 21:45 ` Chris Gianelloni
@ 2006-04-11 22:02 ` Christophe PEREZ
2006-04-12 13:48 ` Chris Gianelloni
0 siblings, 1 reply; 21+ messages in thread
From: Christophe PEREZ @ 2006-04-11 22:02 UTC (permalink / raw
To: gentoo-catalyst
Le Tue, 11 Apr 2006 17:45:44 -0400, Chris Gianelloni a écrit :
> We use "x86" for the installcd and "i686" for the LiveCD.
Ok, i686 is what I have used, and I'm compiling a livecd-stage1.
Distcc is working fine now.
Another question please.
I just need to create a livecd with some desktop softs like OOo, Gimp,
Firefox etc...
The only thing particular I need is the /home is automaticaly mounted on a
USB key (I don't want to build a liveusb because all PC can't boot on USB)
and maybe some others little personalizations.
Can I do that as I'm trying, building a livecd-stage1 then livecd-stage2,
or have I necessarily to start building at a stageX ?
I think I can use the first method, but I'm not sure...
--
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-catalyst] Re: Re: Re: problem with distcc
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
0 siblings, 1 reply; 21+ messages in thread
From: Chris Gianelloni @ 2006-04-12 13:48 UTC (permalink / raw
To: gentoo-catalyst
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
On Tue, 2006-04-11 at 18:02 -0400, Christophe PEREZ wrote:
> Le Tue, 11 Apr 2006 17:45:44 -0400, Chris Gianelloni a écrit :
>
> > We use "x86" for the installcd and "i686" for the LiveCD.
>
> Ok, i686 is what I have used, and I'm compiling a livecd-stage1.
> Distcc is working fine now.
>
>
> Another question please.
> I just need to create a livecd with some desktop softs like OOo, Gimp,
> Firefox etc...
> The only thing particular I need is the /home is automaticaly mounted on a
> USB key (I don't want to build a liveusb because all PC can't boot on USB)
> and maybe some others little personalizations.
>
> Can I do that as I'm trying, building a livecd-stage1 then livecd-stage2,
> or have I necessarily to start building at a stageX ?
>
> I think I can use the first method, but I'm not sure...
You shouldn't ever really need to make your own stages unless you're
just wanting more up-to-date versions.
--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-catalyst] Re: problem with distcc
2006-04-12 13:48 ` Chris Gianelloni
@ 2006-04-12 15:51 ` Christophe PEREZ
2006-04-12 20:12 ` Chris Gianelloni
0 siblings, 1 reply; 21+ messages in thread
From: Christophe PEREZ @ 2006-04-12 15:51 UTC (permalink / raw
To: gentoo-catalyst
Le Wed, 12 Apr 2006 09:48:37 -0400, Chris Gianelloni a écrit :
> You shouldn't ever really need to make your own stages unless you're
> just wanting more up-to-date versions.
Ok, clear.
And, in this case, I have to build my own portage snapshot and all
stage{1,2,3}, that's right ?
======
Other thing :
Build my own portage snapshot is the only way to use an ebuild I made ?
No portage overlay system ?
I tried to define PORTDIR_OVERLAY in envscript, but I have an error :
!!! Invalid PORTDIR_OVERLAY (not a dir): /etc/catalyst2/portage-overlay
# ls /etc/catalyst2/portage-overlay/
net-misc
It would be very sad to have to build snapshot and all stages juste to
have one soft more, but may be it's the only way.
--
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-catalyst] Re: problem with distcc
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
0 siblings, 1 reply; 21+ messages in thread
From: Chris Gianelloni @ 2006-04-12 20:12 UTC (permalink / raw
To: gentoo-catalyst
[-- Attachment #1: Type: text/plain, Size: 1149 bytes --]
On Wed, 2006-04-12 at 11:51 -0400, Christophe PEREZ wrote:
> Le Wed, 12 Apr 2006 09:48:37 -0400, Chris Gianelloni a écrit :
>
> > You shouldn't ever really need to make your own stages unless you're
> > just wanting more up-to-date versions.
>
> Ok, clear.
> And, in this case, I have to build my own portage snapshot and all
> stage{1,2,3}, that's right ?
If you wanted updated stages, yes.
> ======
> Other thing :
> Build my own portage snapshot is the only way to use an ebuild I made ?
> No portage overlay system ?
> I tried to define PORTDIR_OVERLAY in envscript, but I have an error :
>
> !!! Invalid PORTDIR_OVERLAY (not a dir): /etc/catalyst2/portage-overlay
>
>
> # ls /etc/catalyst2/portage-overlay/
> net-misc
>
> It would be very sad to have to build snapshot and all stages juste to
> have one soft more, but may be it's the only way.
Ehh... Please read through /usr/share/doc/catalyst-2.0_rc*/examples
before continuing to ask questions that are already answered there... ;]
--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-catalyst] Re: Re: problem with distcc
2006-04-12 20:12 ` Chris Gianelloni
@ 2006-04-12 21:07 ` Christophe PEREZ
2006-04-12 21:34 ` Christophe PEREZ
2006-04-13 13:06 ` Chris Gianelloni
0 siblings, 2 replies; 21+ messages in thread
From: Christophe PEREZ @ 2006-04-12 21:07 UTC (permalink / raw
To: gentoo-catalyst
Le Wed, 12 Apr 2006 16:12:55 -0400, Chris Gianelloni a écrit :
>> And, in this case, I have to build my own portage snapshot and all
>> stage{1,2,3}, that's right ?
>
> If you wanted updated stages, yes.
Ok, and may be I need something up-to-date because now, I have an error
with pango :
>>> md5 src_uri ;-) pango-1.10.2.tar.bz2
* Please re-emerge x11-libs/cairo with the png and X USE flags set
!!! ERROR: x11-libs/pango-1.10.2 failed.
!!! Function pkg_setup, Line 41, Exitcode 0
!!! cairo needs png and X flags set
!!! If you need support, post the topmost build error, NOT this status message.
But I do have X and png in USE.
> Ehh... Please read through /usr/share/doc/catalyst-2.0_rc*/examples
> before continuing to ask questions that are already answered there... ;]
I always search before asking here, you know.
I can see a portdir_overlay option, but only in snapshot_templace.spec.
And all I can find in others specs (livecd/root_overlay,
livecd/overlay...) don't seem to be what I need.
--
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-catalyst] Re: Re: problem with distcc
2006-04-12 21:07 ` [gentoo-catalyst] " Christophe PEREZ
@ 2006-04-12 21:34 ` Christophe PEREZ
2006-04-13 13:06 ` Chris Gianelloni
1 sibling, 0 replies; 21+ messages in thread
From: Christophe PEREZ @ 2006-04-12 21:34 UTC (permalink / raw
To: gentoo-catalyst
Le Wed, 12 Apr 2006 17:07:32 -0400, Christophe PEREZ a écrit :
> But I do have X and png in USE.
I'm not sure, but it seems that's because I had each USE on a line in my
spec (as I had for the first livecd), X wasn't visible (seen by a chroot
and emerge info).
With all on the same line, it's now compiling cairo again.
--
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: [gentoo-catalyst] Re: Re: problem with distcc
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
1 sibling, 1 reply; 21+ messages in thread
From: Chris Gianelloni @ 2006-04-13 13:06 UTC (permalink / raw
To: gentoo-catalyst
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
On Wed, 2006-04-12 at 17:07 -0400, Christophe PEREZ wrote:
> I always search before asking here, you know.
> I can see a portdir_overlay option, but only in snapshot_templace.spec.
> And all I can find in others specs (livecd/root_overlay,
> livecd/overlay...) don't seem to be what I need.
GRR... It seems to be missing from the example specs now. I've just
added it back in, so it'll be in 2.0_rc42.
Anyway, use portage-overlay in any spec file *except* snapshot. Also,
you need to use the *exact* same overlay for all of your targets, or
else you can cause problems for yourself.
--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-catalyst] Re: problem with distcc
2006-04-13 13:06 ` Chris Gianelloni
@ 2006-04-13 13:59 ` Christophe PEREZ
2006-04-13 15:59 ` Christophe PEREZ
0 siblings, 1 reply; 21+ messages in thread
From: Christophe PEREZ @ 2006-04-13 13:59 UTC (permalink / raw
To: gentoo-catalyst
Le Thu, 13 Apr 2006 09:06:55 -0400, Chris Gianelloni a écrit :
> GRR... It seems to be missing from the example specs now. I've just
> added it back in, so it'll be in 2.0_rc42.
Ah, I'm not so stupid... ;-)
> Anyway, use portage-overlay in any spec file *except* snapshot.
Ok !!
*portage-overlay* is the option name ? and not "portage_overlay" ?
> Also,
> you need to use the *exact* same overlay for all of your targets, or
> else you can cause problems for yourself.
Of course.
thanks.
--
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-catalyst] Re: problem with distcc
2006-04-13 13:59 ` [gentoo-catalyst] " Christophe PEREZ
@ 2006-04-13 15:59 ` Christophe PEREZ
0 siblings, 0 replies; 21+ messages in thread
From: Christophe PEREZ @ 2006-04-13 15:59 UTC (permalink / raw
To: gentoo-catalyst
Le Thu, 13 Apr 2006 09:59:38 -0400, Christophe PEREZ a écrit :
>> Anyway, use portage-overlay in any spec file *except* snapshot.
>
> Ok !!
> *portage-overlay* is the option name ? and not "portage_overlay" ?
I could try now, and it seems to be "portage_overlay".
--
Christophe PEREZ
--
gentoo-catalyst@gentoo.org mailing list
^ permalink raw reply [flat|nested] 21+ messages in thread
end of thread, other threads:[~2006-04-13 15:59 UTC | newest]
Thread overview: 21+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox