GCC and CHOST problem [solved]

Message

eXess · Post by **eXess** » Fri Mar 19, 2010 10:26 am

Hi there,

I'm having a problem while installing Gentoo Linux on a VMWare Fusion (for Mac) Virtual Machine.
Actually everything ran fine so far (though finding the correct kernel config was somewhat difficult)...

Now, I'm running into a strange problem while updating system and adding apps.

First, I ran into the known "gcc problem while updating busybox" problem :

Code: Select all

/bin/sh: i686-pc-linux-gnu-gcc: command not found
make[1]: *** [applets/applets.o] Error 127
make: *** [applets_dir] Error 2
 * ERROR: sys-apps/busybox-1.15.3 failed:
 *   build failed
 * 
 * Call stack:
 *     ebuild.sh, line  54:  Called src_compile
 *   environment, line 2682:  Called die
 * The specific snippet of code:
 *       emake busybox || die "build failed";
 * 
 * If you need support, post the output of 'emerge --info =sys-apps/busybox-1.15.3',
 * the complete build log and the output of 'emerge -pqv =sys-apps/busybox-1.15.3'.
 * The complete build log is located at '/var/tmp/portage/sys-apps/busybox-1.15.3/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/busybox-1.15.3/temp/environment'.
 * S: '/var/tmp/portage/sys-apps/busybox-1.15.3/work/busybox-1.15.3'

However, there seems to be something messy with GCC and/or GLIBC.

Here's my CHOST and CFLAGS in make.conf :

Code: Select all

CFLAGS="-O2 -march=core2 -pipe -fomit-frame-pointer -mmmx -msse2"
CXXFLAGS="${CFLAGS}"
CHOST="i686-pc-linux-gnu"

And then...

Code: Select all

# gcc-config -l
 [1] i486-pc-linux-gnu-4.3.4 *
# binutils-config -l
 [1] i686-pc-linux-gnu-2.18 *

Eeew ? Where is i686 ?

Is this normal ?

Code: Select all

# cat /etc/env.d/05gcc-i686-pc-linux-gnu 
PATH="/usr/i486-pc-linux-gnu/gcc-bin/4.3.4"
ROOTPATH="/usr/i486-pc-linux-gnu/gcc-bin/4.3.4"

# ls -al /etc/env.d/gcc/
total 20
drwxr-xr-x 2 root root 4096 Mar 19 10:52 .
drwxr-xr-x 5 root root 4096 Mar 19 11:09 ..
lrwxrwxrwx 1 root root   23 Mar 11 14:38 .NATIVE -> i486-pc-linux-gnu-4.3.4
-rw-r--r-- 1 root root   32 Feb 16 11:13 config-i486-pc-linux-gnu
-rw-r--r-- 1 root root   32 Mar 19 10:52 config-i686-pc-linux-gnu
-rw-r--r-- 1 root root  235 Feb 16 11:12 i486-pc-linux-gnu-4.3.4

# cat /etc/env.d/gcc/config-i486-pc-linux-gnu 
CURRENT=i486-pc-linux-gnu-4.3.4 

# cat /etc/env.d/gcc/config-i686-pc-linux-gnu 
CURRENT=i486-pc-linux-gnu-4.3.4

# cat /etc/env.d/gcc/i486-pc-linux-gnu-4.3.4 
LDPATH="/usr/lib/gcc/i486-pc-linux-gnu/4.3.4"
MANPATH="/usr/share/gcc-data/i486-pc-linux-gnu/4.3.4/man"
INFOPATH="/usr/share/gcc-data/i486-pc-linux-gnu/4.3.4/info"
STDCXX_INCDIR="g++-v4"
GCC_PATH="/usr/i486-pc-linux-gnu/gcc-bin/4.3.4"

I've rebuilt binutils, python, glibc, and now I'm in the process of re-emerging system (42/111 so far).
GCC won't compile (actually I had not yet rebuilt glibc when trying, I'll try that later if nothing works).

Could someone explain to me how I don't see the i686 profile when listing GCC profiles?
Thanks in advance. This is really starting to bug me...

eXess · Post by **eXess** » Fri Mar 19, 2010 12:05 pm

ok some news now : emerge -e system broke when trying to emerge busybox.
I then tried to re-emerge gcc, but it doesn't work.

Can someone PLEASE help?

I hope there's a way out of this. I really did install using by-the-book instructions. I changed my CHOST flag right away, install time. Never touched it before.

Jaglover · Post by **Jaglover** » Fri Mar 19, 2010 12:11 pm

I changed my CHOST flag right away, install time.

Not clear, you changed your CHOST? You were using 486 tarball?
Did you follow the guide http://www.gentoo.org/doc/en/change-chost.xml

Mike Hunt · Post by **Mike Hunt** » Fri Mar 19, 2010 1:23 pm

If you're just starting out a new install, then probably the easiest way to fix that is a complete restart.
Reformat the partition(s) and use the stage3-i686... tarball, then you should be fine.
Or follow the guide Jaglover recommends, (I guess he drives a Jag.)

I would suggest these flags, see Safe Cflags:-march=native

Code: Select all

CFLAGS="-march=native -O2 -pipe"
CXXFLAGS="${CFLAGS}"

eXess · Post by **eXess** » Fri Mar 19, 2010 2:03 pm

Thanks Mike, but actually this IS (nearly) a fresh install. Apart from emerge --sync (and setting up make.conf), nothing has been done on the system... except installing, which was not easy kernel-wise, as I said before.

So, if there REALLY is no other solution (or it's really too much trouble), I'll start over, but I'll really, really rather find a way to do otherwise. Starting over would mean re-syncing and finding a way to avoid kernel trouble

Is there really no way to declare a correct GCC profile and re-configuring the toolchain with not too much hassle?

[edit]
Hey, actually I noted that my CFLAGS are okay.
It's more about my CHOST and GCC profiles.
How do I emerge (or download, or write...) GCC profiles ?
[/edit]

cyrillic · Post by **cyrillic** » Sat Mar 20, 2010 12:38 am

eXess wrote:Is there really no way to declare a correct GCC profile and re-configuring the toolchain with not too much hassle?

Your CHOST change has not taken effect because you have not recompiled sys-devel/gcc yet.

Once you take care of that, gcc-config should show you the right thing (i686).

eXess · Post by **eXess** » Sat Mar 20, 2010 8:22 am

Except trying to compile GCC failed with the same error as when compiling busybox.
Well, in the meantime, I re-emerged things (such as libtool, etc.). I'll give it another try.

If re-emerging GCC fails again, maybe I should just boot on the LiveCD, chroot in my HD and then re-compile GCC ?
Would this help?

Thanks for any input

eXess · Post by **eXess** » Sat Mar 20, 2010 9:24 am

UPDATE

GCC re-emerged nicely and now I have

Code: Select all

# gcc-config -l 
 [1] i686-pc-linux-gnu-4.3.4 *
# gcc-config -c
i686-pc-linux-gnu-4.3.4

I'll mark this as solved, though I don't really know what did the trick. All I can say is that re-emerging system, libtool, glibc, python and gcc helped...

Thanks everyone.
This was a tough one...