Re: [gentoo-amd64] Re: grub and glibc won't build on my new install

[Randy Barlow]

Duncan wrote:
> Your current profile looks good (it's a current 10th anniversary
> amd64 profile and isn't no-multilib), but you didn't mistakenly try a no-
> multilib version and compile some bits of the toolchain, did you?

Hey Duncan, thanks for the amazingly rapid reply! I'm just now getting 
around to trying some of this out (busy work week!) I definitely didn't 
choose the no-multilib tool chain itself, but I did try out the "server" 
[rofile. Was that potentially my mistake (i.e., is the "server" profile 
non-multilib?)

> Hmm, kernel config!  You have 32-bit executable format turned on in the
> kernel, right?  That's under Executable file formats / Emulations, IA32
> Emulation.  (It's not emulation, but anyway...)  If that's it, you're not
> the first one that's messed up, and probably won't be the last, either.

Well, I'm on the livecd. I assume that the live CD kernel has the 32-bit 
format enabled, otherwise how would you do what I'm trying to do? I did 
build 32-bit into the kernel that I made, but I haven't booted into that 
kernel yet since I can't build grub :)

> I haven't messed with VMs here (my machine doesn't have the hardware
> extensions, and I haven't particularly needed a slower software-only a VM
> for anything, so...), so I know not what if any options may need enabled
> there, in either the host or the VM.  If it's related to that, you'll
> need to find help from someone else.

I'd be surprised if this has something to do with virtualization, but 
hey, you could be right!

> One other possibility to try is FEATURES=-sandbox emerge sandbox.
> Multilib profiles include sandboxing libs for both 32-bit and 64-bit as
> well, and sometimes it's simply the 32-bit side of that which gets
> screwed up.  Of course, building sandbox requires 32-bit as well, but if
> it's just the 32-bit sandbox libs that are screwed,t then bypassing them
> to remerge sandbox itself will work, and hopefully the newly built
> sandbox will be functional.  If that fails with 32-bit errors as well,
> the problem is deeper in your toolchain, likely a screwed-up 32-bit gcc,
> or possibly a screwed-up 32-bit glibc.  It can also be binutils.

Unfortunately, an emerge -e world fails, which should build gcc, glibc, 
and binutils in the correct order. I'll give the sandbox trick a whirl.

Thanks for the reply, and I'll be sure to keep the list updated with my 
findings!