Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 163975 - sys-devel/gcc-4.1.1-r1 emerge fails (probably due to linking problem with libc)
Summary: sys-devel/gcc-4.1.1-r1 emerge fails (probably due to linking problem with libc)
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: AMD64 Linux
: High normal
Assignee: AMD64 Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-26 20:23 UTC by tomas bonnedahl
Modified: 2007-02-05 07:58 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info and err msg from emerge (gcc_error,8.74 KB, text/plain)
2007-01-27 14:35 UTC, tomas bonnedahl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tomas bonnedahl 2007-01-26 20:23:20 UTC
Tried to update my system that hasn't been updated for a couple of months, I finally reached the update of GCC, which failed. 

I've tried using the common 'emerge -u gcc', I have also followed the guide at http://forums.gentoo.org/viewtopic-t-494331-highlight-gcc+64.html and the guide at  http://www.gentoo.org/doc/en/gcc-upgrading.xml#upgrade-general without success.

I think the problem lies with some 32/64bit problem. The system should be multilib, but 'ld' believes that "libc" is incompatible. Just before the error with ld, we can see that alot of 32bit stuff is happening. So, I believe that ld shouldn't use /usr/lib/gcc/x86_64-pc-linux-gnu/... because /usr/lib is a symlink to /usr/lib64 which is the 64bit version.

This could all be wrong of course, and it could be just my system this appears on. If it is, I'm sorry.

Reproducible: Always

Steps to Reproduce:
1.emerge -u gcc 
2.
3.

Actual Results:  
Error from 'ld', result can be seen on url.

Expected Results:  
gcc successfully emerged.
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2007-01-26 20:29:18 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.
Comment 2 tomas bonnedahl 2007-01-27 14:35:52 UTC
Created attachment 108289 [details]
emerge --info and err msg from emerge
Comment 3 tomas bonnedahl 2007-01-27 14:37:33 UTC
Reopening the bug. I removed the URL with information and attached a text file instead.
Comment 4 Simon Stelling (RETIRED) gentoo-dev 2007-01-27 22:13:15 UTC
How long did you not upgrade it? Did you switch profiles before doing this upgrade? If yes, which one was the old one?
Comment 5 tomas bonnedahl 2007-01-28 05:04:43 UTC
(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. 
Comment 6 tomas bonnedahl 2007-02-04 15:29:51 UTC
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
Comment 7 Simon Stelling (RETIRED) gentoo-dev 2007-02-04 17:23:43 UTC
> 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.
Comment 8 tomas bonnedahl 2007-02-05 07:58:16 UTC
> 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.