[SOLVED] gcc compilation problem

[windex]

EDIT: My particular problems were caused because I foolishly choose to install gentoo without the use of a multilib profile. Something that I shan't repeat in the foreseeable future, let's hope.

Hey. I'm having some trouble compiling gcc.

Emerge gcc

resulted in:
/usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory

I tried
to sync portage and rebuild but got a similar error

For example:

Here is gcc -v :
http://codepad.org/69bZuq4i

Here is /etc/portage/make.conf :
http://codepad.org/DteS8bjr

I copied the build log to:
http://codepad.org/432Dm06B

[Hu]

What is the output of emerge --info sys-libs/glibc sys-devel/gcc?

[windex]

[krinn]

Portage 2.2.8-r1 (hardened/linux/amd64/selinux, gcc-4.7.3, glibc-2.17, 3.12.13-gentoo x86_64)

sys-libs/glibc-2.17 was built with the following:
USE="hardened -debug -gd (-multilib) -nscd -profile (-selinux) -suid -systemtap -vanilla" ABI_X86="64"

FEATURES="assume-digests binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles merge-sync news parallel-fetch preserve-libs protect-owned sandbox selinux... "



selinux everywhere but not for your glibc?

[Hu]

I would be more concerned about him using a multilib profile with a no-multilib glibc. You need a multilib glibc installed before you can build multilib glibc/gcc. OP has a no-multilib glibc installed.

[windex]

Thanks guys.

I'm trying to decide if I should dump the SElinux configuration at that point.

Obviously, it's overkill for what I'm trying to do, but since I'll need to learn SElinux eventually now might actually be a good time.

Can I get some personal advice? Should I focus on solving he multilib problem right now, or should I be focusing on learning SElinux principles?

[Hu]

SELinux is a very deep hole. Get your system into a consistent state before you try to learn SELinux.

[windex]

Thanks to both of you for your advice. I've been doing some background reading on SELinux and agree that I have a ways to go before I am ready. Instead we can focus on getting multilib going.
The first thing I did was use eselect to change my profile.

Afterwards, eselect profile list produces:

[Hu]

Yes, a reinstall is usually the recommended course to convert from no-multilib to multilib. However, in your case, you are most of the way through a reinstall already, albeit with the newly installed system buried in /home/multilib. With some careful directory rearrangement, and enough free space, you could use the LiveCD environment to move your existing install to a subdirectory, then copy/move the multilib environment to the root of the filesystem, so that your next reboot uses the multilib environment as a root filesystem. If that all works, you can then use the subdirectory containing your no-multilib environment as a reference to verify you set all the configuration files the way you want, then remove the no-multilib subdirectory.

Your variation of using /etc/portage/make.conf is correct. In older systems, it was /etc/make.conf. The reference blog used the older name.

[windex]

[krinn]

If you re-install, i wonder how you get to that state, but your current glibc don't have 32bits version, so your glibc wasn't built with multilib.

portage output () a package that is force enable/disable. So (multilib) mean in your case : force enabling multilib, something using a multilib profile will normally force enable of course.
but the * in it, also mean its previous state wasn't the one display. So it tell you previous state was with -multilib and now it is force enable.
Wonder again, how you did that reinstall so.

And check codepad.org usage, no idea if the service is buggy or you, but it cut down the output leaving us out with the part where error appears.

A simple solve to your problem: go there and grab ready-made binaries for your toolchain :
http://tinderbox.dev.gentoo.org/hardened/amd64/

download and install glibc and gcc to have ones with multilib enable on your system, and try keep going (better get binutils while you are at it)
remember to install the same version as the packages you grab and make sure you use the --usepkgonly
and use --pretend to see emerge understand what you are trying to do, you don't want emerge gcc, you want emerge "that gcc" package (the one you have download), the pretend output should be in pink/violet color instead of the green color on package name and you should get binary instead of ebuild as

[windex]