From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Can't emerge any gcc
Date: Mon, 28 May 2012 08:01:59 +0700 [thread overview]
Message-ID: <CAA2qdGW1=b6cZ9jH5=5TfbT6EfmBthncrCuva_bcWMrTeP4_xg@mail.gmail.com> (raw)
In-Reply-To: <CALF0-+Xj+JM-1SQK5OduSZ_Rs0jBwnZs4r8W46va7okxJj+gWw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4503 bytes --]
On May 28, 2012 6:39 AM, "Ezequiel Garcia" <elezegarcia@gmail.com> 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'
>
What's your CFLAGS?
Rgds,
[-- Attachment #2: Type: text/html, Size: 5750 bytes --]
next prev parent reply other threads:[~2012-05-28 1:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-27 23:33 [gentoo-user] Can't emerge any gcc Ezequiel Garcia
2012-05-27 23:48 ` William Kenworthy
2012-05-28 0:08 ` Ezequiel Garcia
2012-05-28 1:49 ` W.Kenworthy
2012-05-29 11:28 ` Ezequiel Garcia
2012-05-28 0:18 ` Dale
2012-05-28 1:01 ` Pandu Poluan [this message]
2012-05-29 11:29 ` Ezequiel Garcia
2012-05-29 11:31 ` Ezequiel Garcia
2012-05-29 12:21 ` Ezequiel Garcia
2012-05-29 14:09 ` Ezequiel Garcia
2012-05-29 14:10 ` Alex Schuster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA2qdGW1=b6cZ9jH5=5TfbT6EfmBthncrCuva_bcWMrTeP4_xg@mail.gmail.com' \
--to=pandu@poluan.info \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox