List Info

Thread: build stage1 problems.




build stage1 problems.
country flaguser name
Sweden
2007-06-08 07:08:11
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.
---
also of course the ovbious 
chroot: cannot run command `/tmp/livecd-stage1-chroot.sh':
Exec format
error
-----

Here is a paste from the terminal:

acertop builds # catalyst -v -f liveraboo-stage1.spec 
Gentoo Catalyst, version 2.0.4
Copyright 2003-2006 The Gentoo Foundation
Distributed under the GNU General Public License version 2

Using default Catalyst configuration file,
/etc/catalyst/catalyst.conf
Setting sharedir to config file value
"/usr/lib/catalyst"
Setting snapshot_cache to config file value
"/var/tmp/catalyst/snapshot_cache" Setting
hash_function to config file
value "crc32" Setting storedir to config file
value "/var/tmp/catalyst"
Setting portdir to config file value
"/usr/portage"
Setting distdir to config file value
"/usr/portage/distfiles"
Setting options to config file value "autoresume
kerncache pkgcache
seedcache snapcache ccache" Autoresuming support
enabled.
Compiler cache support enabled.
Kernel cache support enabled.
Package cache support enabled.
Seed cache support enabled.
Snapshot cache support enabled.
Envscript support enabled.
Using target: livecd-stage1
Cross-compiling on x86 for different machine type amd64
Source path set to
/var/tmp/catalyst/builds/stage3-amd64-2007.0.tar.bz2
Caching snapshot to
/var/tmp/catalyst/snapshot_cache/2007-r0/
The autoresume path
is
/var/tmp/catalyst/tmp/default/.autoresume-livecd-stage1-amd6
4-installer-2007-r0/
Location of the package cache
is
/var/tmp/catalyst/packages/default/livecd-stage1-amd64-insta
ller-2007-r0/
Location of the kerncache
is
/var/tmp/catalyst/kerncache/default/livecd-stage1-amd64-inst
aller-2007-r0/
Checking for processes running in chroot and killing them.
--- Running
action sequence: unpack Referenced SEEDCACHE does not appear
to be a
directory, trying to untar... No Valid Resume point
detected, cleaning
up  ... Removing AutoResume Points: ... Emptying
directory
/var/tmp/catalyst/tmp/default/.autoresume-livecd-stage1-amd6
4-installer-2007-r0/
Emptying
directory
/var/tmp/catalyst/tmp/default/livecd-stage1-amd64-installer-
2007-r0/

Starting tar extract
from /var/tmp/catalyst/builds/stage3-amd64-2007.0.tar.bz2
to
/var/tmp/catalyst/tmp/default/livecd-stage1-amd64-installer-
2007-r0/
(This may take some time) ...

--- Running action sequence: unpack_snapshot
Cleaning up invalid snapshot cache at 
	/var/tmp/catalyst/snapshot_cache/2007-r0/ (This can take a
long
time)... Unpacking portage tree (This can take a long time)
...
lockfile does not exist
'/var/tmp/catalyst/snapshot_cache/2007-r0/.catalyst_lock'
--- Running
action sequence: config_profile_link Configuring profile
link...
--- Running action sequence: setup_confdir
--- Running action sequence: portage_overlay
--- Running action sequence: bind
--- Running action sequence: chroot_setup
Setting up chroot...

Warning!!!!
	Overriding certain env variables may cause catastrophic
failure.
	If your build fails look here first as the possible
problem.
	Catalyst assumes you know what you are doing when setting
		these variables.
	Catalyst Maintainers use VERY minimal envscripts if used at
all
	You have been warned

--- Running action sequence: setup_environment
--- Running action sequence: build_packages
copying livecd-stage1-chroot.sh
to
/var/tmp/catalyst/tmp/default/livecd-stage1-amd64-installer-
2007-r0/tmp/
copying chroot-functions.sh
to
/var/tmp/catalyst/tmp/default/livecd-stage1-amd64-installer-
2007-r0/tmp/
Running livecd-stage1-chroot.sh in
chroot
/var/tmp/catalyst/tmp/default/livecd-stage1-amd64-installer-
2007-r0/
chroot: cannot run command `/tmp/livecd-stage1-chroot.sh':
Exec format
error

!!! catalyst: Error in attempt to build packages


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line
1186, in build_packages
    " build_packages "+mypack,"Error in
attempt to build
packages",env=self.env) File
"/usr/lib/catalyst/modules/catalyst_support.py",
line 485, in cmd raise
CatalystError,myexc CatalystError: <unprintable instance
object>
None

!!! catalyst: livecdbuild aborting due to error.


Catalyst aborting....
lockfile does not exist
'/var/tmp/catalyst/tmp/default/livecd-stage1-amd64-installer
-2007-r0/.catalyst_lock'



/Raboo
-- 
gentoo-catalystgentoo.org mailing list


Re: build stage1 problems.
country flaguser name
United States
2007-06-08 07:19:21
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.

-- 
Andrew Gaffney                                 http://dev.gentoo.or
g/~agaffney/
Gentoo Linux Developer             Catalyst/Installer + x86
release coordinator
-- 
gentoo-catalystgentoo.org mailing list


Re: build stage1 problems.
country flaguser name
Sweden
2007-06-08 18:02:00
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 <agaffneygentoo.org> 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.
> 
-- 
gentoo-catalystgentoo.org mailing list


Re: build stage1 problems.
country flaguser name
Sweden
2007-06-08 19:37:30
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 <mailunixwarez.net> 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 <agaffneygentoo.org> 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.
> > 
-- 
gentoo-catalystgentoo.org mailing list


Re: build stage1 problems.
country flaguser name
Sweden
2007-06-09 08:30:22
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 <mailunixwarez.net> 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 <mailunixwarez.net> 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 <agaffneygentoo.org> 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.
> > > 

-- 
gentoo-catalystgentoo.org mailing list


[1-5]

about | contact  Other archives ( Real Estate discussion Medical topics )