From: Franco Vecchiato <franco.vecchiato@fastwebnet.it>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] error creating stage1
Date: Fri, 14 Mar 2008 22:34:18 +0100 [thread overview]
Message-ID: <1205530458.3362.18.camel@franco.casa> (raw)
Hi all,
I'm using catalyst to create my own 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
> /path/to/logstage1) always gives these errors (final part of
logstage1):
<end_of_logstage1>
....
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'
</end_of_logstage1>
The directory /var/tmp/catalyst/tmp/default/stage1-i686-09032008 has
been created (along with its content, also .catalyst_lock), but
the .tar.bz2 file has 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:
</code>
my gentoo laptop (IBM ThinkPad T23) 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
--
gentoo-catalyst@lists.gentoo.org mailing list
next reply other threads:[~2008-03-14 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 21:34 Franco Vecchiato [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-25 2:35 [gentoo-catalyst] Error creating stage1 Luca Casagrande
2006-12-25 4:30 ` Andrew Gaffney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1205530458.3362.18.camel@franco.casa \
--to=franco.vecchiato@fastwebnet.it \
--cc=gentoo-catalyst@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox