Summary: | During 2004.3 to 2005 manual upgrade emerge glibc fails during configure. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Hal Engel <hvengel> |
Component: | Eclasses | Assignee: | AMD64 Project <amd64> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge info
config.log file |
Description
Hal Engel
2005-03-29 16:54:13 UTC
*** Bug 87187 has been marked as a duplicate of this bug. *** you neglected to provide `emerge info` like the bug report page said to also, post the config.log files from the build directory as attachments then re-open Created attachment 54801 [details]
emerge info
Created attachment 54802 [details]
config.log file
Requested files have been attached to the bug report. /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.3/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find /emul/linux/x86/lib/libc.so.6 looks like you missed code listing 4: # emerge -v --oneshot '>=emul-linux-x86-glibc-2.3.4.20041102' I am not sure what happend but I am sure that I didn't miss the step but perhaps it didn't work correctly. It appears to me that once the profile is set to 2005 then emul-linux-x86-glibc emerges differently. So it does not work to just re-emerge emul...glibc - I had already tried that yesterday. So I changed the profile back to 2004.3 and it still didn't work. Then I recreated the symlinks from /lib32 and /usr/lib32 to /emul... Then started over. I am now compiling glibc and it is well past where it failed before. So I will change the status to Resolved invalid since it appears that either I messed up (user error) or there was a hickup the first time I ran through the process. |