Summary: | emerge gcc (4.1.1) fails | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Hong Zhou <hong> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED NEEDINFO | ||
Severity: | major | ||
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Hong Zhou
2006-09-02 17:53:57 UTC
you posted an error that looks like multilib issues ... that cant be the same bug on both x86 and amd64 is your glibc multilib built correctly ? (In reply to comment #1) > you posted an error that looks like multilib issues ... that cant be the same > bug on both x86 and amd64 > > is your glibc multilib built correctly ? > Both machines are complete new installation. What I did was very simple: 1. Install Gentoo 2006.1 2. emerge gentoo-sources, genkernel, grub etc. 3. genkerel --menuconfig all; grub-install etc. 4. reboot 5. emerge gcc and it fails (In reply to comment #1) > you posted an error that looks like multilib issues ... that cant be the same > bug on both x86 and amd64 > > is your glibc multilib built correctly ? > I'm quite sure this bug is reproducible on new installation (Gentoo 2006.1) as I reinstall the system on a Dell PE1855 server 3 times. The results of emerge gcc are the same. maybe, but it is impossible for you to have the same error that you posted here in both an amd64 and an i686 install what does this show on your machine: echo 'int main(){}' > test.c gcc -m32 test.c -o test ./test post the config.log files from the /var/tmp/portage/gcc-4.1.1/ dir as attachments also, why are you even bothering to re-emerge gcc ? 2006.1 has 4.1.1 in it |