Ok, now i solved the package.unmask problem by adding "portage_confdir:/etc/portage" to the stage1 spec file.
On Sat, 9 Jun 2007 02:37:30 +0200 Raboo Treed <[EMAIL PROTECTED]> wrote: > Okay i unmasked it in /etc/portage/package.unmask > But it still says that sys-apps/gli-0.5.4 is masked. > When using catalyst, do i unmask the packages in another place? > > On Sat, 9 Jun 2007 01:02:00 +0200 > Raboo Treed <[EMAIL PROTECTED]> wrote: > > > Okay, next problem, gli is in my stage1 spec file. > > - sys-apps/gli-0.5.4 (masked by: package.mask) > > Should i remove it or should i unmask it? it says it can do serious > > breakages on a machine, but this is in a chroot.. so i guess a > > unmask is in order? > > > > > > > > On Fri, 08 Jun 2007 07:19:21 -0500 > > Andrew Gaffney <[EMAIL PROTECTED]> wrote: > > > > > Raboo Treed wrote: > > > > Hey, i got problems of which i don't know how to fix. > > > > > > > > things that are wrong: > > > > lockfile does not exist > > > > '/var/tmp/catalyst/snapshot_cache/2007-r0/.catalyst_lock' > > > > it does exist. > > > > > > This isn't a problem. > > > > > > > also of course the ovbious > > > > chroot: cannot run command `/tmp/livecd-stage1-chroot.sh': Exec > > > > format error > > > > > > This is. > > > > > > > Cross-compiling on x86 for different machine type amd64 > > > > > > This is your problem. If you want to build for amd64, do it on > > > amd64. > > > -- [EMAIL PROTECTED] mailing list
