Re: [gentoo-catalyst] problem with ARCH

[martin nicolas <nicko.martin@gmail.com>]

[-- 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