View previous topic :: View next topic |
Author |
Message |
Fenster Apprentice
Joined: 26 Oct 2004 Posts: 172 Location: Purgatory
|
Posted: Fri Dec 01, 2006 10:57 pm Post subject: [Solved] No C++ compiler?! |
|
|
This is a weird one, I'm going through a new Gentoo installation on a 15" MBP, with portage frequently erroring out with a message that no c++ compiler is to be found. I'm installing off the live CD, using the 2006.1 x86 stage 1.
Code: | CFLAGS="-O2 -march=prescott -fomit-frame-pointer -pipe"
CHOST="i686-pc-linux-gnu"
ACCEPT_KEYWORDS="~x86"
CXXFLAGS="${CFLAGS}"
MAKEOPTS="-j4"
USE="gtk gtk2 alsa jpeg png tiff gnome mp3 svg -kde -qt -ncurses truetype wifi" |
GPM:
Code: | checking whether we are using the GNU C++ compiler... no
checking whether g++ accepts -g... no
checking C++ compiler g++ -O2 -march=prescott -fomit-frame-pointer -pipe... no
configure: error: C++ compiler not available, see config.log for details
!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/dev-libs/gmp-4.2.1/work/gmp-4.2.1/config.log
!!! ERROR: dev-libs/gmp-4.2.1 failed.
Call stack:
ebuild.sh, line 1568: Called dyn_compile
ebuild.sh, line 937: Called src_compile
gmp-4.2.1.ebuild, line 42: Called econf '--localstatedir=/var/state/gmp' '--disable-mpfr' '--disable-mpbsd' '--enable-cxx'
ebuild.sh, line 540: Called die
!!! econf failed
!!! If you need support, post the topmost build error, and the call stack if relevant. |
Udev:
Code: |
>>> Compiling source in /var/tmp/portage/sys-fs/udev-103/work/udev-103 ...
/usr/bin/i686-pc-linux-gnu-ar
get_libdir = lib
GENHDR udev_version.h
CC udev_device.o
make: i686-pc-linux-gnu-gcc: Command not found
make: *** [udev_device.o] Error 127
!!! ERROR: sys-fs/udev-103 failed.
Call stack:
ebuild.sh, line 1568: Called dyn_compile
ebuild.sh, line 937: Called src_compile
udev-103.ebuild, line 78: Called die
!!! (no error message)
!!! If you need support, post the topmost build error, and the call stack if relevant. |
Code: | GCC indicates that I am using it:
livecd / # gcc-config -l
[1] i386-pc-linux-gnu-4.1.1 * |
Last edited by Fenster on Fri Dec 01, 2006 11:45 pm; edited 1 time in total |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54237 Location: 56N 3W
|
Posted: Fri Dec 01, 2006 11:10 pm Post subject: |
|
|
Fenster,
You have changed your CHOST. Thats a VeryBadThing.
You have Code: | CHOST="i686-pc-linux-gnu" | but your GCC says Code: | i386-pc-linux-gnu-4.1.1 | Notice the i686 and i386.
There is a process you need to go through to do that because the various system tools have CHOST embedded in them. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
Fenster Apprentice
Joined: 26 Oct 2004 Posts: 172 Location: Purgatory
|
Posted: Fri Dec 01, 2006 11:45 pm Post subject: |
|
|
Doh, duly noted, fixed and marking as solved. Thank'ee. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|