| Summary: | glibc-2.4-r4 fails to build multilib due to old eselect-compiler wrappers | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jacob Matthews <tychver> |
| Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | volkerarmin |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge --info
glibc error and stack |
||
|
Description
Jacob Matthews
2006-10-02 03:23:52 UTC
Created attachment 98588 [details]
emerge --info
How about posting some errors? Created attachment 98594 [details]
glibc error and stack
(In reply to comment #2) > How about posting some errors? > Sorry about that, got distracted halfway through posting. try running `gcc-config` to reselect your profile and emerge again Thanks. glibc built successfully. As suggested, running gcc-config fixed this problem for me.
When I ran `gcc-config -l', x86_64-pc-linux-gnu-4.1.1 was already listed as the default compiler, so I ran `gcc-config -f x86_64-pc-linux-gnu-4.1.' to force regeneration.
Since I had to remove eselect-compiler to upgrade to a new version of gcc-config just recently, should I file a bug against gcc-config for leaving my system in a state where glibc couldn't be compiled?
no, it isnt the fault of gcc-config ... you didnt upgrade gcc-config recently, i added the blocker without rev-bumping it eselect-compiler still had crap left on your system which running gcc-config replaced *** Bug 150013 has been marked as a duplicate of this bug. *** |