1 |
I'm attempting to build stage2, from a successfully created stage1 |
2 |
tarball. I get an error: i686-pc-linux-gnu-gcc: No such file or |
3 |
directory |
4 |
|
5 |
I have included specs and output from catalyst. What am I missing here? |
6 |
|
7 |
The following is my spec file: |
8 |
subarch: i686 |
9 |
target: stage2 |
10 |
version_stamp: rwmc.001 |
11 |
rel_type: default |
12 |
profile: default/linux/x86/2008.0 |
13 |
snapshot: latest |
14 |
source_subpath: default/stage1-x86-rwmc.001 |
15 |
chost: i686-pc-linux-gnu |
16 |
|
17 |
I generated the stage1 from the following spec file successfully: |
18 |
subarch: x86 |
19 |
target: stage1 |
20 |
version_stamp: rwmc.001 |
21 |
rel_type: default |
22 |
profile: default/linux/x86/2008.0 |
23 |
snapshot: latest |
24 |
source_subpath: default/stage3-x86-2007.0 |
25 |
chost: i486-pc-linux-gnu |
26 |
|
27 |
The following is the last (what I seem to think is relevant) output from |
28 |
catalyst -d -f rwmc-stage2.spec: |
29 |
Gentoo Linux; http://www.gentoo.org/ |
30 |
Copyright 1999-2008 Gentoo Foundation; Distributed under the GPLv2 |
31 |
Starting Bootstrap of base system ... |
32 |
------------------------------------------------------------------------ |
33 |
------- |
34 |
[[ (0/3) Locating packages ]] |
35 |
* Using baselayout : sys-apps/baselayout |
36 |
* Using portage : virtual/portage |
37 |
* Using os-headers : >=sys-kernel/linux-headers-2.6.23-r3 |
38 |
* Using binutils : sys-devel/binutils |
39 |
* Using gcc : sys-devel/gcc |
40 |
* Using gettext : gettext |
41 |
* Using libc : virtual/libc |
42 |
* Using texinfo : sys-apps/texinfo |
43 |
* Using zlib : sys-libs/zlib |
44 |
* Using ncurses : sys-libs/ncurses |
45 |
------------------------------------------------------------------------ |
46 |
------- |
47 |
[[ (1/3) Configuring environment ]] |
48 |
* GENTOO_MIRRORS="http://distfiles.gentoo.org |
49 |
http://distro.ibiblio.org/pub/linux/distributions/gentoo" |
50 |
* PORTDIR="/usr/portage" |
51 |
* DISTDIR="/usr/portage/distfiles" |
52 |
* PKGDIR="/usr/portage/packages" |
53 |
* PORTAGE_TMPDIR="/var/tmp" |
54 |
* CFLAGS="-O2 -march=i686 -pipe" |
55 |
* CHOST="i686-pc-linux-gnu" |
56 |
* CXXFLAGS="-O2 -march=i686 -pipe" |
57 |
* ACCEPT_KEYWORDS="x86" |
58 |
* FEATURES="ccache distlocks metadata-transfer nodoc noinfo noman |
59 |
sandbox sfperms strict unmerge-orphans userfetch" |
60 |
------------------------------------------------------------------------ |
61 |
------- |
62 |
[[ (2/3) Updating portage ]] |
63 |
Calculating dependencies... done! |
64 |
>>> Verifying ebuild Manifests... |
65 |
|
66 |
>>> Emerging (1 of 1) sys-apps/portage-2.1.4.5 to / |
67 |
* portage-2.1.4.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... |
68 |
[ ok ] |
69 |
* portage-2.1.4.5.patch.bz2 RMD160 SHA1 SHA256 size ;-) ... |
70 |
[ ok ] |
71 |
* checking ebuild checksums ;-) ... |
72 |
[ ok ] |
73 |
* checking auxfile checksums ;-) ... |
74 |
[ ok ] |
75 |
* checking miscfile checksums ;-) ... |
76 |
[ ok ] |
77 |
* checking portage-2.1.4.tar.bz2 ;-) ... |
78 |
[ ok ] |
79 |
* checking portage-2.1.4.5.patch.bz2 ;-) ... |
80 |
[ ok ] |
81 |
>>> Unpacking source... |
82 |
>>> Unpacking portage-2.1.4.tar.bz2 to |
83 |
/var/tmp/portage/sys-apps/portage-2.1.4.5/work |
84 |
>>> Unpacking portage-2.1.4.5.patch.bz2 to |
85 |
/var/tmp/portage/sys-apps/portage-2.1.4.5/work |
86 |
* Applying portage-2.1.4.5.patch ... |
87 |
[ ok ] |
88 |
* Setting portage.VERSION to 2.1.4.5 ... |
89 |
[ ok ] |
90 |
>>> Source unpacked. |
91 |
>>> Compiling source in |
92 |
/var/tmp/portage/sys-apps/portage-2.1.4.5/work/portage-2.1.4 ... |
93 |
i686-pc-linux-gnu-gcc: No such file or directory |
94 |
* |
95 |
* ERROR: sys-apps/portage-2.1.4.5 failed. |
96 |
* Call stack: |
97 |
* ebuild.sh, line 49: Called src_compile |
98 |
* environment, line 2470: Called die |
99 |
* The specific snippet of code: |
100 |
* $(tc-getCC) ${CFLAGS} ${LDFLAGS} -o tbz2tool tbz2tool.c || die |
101 |
"Failed to build tbz2tool"; |
102 |
* The die message: |
103 |
* Failed to build tbz2tool |
104 |
* |
105 |
* If you need support, post the topmost build error, and the call stack |
106 |
if relevant. |
107 |
* A complete build log is located at |
108 |
'/var/tmp/portage/sys-apps/portage-2.1.4.5/temp/build.log'. |
109 |
* The ebuild environment file is located at |
110 |
'/var/tmp/portage/sys-apps/portage-2.1.4.5/temp/environment'. |
111 |
* |
112 |
|
113 |
* Messages for package sys-apps/portage-2.1.4.5: |
114 |
|
115 |
* |
116 |
* ERROR: sys-apps/portage-2.1.4.5 failed. |
117 |
* Call stack: |
118 |
* ebuild.sh, line 49: Called src_compile |
119 |
* environment, line 2470: Called die |
120 |
* The specific snippet of code: |
121 |
* $(tc-getCC) ${CFLAGS} ${LDFLAGS} -o tbz2tool tbz2tool.c || die |
122 |
"Failed to build tbz2tool"; |
123 |
* The die message: |
124 |
* Failed to build tbz2tool |
125 |
* |
126 |
* If you need support, post the topmost build error, and the call stack |
127 |
if relevant. |
128 |
* A complete build log is located at |
129 |
'/var/tmp/portage/sys-apps/portage-2.1.4.5/temp/build.log'. |
130 |
* The ebuild environment file is located at |
131 |
'/var/tmp/portage/sys-apps/portage-2.1.4.5/temp/environment'. |
132 |
* |
133 |
|
134 |
!!! catalyst: run script failed. |
135 |
|
136 |
|
137 |
Traceback (most recent call last): |
138 |
File "modules/generic_stage_target.py", line 1250, in run_local |
139 |
"run script failed.",env=self.env) |
140 |
File "/usr/lib/catalyst/modules/catalyst_support.py", line 539, in cmd |
141 |
raise CatalystError,myexc |
142 |
CatalystError |
143 |
None |
144 |
|
145 |
!!! catalyst: Stage build aborting due to error. |
146 |
|
147 |
!!! catalyst: Error encountered during run of target stage2 |
148 |
|
149 |
Catalyst aborting.... |