[gentoo-catalyst] Attempt to create stage2 fails missing i686-pc-linux-gnu

[gentoo-catalyst] Attempt to create stage2 fails missing i686-pc-linux-gnu

[Dio, James]

I'm attempting to build stage2, from a successfully created stage1
tarball. I get an error: i686-pc-linux-gnu-gcc: No such file or
directory

I have included specs and output from catalyst. What am I missing here?

The following is my spec file:
subarch: i686
target: stage2
version_stamp: rwmc.001
rel_type: default
profile: default/linux/x86/2008.0
snapshot: latest
source_subpath: default/stage1-x86-rwmc.001
chost: i686-pc-linux-gnu

I generated the stage1 from the following spec file successfully:
subarch: x86
target: stage1
version_stamp: rwmc.001
rel_type: default
profile: default/linux/x86/2008.0
snapshot: latest
source_subpath: default/stage3-x86-2007.0
chost: i486-pc-linux-gnu

The following is the last (what I seem to think is relevant) output from
catalyst -d -f rwmc-stage2.spec:
Gentoo Linux; http://www.gentoo.org/
Copyright 1999-2008 Gentoo Foundation; Distributed under the GPLv2
Starting Bootstrap of base system ...
------------------------------------------------------------------------
-------
  [[ (0/3) Locating packages ]]
 * Using baselayout : sys-apps/baselayout
 * Using portage    : virtual/portage
 * Using os-headers : >=sys-kernel/linux-headers-2.6.23-r3
 * Using binutils   : sys-devel/binutils
 * Using gcc        : sys-devel/gcc
 * Using gettext    : gettext
 * Using libc       : virtual/libc
 * Using texinfo    : sys-apps/texinfo
 * Using zlib       : sys-libs/zlib
 * Using ncurses    : sys-libs/ncurses
------------------------------------------------------------------------
-------
  [[ (1/3) Configuring environment ]]
 * GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/linux/distributions/gentoo"
 * PORTDIR="/usr/portage"
 * DISTDIR="/usr/portage/distfiles"
 * PKGDIR="/usr/portage/packages"
 * PORTAGE_TMPDIR="/var/tmp"
 * CFLAGS="-O2 -march=i686 -pipe"
 * CHOST="i686-pc-linux-gnu"
 * CXXFLAGS="-O2 -march=i686 -pipe"
 * ACCEPT_KEYWORDS="x86"
 * FEATURES="ccache distlocks metadata-transfer nodoc noinfo noman
sandbox sfperms strict unmerge-orphans userfetch"
------------------------------------------------------------------------
-------
  [[ (2/3) Updating portage ]]
Calculating dependencies... done!
>>> Verifying ebuild Manifests...

>>> Emerging (1 of 1) sys-apps/portage-2.1.4.5 to /
 * portage-2.1.4.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...
[ ok ]
 * portage-2.1.4.5.patch.bz2 RMD160 SHA1 SHA256 size ;-) ...
[ ok ]
 * checking ebuild checksums ;-) ...
[ ok ]
 * checking auxfile checksums ;-) ...
[ ok ]
 * checking miscfile checksums ;-) ...
[ ok ]
 * checking portage-2.1.4.tar.bz2 ;-) ...
[ ok ]
 * checking portage-2.1.4.5.patch.bz2 ;-) ...
[ ok ]
>>> Unpacking source...
>>> Unpacking portage-2.1.4.tar.bz2 to
/var/tmp/portage/sys-apps/portage-2.1.4.5/work
>>> Unpacking portage-2.1.4.5.patch.bz2 to
/var/tmp/portage/sys-apps/portage-2.1.4.5/work
 * Applying portage-2.1.4.5.patch ...
[ ok ]
 * Setting portage.VERSION to 2.1.4.5 ...
[ ok ]
>>> Source unpacked.
>>> Compiling source in
/var/tmp/portage/sys-apps/portage-2.1.4.5/work/portage-2.1.4 ...
i686-pc-linux-gnu-gcc: No such file or directory
 *
 * ERROR: sys-apps/portage-2.1.4.5 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2470:  Called die
 * The specific snippet of code:
 *       $(tc-getCC) ${CFLAGS} ${LDFLAGS} -o tbz2tool tbz2tool.c || die
"Failed to build tbz2tool";
 *  The die message:
 *   Failed to build tbz2tool
 *
 * 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-apps/portage-2.1.4.5/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/sys-apps/portage-2.1.4.5/temp/environment'.
 *

 * Messages for package sys-apps/portage-2.1.4.5:

 *
 * ERROR: sys-apps/portage-2.1.4.5 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2470:  Called die
 * The specific snippet of code:
 *       $(tc-getCC) ${CFLAGS} ${LDFLAGS} -o tbz2tool tbz2tool.c || die
"Failed to build tbz2tool";
 *  The die message:
 *   Failed to build tbz2tool
 *
 * 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-apps/portage-2.1.4.5/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/sys-apps/portage-2.1.4.5/temp/environment'.
 *

!!! catalyst: run script failed.


Traceback (most recent call last):
  File "modules/generic_stage_target.py", line 1250, in run_local
    "run script failed.",env=self.env)
  File "/usr/lib/catalyst/modules/catalyst_support.py", line 539, in cmd
    raise CatalystError,myexc
CatalystError
None

!!! catalyst: Stage build aborting due to error.

!!! catalyst: Error encountered during run of target stage2

Catalyst aborting....

Re: [gentoo-catalyst] Attempt to create stage2 fails missing i686-pc-linux-gnu

[Peter Stuge]

Dio, James wrote:
> I'm attempting to build stage2, from a successfully created stage1
> tarball. I get an error: i686-pc-linux-gnu-gcc: No such file or
> directory

Your stage1 only built i486-pc-linux-gnu-gcc I bet, because that's
the chost you set in that spec file.


> I have included specs and output from catalyst. What am I missing
> here?

I haven't done stage1/2 in a while, but try using subarch i686 and
chost i686-pc-linux-gnu in stage1 too.


//Peter