| Summary: | catalyst 1.1.1 unsuccessful in stage 1 | ||
|---|---|---|---|
| Product: | Gentoo Hosted Projects | Reporter: | M. Edward Borasky <znmeb> |
| Component: | Catalyst | Assignee: | Gentoo Catalyst Developers <catalyst> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
M. Edward Borasky
2004-11-27 16:05:07 UTC
Seed stage has to be an unoptimized stage. You would have to use stage3-x86-2004.3 rather than stage3-i686-2004.3 or it won't work. That didn't work. Same error message, same place:
emerge: please tell me what to do.
Usage:
emerge [ options ] [ action ] [ ebuildfile | tbz2file | dependency ] [ ... ]
emerge [ options ] [ action ] < system | world >
emerge < --sync | --metadata | --info >
emerge --resume [ --pretend | --ask | --skipfirst ]
emerge --help [ system | config | sync ]
Options: -[abcCdDefhikKlnoOpPsSuUvV] [--oneshot] [--newuse] [--noconfmem]
[--columns] [--nospinner]
Actions: [ --clean | --depclean | --inject | --prune | --regen | --search | --unmerge ]
For more help try 'emerge --help' or consult the man page.
!!! catalyst: build script failed
!!! catalyst: Stage build aborting due to error.
!!! catalyst: could not complete build
------------------------------------------------------------------------
I've seen that message ("emerge: please tell me what to do") before, when I've forgotten to include a "target" on an emerge command. I think one of the scripts in catalyst is missing a target.
Here's the new spec file:
## generic installation stage specfile
## used to build a stage1, stage2, or stage3 installation tarball
## John Davis <zhen@gentoo.org>
# subarch can be any of the supported Catalyst subarches (like athlon-xp). Refer
# to the catalyst reference manual (http://www.gentoo.org/proj/en/releng/catalys
t) for supported arches.
# example:
# subarch: athlon-xp
subarch: x86
# version stamp is an identifier for the build. can be anything you want it to b
e, but it
# is usually a date.
# example:
# version_stamp: 2004.2
version_stamp: 20041127-znmeb
# target specifies what type of build Catalyst is to do. check the catalyst refe
rence manual
# for supported targets.
# example:
# target: stage2
target: stage1
# rel_type defines what kind of build we are doing. usually, default will suffic
e.
# example:
# rel_type: default
rel_type: default
# system profile used to build the media
# example:
# profile: default-x86-2004.0
profile: i686-science
# which snapshot to use
# example:
# snapshot: 20040614
snapshot: 20041127-znmeb
# where the seed stage comes from, path is relative to $clst_sharedir (catalyst.
conf)
# example:
# default/stage3-x86-2004.1
source_subpath: default/stage3-x86-2004.3
------------------------------------------------------------------------------
One other note: I was watching it run, and in the step before, it compiled "ccache", and it was using the *host* CFLAGS -- "march=pentium3", etc. Is that right, or should it be using the target CFLAGS -- generic x86 or i686?
All of the scripts that come with catalyst are examples and need to be edited to suit your needs. I'm sorry, but without more information there simply isn't anything I can do as catalyst works as it is supposed to when there is a proper spec file in use. Perhaps you could check out gentoo/src/releng/specs/2004.3/x86 from viewcvs and use those instead. |
