Gentoo Archives: gentoo-user

From: Pandu Poluan <pandu@××××××.info>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Can't emerge any gcc
Date: Mon, 28 May 2012 01:04:19
Message-Id: CAA2qdGW1=b6cZ9jH5=5TfbT6EfmBthncrCuva_bcWMrTeP4_xg@mail.gmail.com
In Reply to: [gentoo-user] Can't emerge any gcc by Ezequiel Garcia
1 On May 28, 2012 6:39 AM, "Ezequiel Garcia" <elezegarcia@×××××.com> wrote:
2 >
3 > Hi,
4 >
5 > I can't emerge any gcc. I tried emerging 4.7, 4.5.3-r2 with no luck.
6 >
7 > Should I file a bug?
8 >
9 > Thanks,
10 > Ezequiel.
11 > ---
12 >
13 > Checking multilib configuration for libgomp...
14 > Configuring stage 1 in i686-pc-linux-gnu/libgomp
15 > configure: loading site script /usr/share/config.site
16 > configure: loading site script /usr/share/crossdev/include/site/linux
17 > configure: loading site script /usr/share/crossdev/include/site/linux-gnu
18 > configure: loading site script
19 /usr/share/crossdev/include/site/i686-linux-gnu
20 > configure: creating cache ./config.cache
21 > checking for --enable-version-specific-runtime-libs... no
22 > checking for --enable-generated-files-in-srcdir... no
23 > checking build system type... i686-pc-linux-gnu
24 > checking host system type... i686-pc-linux-gnu
25 > checking target system type... i686-pc-linux-gnu
26 > checking for a BSD-compatible install... /usr/bin/install -c
27 > checking whether build environment is sane... yes
28 > checking for a thread-safe mkdir -p... /bin/mkdir -p
29 > checking for gawk... gawk
30 > checking whether make sets $(MAKE)... yes
31 > checking for i686-pc-linux-gnu-gcc...
32 > /var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/./gcc/xgcc
33 > -B/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/./gcc/
34 > -B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/lib/ -isystem
35 > /usr/i686-pc-linux-gnu/include -isystem
36 > /usr/i686-pc-linux-gnu/sys-include
37 > checking for C compiler default output file name...
38 > configure: error: in
39 >
40 `/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/i686-pc-linux-gnu/libgomp':
41 > configure: error: C compiler cannot create executables
42 > See `config.log' for more details.
43 > make[2]: *** [configure-stage1-target-libgomp] Error 77
44 > make[2]: Leaving directory
45 `/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build'
46 > make[1]: *** [stage1-bubble] Error 2
47 > make[1]: Leaving directory
48 `/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build'
49 > make: *** [bootstrap-lean] Error 2
50 > emake failed
51 > * ERROR: sys-devel/gcc-4.5.3-r2 failed (compile phase):
52 > * emake failed with bootstrap-lean
53 > *
54 > * Call stack:
55 > * ebuild.sh, line 85: Called src_compile
56 > * environment, line 3866: Called toolchain_src_compile
57 > * environment, line 4507: Called gcc_do_make
58 > * environment, line 2223: Called die
59 > * The specific snippet of code:
60 > * emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}"
61 > LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET}
62 > || die "emake failed with ${GCC_MAKE_TARGET}";
63 > *
64 > * If you need support, post the output of 'emerge --info
65 > =sys-devel/gcc-4.5.3-r2',
66 > * the complete build log and the output of 'emerge -pqv
67 > =sys-devel/gcc-4.5.3-r2'.
68 > *
69 > * Please include
70 > /var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/gcc-build-logs.tar.bz2
71 > in your bug report
72 > *
73 > * The complete build log is located at
74 > '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/build.log'.
75 > * The ebuild environment file is located at
76 > '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/environment'.
77 > * S: '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build'
78 >
79 > >>> Failed to emerge sys-devel/gcc-4.5.3-r2, Log file:
80 >
81 > >>> '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/build.log'
82 >
83 > * Messages for package sys-devel/gcc-4.5.3-r2:
84 >
85 > * ERROR: sys-devel/gcc-4.5.3-r2 failed (compile phase):
86 > * emake failed with bootstrap-lean
87 > *
88 > * Call stack:
89 > * ebuild.sh, line 85: Called src_compile
90 > * environment, line 3866: Called toolchain_src_compile
91 > * environment, line 4507: Called gcc_do_make
92 > * environment, line 2223: Called die
93 > * The specific snippet of code:
94 > * emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}"
95 > LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET}
96 > || die "emake failed with ${GCC_MAKE_TARGET}";
97 > *
98 > * If you need support, post the output of 'emerge --info
99 > =sys-devel/gcc-4.5.3-r2',
100 > * the complete build log and the output of 'emerge -pqv
101 > =sys-devel/gcc-4.5.3-r2'.
102 > *
103 > * Please include
104 > /var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/gcc-build-logs.tar.bz2
105 > in your bug report
106 > *
107 > * The complete build log is located at
108 > '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/build.log'.
109 > * The ebuild environment file is located at
110 > '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/environment'.
111 > * S: '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build'
112 >
113
114 What's your CFLAGS?
115
116 Rgds,

Replies

Subject Author
Re: [gentoo-user] Can't emerge any gcc Ezequiel Garcia <elezegarcia@×××××.com>