| Summary: | sys-devel/gcc-4.1.1-r1 emerge fails (probably due to linking problem with libc) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | tomas bonnedahl <tomas> |
| Component: | [OLD] Core system | Assignee: | AMD64 Project <amd64> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | emerge --info and err msg from emerge | ||
|
Description
tomas bonnedahl
2007-01-26 20:23:20 UTC
Please, don't refer to third party links like pastebins when reporting bugs; makes bugs useless in days. Post/attach all the relevant info here and reopen then. Created attachment 108289 [details]
emerge --info and err msg from emerge
Reopening the bug. I removed the URL with information and attached a text file instead. How long did you not upgrade it? Did you switch profiles before doing this upgrade? If yes, which one was the old one? (In reply to comment #4) > How long did you not upgrade it? Did you switch profiles before doing this > upgrade? If yes, which one was the old one? > I installed the box in August/September 2006 with profile 2006.0. I did try to upgrade it using the old profile, that didn't work so I thought I upgrade the profile to 2006.1/desktop, but the same err came. Nothing is special with this box, just regular Gentoo desktop user with a AMD64 processor. I have some new information regarding this "bug". It seems gcc-3.4.6 was built using --disable-multilib (probably with a no-multilib profile). As I said I tried to change the profile to 2006.1/Desktop and reemerge gcc with multilib support but without success. I believe this bug is only happening on my system and hence shouldn't be here. I will however be greatful if someone knows how to fix this without having to reinstall. More information can be found in this thread: http://forums.gentoo.org/viewtopic-t-537106.html > I believe this bug is only happening on my system and hence shouldn't be here. Indeed, it's not a bug. > I will however be greatful if someone knows how to fix this without having to > reinstall. Short answer: There is no way, unfortunately. Long answer: There is no way, unfortunately. However, you can _try_ to unpack a stage3 over the old system, revdep-rebuild, then update again, then revdep-rebuild again. However, this is still not safe and pretty time-consuming, you might be better of with a complete reinstall. > Long answer: There is no way, unfortunately. However, you can _try_ to unpack a
> stage3 over the old system, revdep-rebuild, then update again, then
> revdep-rebuild again. However, this is still not safe and pretty
> time-consuming, you might be better of with a complete reinstall.
>
Thank you and sorry for the bug post. I think Ill try it before the re-install.
|