public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Mansour Al Akeel" <mansour.alakeel@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Can not compile gcc
Date: Fri, 14 Nov 2008 14:02:19 -0400	[thread overview]
Message-ID: <2a21586d0811141002p735a3839h74ec70ff8dd7f524@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 5087 bytes --]

Hello all, I have updated my use flags.

USE="X aac aiglx alsa aoss asf bzip2 cairo dbus dvd emerald fam firefox gif
     glitz gnome gstreamer gtk hal java jpeg mad mp3 mp4 new-login nptl
     nptlonly nsplugin opengl pdf png samba spell sqlite svg symlink threads
     tiff truetype unicode x264 xcomposite xinerama xml xorg xscreensaver xv
     xvid -arts -eds -esd -fortran -ipv6 -kde -qt3 -qt4"

And then tried :
emerge -vuD --newuse world

It failed with the error:
=============================================================
checking whether the C compiler works... configure: error: cannot run C
compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
make[2]: *** [configure-target-libstdc++-v3] Error 1
make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.1.2/work/build'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.1.2/work/build'
make: *** [profiledbootstrap] Error 2
 *
 * ERROR: sys-devel/gcc-4.1.2 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 4646:  Called toolchain_src_compile
 *             environment, line 5164:  Called gcc_src_compile
 *             environment, line 2972:  Called gcc_do_make
 *             environment, line 2795:  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}";
 *  The die message:
 *   emake failed with profiledbootstrap
 *
 * If you need support, post the topmost build error, and the call stack if
relevant.
 * A complete build log is located at
'/var/tmp/portage/sys-devel/gcc-4.1.2/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/sys-devel/gcc-4.1.2/temp/environment'.
 *

 * Messages for package app-editors/nano-2.1.5:

 * More helpful info about nano, visit the GDP page:
 * http://www.gentoo.org/doc/en/nano-basics-guide.xml

 * Messages for package sys-devel/gcc-4.1.2:

 *
 * ERROR: sys-devel/gcc-4.1.2 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 4646:  Called toolchain_src_compile
 *             environment, line 5164:  Called gcc_src_compile
 *             environment, line 2972:  Called gcc_do_make
 *             environment, line 2795:  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}";
 *  The die message:
 *   emake failed with profiledbootstrap
 *
 * If you need support, post the topmost build error, and the call stack if
relevant.
 * A complete build log is located at
'/var/tmp/portage/sys-devel/gcc-4.1.2/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/sys-devel/gcc-4.1.2/temp/environment'.
 *
 * Regenerating GNU info directory index...
 * Processed 132 info files.
 * IMPORTANT: 3 config files in '/etc' need updating.
 * See the CONFIGURATION FILES section of the emerge
 * man page to learn how to update config files.
=============================================================
The log file:

checking for x86_64-pc-linux-gnu-gcc...
/var/tmp/portage/sys-devel/gcc-4.1.2/work/build/./gcc/xgcc
-B/var/tmp/portage/sys-devel/gcc-4.1.2/work/build/./gcc/
-B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem
/usr/x86_64-pc-linux-gnu/include -isystem
/usr/x86_64-pc-linux-gnu/sys-include  -m32
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C
compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
make[2]: *** [configure-target-libstdc++-v3] Error 1
make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.1.2/work/build'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.1.2/work/build'
make: *** [profiledbootstrap] Error 2
 *
 * ERROR: sys-devel/gcc-4.1.2 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 4646:  Called toolchain_src_compile
 *             environment, line 5164:  Called gcc_src_compile
 *             environment, line 2972:  Called gcc_do_make
 *             environment, line 2795:  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}";
 *  The die message:
 *   emake failed with profiledbootstrap
 *
 * If you need support, post the topmost build error, and the call stack if
relevant.
 * A complete build log is located at
'/var/tmp/portage/sys-devel/gcc-4.1.2/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/sys-devel/gcc-4.1.2/temp/environment'.
 *


Any idea ?

[-- Attachment #2: Type: text/html, Size: 7362 bytes --]

             reply	other threads:[~2008-11-14 18:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-14 18:02 Mansour Al Akeel [this message]
2008-11-14 18:26 ` [gentoo-amd64] Can not compile gcc Barry Schwartz
2008-11-14 18:34   ` Justin
2008-11-14 19:31     ` Branko Badrljica
2008-11-14 18:40       ` Justin
2008-11-14 19:14         ` Mansour Al Akeel
2008-11-14 19:24           ` Beso
2008-11-14 19:30 ` [gentoo-amd64] " Duncan
2008-11-14 19:54   ` Mansour Al Akeel
2008-11-14 21:16     ` [gentoo-amd64] " Tonko Mulder
2008-11-14 21:23       ` Mansour Al Akeel
2008-11-14 23:44     ` [gentoo-amd64] " Duncan
2008-11-15  2:58       ` Mansour Al Akeel
2008-11-15  6:41         ` Duncan
2008-11-14 21:48 ` [gentoo-amd64] " Christoph Mende
2008-11-14 22:22   ` Mansour Al Akeel
2008-11-14 23:19     ` Branko Badrljica
2008-11-14 22:31       ` Beso
2008-11-14 23:10         ` Mansour Al Akeel
2008-11-14 23:26           ` Beso

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=2a21586d0811141002p735a3839h74ec70ff8dd7f524@mail.gmail.com \
    --to=mansour.alakeel@gmail.com \
    --cc=gentoo-amd64@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