| View previous topic :: View next topic |
| Author |
Message |
franco_v
n00b
Joined: 13 Mar 2008
Posts: 2
|
 Posted: Thu Mar 13, 2008 8:47 pm Post subject: catalyst: error creating stage1 |
 |
|
Hi all,
I'm using catalyst to create my personal stage3, but I have problems creating stage1.
I created the portage snapshot (catalyst -s 09032008), no problems there, but the following command (catalyst -f /path/to/stage1.spec) always gives these errors:
| Code: | ....
test ! -x /var/tmp/portage/sys-libs/glibc-2.6.1/work/build-default-i686-pc-linux-gnu-nptl/elf/ldconfig || LC_ALL=C LANGUAGE=C \
/var/tmp/portage/sys-libs/glibc-2.6.1/work/build-default-i686-pc-linux-gnu-nptl/elf/ldconfig -r /var/tmp/portage/sys-libs/glibc-2.6.1/image/ \
/lib /usr/lib
/var/tmp/portage/sys-libs/glibc-2.6.1/work/build-default-i686-pc-linux-gnu-nptl/elf/ldconfig: Can't open configuration file /etc/ld.so.conf: No such file or directory
make[1]: Leaving directory `/var/tmp/portage/sys-libs/glibc-2.6.1/work/glibc-2.6.1'
/usr/portage/sys-libs/glibc/files/eblits/src_install.eblit: line 215: i686-pc-linux-gnu-strip: command not found
*
* ERROR: sys-libs/glibc-2.6.1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_install
* environment, line 3483: Called eblit-run 'src_install'
* environment, line 1146: Called die
* The specific snippet of code:
* eblit-${PN}-$1 || die;
* The die message:
* (no error message)
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.6.1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.6.1/temp/environment'.
*
* Messages for package dev-libs/expat-2.0.1 merged to /tmp/stage1root/:
* Please note that the soname of the library changed!
* If you are upgrading from a previous version you need
* to fix dynamic linking inconsistencies by executing:
* revdep-rebuild -X --library libexpat.so.0
* Messages for package sys-apps/sandbox-1.2.18.1-r2 merged to /tmp/stage1root/:
* If configure fails with a 'cannot run C compiled programs' error, try this:
* FEATURES=-sandbox emerge sandbox
* Messages for package sys-libs/timezone-data-2007k merged to /tmp/stage1root/:
* You do not have TIMEZONE set in /etc/conf.d/clock.
* Setting /etc/localtime to Factory.
* Messages for package app-editors/nano-2.0.7 merged to /tmp/stage1root/:
* More helpful info about nano, visit the GDP page:
* http://www.gentoo.org/doc/en/nano-basics-guide.xml
* Messages for package dev-libs/libxml2-2.6.30-r1 merged to /tmp/stage1root/:
* Skipping XML catalog creation for stage building (bug #208887).
* Messages for package sys-libs/glibc-2.6.1 merged to /tmp/stage1root/:
*
* ERROR: sys-libs/glibc-2.6.1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_install
* environment, line 3483: Called eblit-run 'src_install'
* environment, line 1146: Called die
* The specific snippet of code:
* eblit-${PN}-$1 || die;
* The die message:
* (no error message)
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/sys-libs/glibc-2.6.1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/sys-libs/glibc-2.6.1/temp/environment'.
*
!!! catalyst: run script failed.
Traceback (most recent call last):
File "modules/generic_stage_target.py", line 1062, in run_local
cmd("/bin/bash "+self.settings["controller_file"]+" run","run script failed.",env=self.env)
File "/usr/lib/catalyst/modules/catalyst_support.py", line 486, in cmd
raise CatalystError,myexc
CatalystError: <unprintable instance object>
None
!!! catalyst: Stage build aborting due to error.
!!! catalyst: Error encountered during run of target stage1
Catalyst aborting....
lockfile does not exist '/var/tmp/catalyst/tmp/default/stage1-i686-09032008/.catalyst_lock' |
The directory /var/tmp/catalyst/tmp/default/stage1-i686-09032008 is created (along with its content), but the .tar.bz2 file is not.
this is my stage1.spec file:
| Code: | subarch: i686
version_stamp: 09032008
target: stage1
rel_type: default
profile: default-linux/x86/2007.0
snapshot: 09032008
source_subpath: stage3-x86-2007.0
distcc_hosts:
portage_confdir: /etc/portage
portage_overlay:
pkgcache_path: /tmp/packages
chost: i686-pc-linux-gnu
cflags: -O2 -pipe -fomit-frame-pointer -mtune=i686
cxxflags: -O2 -pipe -fomit-frame-pointer -mtune=i686
ldflags: |
my gentoo machine is updated and I use catalyst 2.0.5
I tried several times those two commands (catalyst -s ... and catalyst -f ...), after several complete updates (emerge -uD world); I also tried -Os in cflags and cxxflags, never modified the standard /etc/catalyst/catalyst.conf file.
I'm a newbie of Gentoo, maybe there's something wrong or something I don't know
Any suggestions?
Thanks in advance
Franco Vecchiato |
|
| Back to top |
|
 |
z9
n00b
Joined: 16 Mar 2008
Posts: 2
|
| Posted: Sun Mar 16, 2008 8:58 am Post subject: |
|
|
I had this problem too.
If you are using stage3-x86-2007.0 its chost is 486 so the 686 tool kit is missing. Switch to stage3-i686-2007.0.tar.bz2 form your local mirror and you should be good. |
|
| Back to top |
|
|
z9
n00b
Joined: 16 Mar 2008
Posts: 2
|
| Posted: Mon Mar 17, 2008 11:49 pm Post subject: |
|
|
Scratch my last post it caused problems in the stage3 build. Apparently the stage1 is suppose to be generic. For the stage1.spec change it to “subarch x86 chost: i486-pc-linux-gnu” this got me up to stage3.
| Code: |
cat stage1.spec
subarch: x86
version_stamp: 08.1
target: stage1
rel_type: default
profile: default-linux/x86/2007.0
snapshot: stage1
source_subpath: default/stage3-x86-2007.0
distcc_hosts:
portage_confdir: /root/catalyst/portage
portage_overlay:
pkgcache_path: /tmp/packages/catalyst/satge1
chost: i486-pc-linux-gnu
cflags: -Os -pipe -fomit-frame-pointer -march=i686
cxxflags: -Os -pipe -fomit-frame-pointer -march=i686
ldflags:
|
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Other Things Gentoo
