From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SYoNZ-0008Nv-Gv for garchives@archives.gentoo.org; Mon, 28 May 2012 01:04:19 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 25E09E0841; Mon, 28 May 2012 01:03:54 +0000 (UTC) Received: from svr-us4.tirtonadi.com (svr-us4.tirtonadi.com [69.65.43.212]) by pigeon.gentoo.org (Postfix) with ESMTP id D4712E0793 for ; Mon, 28 May 2012 01:02:02 +0000 (UTC) Received: from mail-vb0-f53.google.com ([209.85.212.53]) by svr-us4.tirtonadi.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.69) (envelope-from ) id 1SYoLS-000wf8-Fv for gentoo-user@lists.gentoo.org; Mon, 28 May 2012 08:02:02 +0700 Received: by vbbfc26 with SMTP id fc26so1961091vbb.40 for ; Sun, 27 May 2012 18:01:59 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.52.89.226 with SMTP id br2mr5731432vdb.83.1338166919876; Sun, 27 May 2012 18:01:59 -0700 (PDT) Received: by 10.220.81.202 with HTTP; Sun, 27 May 2012 18:01:59 -0700 (PDT) Received: by 10.220.81.202 with HTTP; Sun, 27 May 2012 18:01:59 -0700 (PDT) In-Reply-To: References: Date: Mon, 28 May 2012 08:01:59 +0700 Message-ID: Subject: Re: [gentoo-user] Can't emerge any gcc From: Pandu Poluan To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=20cf307cff74e8d06c04c10e4368 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - svr-us4.tirtonadi.com X-AntiAbuse: Original Domain - lists.gentoo.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - poluan.info X-Archives-Salt: 10bc7b26-f895-4cdd-9a3a-0e441fef1545 X-Archives-Hash: 2b4134b74e608403deb07a37de4fe2de --20cf307cff74e8d06c04c10e4368 Content-Type: text/plain; charset=UTF-8 On May 28, 2012 6:39 AM, "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' > What's your CFLAGS? Rgds, --20cf307cff74e8d06c04c10e4368 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


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 luc= k.
>
> 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<= br> > configure: loading site script /usr/share/crossdev/include/site/linux-= gnu
> configure: loading site script /usr/share/crossdev/include/site/i686-l= inux-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/wo= rk/build'
> make[1]: *** [stage1-bubble] Error 2
> make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.5.3-r2/wo= rk/build'
> make: *** [bootstrap-lean] Error 2
> emake failed
> =C2=A0* ERROR: sys-devel/gcc-4.5.3-r2 failed (compile phase):
> =C2=A0* =C2=A0 emake failed with bootstrap-lean
> =C2=A0*
> =C2=A0* Call stack:
> =C2=A0* =C2=A0 =C2=A0 ebuild.sh, line =C2=A0 85: =C2=A0Called src_comp= ile
> =C2=A0* =C2=A0 environment, line 3866: =C2=A0Called toolchain_src_comp= ile
> =C2=A0* =C2=A0 environment, line 4507: =C2=A0Called gcc_do_make
> =C2=A0* =C2=A0 environment, line 2223: =C2=A0Called die
> =C2=A0* The specific snippet of code:
> =C2=A0* =C2=A0 =C2=A0 =C2=A0 emake LDFLAGS=3D"${LDFLAGS}" ST= AGE1_CFLAGS=3D"${STAGE1_CFLAGS}"
> LIBPATH=3D"${LIBPATH}" BOOT_CFLAGS=3D"${BOOT_CFLAGS}&qu= ot; ${GCC_MAKE_TARGET}
> || die "emake failed with ${GCC_MAKE_TARGET}";
> =C2=A0*
> =C2=A0* If you need support, post the output of 'emerge --info
> =3Dsys-devel/gcc-4.5.3-r2',
> =C2=A0* the complete build log and the output of 'emerge -pqv
> =3Dsys-devel/gcc-4.5.3-r2'.
> =C2=A0*
> =C2=A0* Please include
> /var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/gcc-build-logs.tar.= bz2
> in your bug report
> =C2=A0*
> =C2=A0* The complete build log is located at
> '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/build.log'.
> =C2=A0* The ebuild environment file is located at
> '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/environment'. > =C2=A0* 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:
>
> >>> =C2=A0'/var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/b= uild.log'
>
> =C2=A0* Messages for package sys-devel/gcc-4.5.3-r2:
>
> =C2=A0* ERROR: sys-devel/gcc-4.5.3-r2 failed (compile phase):
> =C2=A0* =C2=A0 emake failed with bootstrap-lean
> =C2=A0*
> =C2=A0* Call stack:
> =C2=A0* =C2=A0 =C2=A0 ebuild.sh, line =C2=A0 85: =C2=A0Called src_comp= ile
> =C2=A0* =C2=A0 environment, line 3866: =C2=A0Called toolchain_src_comp= ile
> =C2=A0* =C2=A0 environment, line 4507: =C2=A0Called gcc_do_make
> =C2=A0* =C2=A0 environment, line 2223: =C2=A0Called die
> =C2=A0* The specific snippet of code:
> =C2=A0* =C2=A0 =C2=A0 =C2=A0 emake LDFLAGS=3D"${LDFLAGS}" ST= AGE1_CFLAGS=3D"${STAGE1_CFLAGS}"
> LIBPATH=3D"${LIBPATH}" BOOT_CFLAGS=3D"${BOOT_CFLAGS}&qu= ot; ${GCC_MAKE_TARGET}
> || die "emake failed with ${GCC_MAKE_TARGET}";
> =C2=A0*
> =C2=A0* If you need support, post the output of 'emerge --info
> =3Dsys-devel/gcc-4.5.3-r2',
> =C2=A0* the complete build log and the output of 'emerge -pqv
> =3Dsys-devel/gcc-4.5.3-r2'.
> =C2=A0*
> =C2=A0* Please include
> /var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build/gcc-build-logs.tar.= bz2
> in your bug report
> =C2=A0*
> =C2=A0* The complete build log is located at
> '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/build.log'.
> =C2=A0* The ebuild environment file is located at
> '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/temp/environment'. > =C2=A0* S: '/var/tmp/portage/sys-devel/gcc-4.5.3-r2/work/build'= ;
>

What's your CFLAGS?

Rgds,

--20cf307cff74e8d06c04c10e4368--