[gentoo-catalyst] problem with ARCH

[gentoo-catalyst] problem with ARCH

[martin nicolas]

So in first time hello every body, in a second time please excuse me
for my poor level in english.

So now my problem, I try for the first time to build a livecd based on
a stage1 and have the folowing problem :

!!! ARCH is not set... Are you missing the /etc/make.profile symlink?
!!! Is the symlink correct? Is your portage tree complete?

but my /etc/make.profile is correctly set.

What can I do ?
--
gentoo-catalyst@gentoo.org mailing list

[gentoo-catalyst] problem with ARCH

[martin nicolas]

So in first time hello everybody, in a second time please excuse me
for my poor level in english.

So now my problem, I try for the first time to build a livecd based on
a stage1 and have the folowing problem :

!!! ARCH is not set... Are you missing the /etc/make.profile symlink?
!!! Is the symlink correct? Is your portage tree complete?

but my /etc/make.profile is correctly set.

What can I do ?
--
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] problem with ARCH

[Tobias Scherbaum]

[-- Attachment #1: Type: text/plain, Size: 404 bytes --]

On Wed, 2004-12-22 at 10:40 +0100, martin nicolas wrote:
> !!! ARCH is not set... Are you missing the /etc/make.profile symlink?
> !!! Is the symlink correct? Is your portage tree complete?
> 
> but my /etc/make.profile is correctly set.

Are you using a cascading profiles enabled stage archive, but an "old"
profile (i.e. default-x86-2004.2) in your specfile or the other way
round?

Tobias

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-catalyst] problem with ARCH

[martin nicolas]

[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]

I dont think so, in fact here is the total debug output :

>>> Regenerating /etc/ld.so.cache...
 * Caching service dependencies...


Performing Global Updates: /usr/portage/profiles/updates/4Q-2004
(Could take a couple of minutes if you have a lot of binary packages.)
  .='update pass'  *='binary update'  @='/var/db move'
  s='/var/db SLOT move' S='binary SLOT move' p='update /etc/portage/package.*'
......................................s.....s.......



 ** Skipping packages. Run 'fixpackages' or set it in FEATURES to fix the
    tbz2's in the packages directory. Note: This can take a very long time.
!!! ARCH is not set... Are you missing the /etc/make.profile symlink?
!!! Is the symlink correct? Is your portage tree complete?

and my spec file in attachment.

Thanks for the replies.


On Wed, 22 Dec 2004 11:31:57 +0100, Tobias Scherbaum
<dertobi123@gentoo.org> wrote:
> On Wed, 2004-12-22 at 10:40 +0100, martin nicolas wrote:
> > !!! ARCH is not set... Are you missing the /etc/make.profile symlink?
> > !!! Is the symlink correct? Is your portage tree complete?
> >
> > but my /etc/make.profile is correctly set.
> 
> Are you using a cascading profiles enabled stage archive, but an "old"
> profile (i.e. default-x86-2004.2) in your specfile or the other way
> round?
> 
> Tobias
> 
> 
>

[-- Attachment #2: livecd-stage1_template.spec --]
[-- Type: application/octet-stream, Size: 1913 bytes --]

## livecd-stage1 example specfile
## used to build a livecd-stage1

## John Davis <zhen@gentoo.org>

# subarch can be any of the supported Catalyst subarches (like athlon-xp). Refer
# to the catalyst reference manual (http://www.gentoo.org/proj/en/releng/catalyst) for supported arches.
# example:
# subarch: athlon-xp
subarch: x86

# version stamp is an identifier for the build. can be anything you want it to be, but it
# is usually a date.
# example:
# version_stamp: 2004.2
version_stamp: OpenBOX-alpha-211204

# target specifies what type of build Catalyst is to do. check the catalyst reference manual
# for supported targets.
# example:
# target: stage2
target: stage1

# rel_type defines what kind of build we are doing. usually, default will suffice.
# example:
# rel_type: default
rel_type: default

# system profile used to build the media
# example:
profile: default-x86-2004.3
#profile:

# which snapshot to use
# example:
# snapshot: 20040614
snapshot: 2004.3

# where the seed stage comes from, path is relative to $clst_sharedir (catalyst.conf)
# example:
#default/stage3-x86-2004.1
source_subpath: stage3-x86-2004.3

# use variables that we would like to use when building the LiveCD packages
livecd/use:
	ipv6
	socks5
	livecd
	fbcon
	ssl
	speedtouch
	atm
	ppp
	
# list of packages to be merged into the LiveCD fs.
livecd/packages:
	baselayout
	livecd-tools
	genkernel
	ucl
	kudzu-knoppix
	module-init-tools
	hotplug
	irssi
	aumix
	metalog
	pciutils
	parted
	mt-st
	links
	star
	strace
	raidtools
	nfs-utils
	jfsutils
	usbutils
	speedtouch
	ppp
	linux-atm
	xfsprogs
	xfsdump
	e2fsprogs
	reiserfsprogs
	hdparm
	nano
	less
	ccache
	distcc
	openssh
	dhcpcd
	mingetty
	pwgen
	popt
	dialog
	rp-pppoe
	gpm
	screen
	mirrorselect
	penggy
	iputils
	hwdata-knoppix
	hwsetup
	bootsplash
	device-mapper
	lvm2
	evms
	vim
	gpart
	pwgen
	pptpclient
	mdadm
	tcptraceroute
	netcat
	ethtool
	wireless-tools
	ufed

Re: [gentoo-catalyst] problem with ARCH

[Tobias Scherbaum]

[-- Attachment #1: Type: text/plain, Size: 304 bytes --]

On Wed, 2004-12-22 at 12:13 +0100, martin nicolas wrote:
> !!! ARCH is not set... Are you missing the /etc/make.profile symlink?
> !!! Is the symlink correct? Is your portage tree complete?
> 
> and my spec file in attachment.

Try "profile: default-linux/x86/2004.3" in your spec file.

Tobias

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-catalyst] problem with ARCH

[martin nicolas]

Thanks a lot it works !!!!
Now waiting for a long time ..... 


On Wed, 22 Dec 2004 12:17:50 +0100, Tobias Scherbaum
<dertobi123@gentoo.org> wrote:
> On Wed, 2004-12-22 at 12:13 +0100, martin nicolas wrote:
> > !!! ARCH is not set... Are you missing the /etc/make.profile symlink?
> > !!! Is the symlink correct? Is your portage tree complete?
> >
> > and my spec file in attachment.
> 
> Try "profile: default-linux/x86/2004.3" in your spec file.
> 
> Tobias
> 
> 
>
--
gentoo-catalyst@gentoo.org mailing list

[gentoo-catalyst] Problem with ARCH

[Dylan Carlson]

Greetings,

I feel stupid sending this email but I don't have the time to peek at 
catalyst's internals to figure it out, just to roll these amd64 stages for 
hardened.  Figuring that it was a problem with the hardened/amd64 profile, 
I tried the default-linux/amd64/2004.3 profile and it failed too.  
Obviously I'm doing something wrong, and I would appreciate it if someone 
pointed it out for me.

Anyway, here's the error:

Gentoo Catalyst, version 1.1.0
Copyright 2003-2004 The Gentoo Foundation
Distributed under the GNU General Public License version 2

Using default Catalyst configuration file, /etc/catalyst/catalyst.conf
Setting storedir to default value "/var/tmp/catalyst"
Setting portdir to default value "/usr/portage"
Setting distdir to config file value "/usr/portage/distfiles"
Setting options to config file value "ccache pkgcache kerncache"
Setting sharedir to config file value "/usr/lib/catalyst"
Compiler cache support enabled.
Package cache support enabled.
Kernel cache support enabled.
Envscript support enabled.
Building natively for amd64
Setting up directories...
Running command "rm -rf /var/tmp/catalyst/tmp/default/stage3-amd64-2005.0"
Unpacking stage tarball...
Running command "tar 
xjpf /var/tmp/catalyst/builds/stage3-amd64-2004.3.tar.bz2 
-C /var/tmp/catalyst/tmp/default/stage3-amd64-2005.0"
Unpacking portage tree snapshot...
Running command "tar 
xjpf /var/tmp/catalyst/snapshots/portage-20041230.tar.bz2 
-C /var/tmp/catalyst/tmp/default/stage3-amd64-2005.0/usr"
Configuring profile link...
Running command "rm 
-f /var/tmp/catalyst/tmp/default/stage3-amd64-2005.0/etc/make.profile"
Running command "ln 
-sf ../usr/portage/profiles/default-linux/amd64/2004.3 /var/tmp/catalyst/tmp/default/stage3-amd64-2005.0/etc/make.profile"
Setting up chroot...
Running command 
"cp /etc/resolv.conf /var/tmp/catalyst/tmp/default/stage3-amd64-2005.0/etc"
Running command 
"cp /root/catalyst-env.sh /var/tmp/catalyst/tmp/default/stage3-amd64-2005.0/tmp/envscript"
Running command "rm 
-f /var/tmp/catalyst/tmp/default/stage3-amd64-2005.0/etc/make.conf"
Running command "/bin/bash /usr/lib/catalyst/targets/stage3/stage3.sh run"
>>> Regenerating /etc/ld.so.cache...
 * Caching service dependencies...
!!! ARCH is not set... Are you missing the /etc/make.profile symlink?
!!! Is the symlink correct? Is your portage tree complete?                                                



Here's my spec file:

# subarch can be any of the supported Catalyst subarches (like athlon-xp). 
Refer
# to the catalyst reference manual 
(http://www.gentoo.org/proj/en/releng/catalyst) for supported arches.
# example:
# subarch: athlon-xp
subarch: amd64

# version stamp is an identifier for the build. can be anything you want it 
to be, but it
# is usually a date.
# example:
# version_stamp: 2004.2
version_stamp: 2005.0

# target specifies what type of build Catalyst is to do. check the catalyst 
reference manual
# for supported targets.
# example:
# target: stage2
target: stage3

# rel_type defines what kind of build we are doing. usually, default will 
suffice.
# example:
# rel_type: default
rel_type: default

# system profile used to build the media
# example:
# profile: default-x86-2004.0
#profile: hardened/amd64
profile: default-linux/amd64/2004.3

# which snapshot to use
# example:
# snapshot: 20040614
snapshot: 20041230

# where the seed stage comes from, path is relative to $clst_sharedir 
(catalyst.conf)
# example:
# default/stage3-x86-2004.1
source_subpath: stage3-amd64-2004.3

Cheers,
Dylan Carlson [absinthe@gentoo.org]
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x708E165F
--
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Problem with ARCH

[Dylan Carlson]

bump, please

On Thu December 30 2004 12:08, Dylan Carlson wrote:
> Greetings,
>
> I feel stupid sending this email but I don't have the time to peek at
> catalyst's internals to figure it out, just to roll these amd64 stages
> for hardened.  Figuring that it was a problem with the hardened/amd64
> profile, I tried the default-linux/amd64/2004.3 profile and it failed
> too. Obviously I'm doing something wrong, and I would appreciate it if
> someone pointed it out for me.
>
> Anyway, here's the error:
>
> Gentoo Catalyst, version 1.1.0
> Copyright 2003-2004 The Gentoo Foundation
> Distributed under the GNU General Public License version 2
>
> Using default Catalyst configuration file, /etc/catalyst/catalyst.conf
> Setting storedir to default value "/var/tmp/catalyst"
> Setting portdir to default value "/usr/portage"
> Setting distdir to config file value "/usr/portage/distfiles"
> Setting options to config file value "ccache pkgcache kerncache"
> Setting sharedir to config file value "/usr/lib/catalyst"
> Compiler cache support enabled.
> Package cache support enabled.
> Kernel cache support enabled.
> Envscript support enabled.
> Building natively for amd64
> Setting up directories...
> Running command "rm -rf
> /var/tmp/catalyst/tmp/default/stage3-amd64-2005.0" Unpacking stage
> tarball...
> Running command "tar
> xjpf /var/tmp/catalyst/builds/stage3-amd64-2004.3.tar.bz2
> -C /var/tmp/catalyst/tmp/default/stage3-amd64-2005.0"
> Unpacking portage tree snapshot...
> Running command "tar
> xjpf /var/tmp/catalyst/snapshots/portage-20041230.tar.bz2
> -C /var/tmp/catalyst/tmp/default/stage3-amd64-2005.0/usr"
> Configuring profile link...
> Running command "rm
> -f /var/tmp/catalyst/tmp/default/stage3-amd64-2005.0/etc/make.profile"
> Running command "ln
> -sf ../usr/portage/profiles/default-linux/amd64/2004.3
> /var/tmp/catalyst/tmp/default/stage3-amd64-2005.0/etc/make.profile"
> Setting up chroot...
> Running command
> "cp /etc/resolv.conf
> /var/tmp/catalyst/tmp/default/stage3-amd64-2005.0/etc" Running command
> "cp /root/catalyst-env.sh
> /var/tmp/catalyst/tmp/default/stage3-amd64-2005.0/tmp/envscript" Running
> command "rm
> -f /var/tmp/catalyst/tmp/default/stage3-amd64-2005.0/etc/make.conf"
> Running command "/bin/bash /usr/lib/catalyst/targets/stage3/stage3.sh
> run"
>
> >>> Regenerating /etc/ld.so.cache...
>
>  * Caching service dependencies...
> !!! ARCH is not set... Are you missing the /etc/make.profile symlink?
> !!! Is the symlink correct? Is your portage tree complete?
>
>
>
> Here's my spec file:
>
> # subarch can be any of the supported Catalyst subarches (like
> athlon-xp). Refer
> # to the catalyst reference manual
> (http://www.gentoo.org/proj/en/releng/catalyst) for supported arches.
> # example:
> # subarch: athlon-xp
> subarch: amd64
>
> # version stamp is an identifier for the build. can be anything you want
> it to be, but it
> # is usually a date.
> # example:
> # version_stamp: 2004.2
> version_stamp: 2005.0
>
> # target specifies what type of build Catalyst is to do. check the
> catalyst reference manual
> # for supported targets.
> # example:
> # target: stage2
> target: stage3
>
> # rel_type defines what kind of build we are doing. usually, default
> will suffice.
> # example:
> # rel_type: default
> rel_type: default
>
> # system profile used to build the media
> # example:
> # profile: default-x86-2004.0
> #profile: hardened/amd64
> profile: default-linux/amd64/2004.3
>
> # which snapshot to use
> # example:
> # snapshot: 20040614
> snapshot: 20041230
>
> # where the seed stage comes from, path is relative to $clst_sharedir
> (catalyst.conf)
> # example:
> # default/stage3-x86-2004.1
> source_subpath: stage3-amd64-2004.3
>
> Cheers,
> Dylan Carlson [absinthe@gentoo.org]
> Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x708E165F
> --
> gentoo-catalyst@gentoo.org mailing list

-- 
Dylan Carlson [absinthe@gentoo.org]
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x708E165F
--
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Problem with ARCH

[John Davis]

[-- Attachment #1: Type: text/plain, Size: 641 bytes --]

On Thu, 2004-12-30 at 17:21 -0500, Dylan Carlson wrote:
> bump, please
> 

Try using Catalyst CVS (gentoo/src/catalyst) and see if that fixes the
problem. I know that there were at least a couple of problems with
stacked profiles that were fixed in CVS.

Remember to set "sharedir" in /etc/catalyst/catalyst.conf to the
location of the CVS co.

Cheers,
//John
-- 
John Davis <zhen@gentoo.org>
The Gentoo Foundation
Trustee | Release Engineering Manager | Catalyst code monkey

---
"When people learn no tools of judgement and merely follow their hopes,
the seeds of political manipulation are sown"
- Stephen Jay Gould

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-catalyst] Problem with ARCH

[Dylan Carlson]

On Thu December 30 2004 17:33, John Davis wrote:
> Remember to set "sharedir" in /etc/catalyst/catalyst.conf to the
> location of the CVS co.

Yeah, I tried that... no luck.  :/

I think grsec is getting in the way because of a more limited chroot.  Alas 
I will have to spend more time on this in Jan, unfortunately.   Thanks 
though.

-- 
Dylan Carlson [absinthe@gentoo.org]
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x708E165F
--
gentoo-catalyst@gentoo.org mailing list

Re: [gentoo-catalyst] Problem with ARCH

[Chris Gianelloni]

[-- Attachment #1: Type: text/plain, Size: 797 bytes --]

On Thu, 2004-12-30 at 17:59 -0500, Dylan Carlson wrote:
> On Thu December 30 2004 17:33, John Davis wrote:
> > Remember to set "sharedir" in /etc/catalyst/catalyst.conf to the
> > location of the CVS co.
> 
> Yeah, I tried that... no luck.  :/
> 
> I think grsec is getting in the way because of a more limited chroot.  Alas 
> I will have to spend more time on this in Jan, unfortunately.   Thanks 
> though.

You have to pretty much turn off all chroot restrictions to use catalyst
successfully.

Also, there's no need to "bump" on a mailing list.  John and I were
actually discussing your problem yesterday, but as of yet had not come
up with any solutions to your problem.

-- 
Chris Gianelloni
Release Engineering - Operations/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]