1 |
On Fri, 1 Feb 2013 01:57:09 -0500 |
2 |
Linpeng Tang <chnttlp@×××××.com> wrote: |
3 |
|
4 |
> Hi, |
5 |
> |
6 |
> I am trying to install gentoo-prefix on another CentOS 5 server. I followed |
7 |
> heroxbd's previous advice but ran into some new problems. The installation |
8 |
> fails at gcc-config-1.8, and the build log says |
9 |
> |
10 |
> >>> Compiling source in |
11 |
> /state/partition1/linpengt/gentoo/var/tmp/portage/sys-devel/gcc-config-1.8-r00.1/work/gcc-config-1.8 |
12 |
> ... |
13 |
> make -j5 EPREFIX=/state/partition1/linpengt/gentoo |
14 |
> CC=x86_64-pc-linux-gnu-gcc |
15 |
> make: *** No rule to make target `wrapper.c.in', needed by `wrapper.c'. |
16 |
> Stop. |
17 |
> emake failed |
18 |
> * ERROR: sys-devel/gcc-config-1.8-r00.1 failed (compile phase): |
19 |
> * (no error message) |
20 |
> * |
21 |
> * Call stack: |
22 |
> * ebuild.sh, line 85: Called call-ebuildshell 'src_compile' |
23 |
> * environment, line 441: Called src_compile |
24 |
> * environment, line 2223: Called die |
25 |
> * The specific snippet of code: |
26 |
> * emake EPREFIX="${EPREFIX}" CC="$(tc-getCC)" || die |
27 |
> |
28 |
> Does anyone has any idea what's causing the problem? |
29 |
> |
30 |
> Best regards. |
31 |
> |
32 |
|
33 |
Hi Linpeng, |
34 |
|
35 |
Yes I encountered this issue on a fresh install of prefix. For some reason at |
36 |
this point in building stage3 these lines |
37 |
|
38 |
rename from wrapper.c |
39 |
rename to wrapper.c.in |
40 |
--- a/wrapper.c |
41 |
+++ b/wrapper.c.in |
42 |
|
43 |
in 'gcc-config-prefix-1.8-r221.patch' don't appear to be doing what's |
44 |
intended. If you modify 'gcc-config-1.8-r00.1.ebuild' to read: |
45 |
|
46 |
src_prepare() { |
47 |
epatch "${FILESDIR}"/${PN}-prefix-${PV}-r${PREFIXREV}.patch |
48 |
epatch "${FILESDIR}"/${P}-copy-gcc-libs.patch |
49 |
mv wrapper.c wrapper.c.in |
50 |
} |
51 |
|
52 |
and then regenerate the manifest (from a shell where EPREFIX and PATH have been |
53 |
exported), i.e. |
54 |
|
55 |
ebuild <path-to-gcc-config-1.8-r00.1.ebuild> manifest |
56 |
|
57 |
then you should be able to continue with building stage3. This worked for me. It |
58 |
is not a solution, just a band-aid. |
59 |
|
60 |
Steve |