public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
Search results ordered by [date|relevance]  view[summary|nested|Atom feed]
thread overview below | download: 
* Re: [gentoo-user] Can't emerge any gcc
  @ 2012-05-27 23:48 99% ` William Kenworthy
  0 siblings, 0 replies; 1+ results
From: William Kenworthy @ 2012-05-27 23:48 UTC (permalink / raw
  To: gentoo-user

probably not, you will need some more info as its a bit vague:

What does "gcc -v" say?

and "gcc-config -l"

Can you compile anything, either through emerge or manually (i.e., even
a  small "hello world")

Need to narrow it down.

BillK




On Sun, 2012-05-27 at 20:33 -0300, Ezequiel Garcia wrote:
> Hi,
> 
> I can't emerge any gcc. I tried emerging 4.7, 4.5.3-r2 with no luck.
> 
> Should I file a bug?
> 
> Thanks,
> Ezequiel.
> ---
> 
> Checking multilib configuration for libgomp...
> Configuring stage 1 in i686-pc-linux-gnu/libgomp
> configure: loading site script /usr/share/config.site
> configure: loading site script /usr/share/crossdev/include/site/linux
> configure: loading site script /usr/share/crossdev/include/site/linux-gnu
> configure: loading site script /usr/share/crossdev/include/site/i686-linux-gnu
> configure: creating cache ./config.cache
> checking for --enable-version-specific-runtime-libs... no
> checking for --enable-generated-files-in-srcdir... no
> checking build system type... i686-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
> checking target system type... i686-pc-linux-gnu
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking for i686-pc-linux-gnu-gcc...
> /var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/./gcc/xgcc
> -B/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/./gcc/
> -B/usr/i686-pc-linux-gnu/bin/ -B/usr/i686-pc-linux-gnu/lib/ -isystem
> /usr/i686-pc-linux-gnu/include -isystem
> /usr/i686-pc-linux-gnu/sys-include
> checking for C compiler default output file name...
> configure: error: in
> `/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/i686-pc-linux-gnu/libgomp':
> configure: error: C compiler cannot create executables
> See `config.log' for more details.
> make[2]: *** [configure-stage1-target-libgomp] Error 77
> make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build'
> make[1]: *** [stage1-bubble] Error 2
> make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build'
> make: *** [bootstrap-lean] Error 2
> emake failed
>  * ERROR: sys-devel/gcc-4.5.3-r2 failed (compile phase):
>  *   emake failed with bootstrap-lean
>  *
>  * Call stack:
>  *     ebuild.sh, line   85:  Called src_compile
>  *   environment, line 3866:  Called toolchain_src_compile
>  *   environment, line 4507:  Called gcc_do_make
>  *   environment, line 2223:  Called die
>  * The specific snippet of code:
>  *       emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}"
> LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET}
> || die "emake failed with ${GCC_MAKE_TARGET}";
>  *
>  * If you need support, post the output of 'emerge --info
> =sys-devel/gcc-4.5.3-r2',
>  * the complete build log and the output of 'emerge -pqv
> =sys-devel/gcc-4.5.3-r2'.
>  *
>  * Please include
> /var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/gcc-build-logs.tar.bz2
> in your bug report
>  *
>  * The complete build log is located at
> '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/build.log'.
>  * The ebuild environment file is located at
> '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/environment'.
>  * S: '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build'
> 
> >>> Failed to emerge sys-devel/gcc-4.5.3-r2, Log file:
> 
> >>>  '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/build.log'
> 
>  * Messages for package sys-devel/gcc-4.5.3-r2:
> 
>  * ERROR: sys-devel/gcc-4.5.3-r2 failed (compile phase):
>  *   emake failed with bootstrap-lean
>  *
>  * Call stack:
>  *     ebuild.sh, line   85:  Called src_compile
>  *   environment, line 3866:  Called toolchain_src_compile
>  *   environment, line 4507:  Called gcc_do_make
>  *   environment, line 2223:  Called die
>  * The specific snippet of code:
>  *       emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}"
> LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET}
> || die "emake failed with ${GCC_MAKE_TARGET}";
>  *
>  * If you need support, post the output of 'emerge --info
> =sys-devel/gcc-4.5.3-r2',
>  * the complete build log and the output of 'emerge -pqv
> =sys-devel/gcc-4.5.3-r2'.
>  *
>  * Please include
> /var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/gcc-build-logs.tar.bz2
> in your bug report
>  *
>  * The complete build log is located at
> '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/build.log'.
>  * The ebuild environment file is located at
> '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/environment'.
>  * S: '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build'
> 





^ permalink raw reply	[relevance 99%]

Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2012-05-27 23:33     [gentoo-user] Can't emerge any gcc Ezequiel Garcia
2012-05-27 23:48 99% ` William Kenworthy

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox