Summary: | amd64 upgrade problems (specifically with libm), starting from 2005.1 64-bit Universal install CD | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Colin Fox <cfox> |
Component: | New packages | Assignee: | AMD64 Project <amd64> |
Status: | RESOLVED WORKSFORME | ||
Severity: | major | CC: | toolchain |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Colin Fox
2005-10-18 17:10:00 UTC
OK. When are you getting these errors? Is this on an emerge of new packages? Updates on current packages? Have you updated glibc since the release? Essentially, if things have changed since the release media, then we need to move this on to the proper maintainers. This is when doing an update. I basically just did this: 1. Installed from the 2005.1 universal 64 bit disk. 2. Did an emerge --sync 3. emerge -U world That's it. At some point, I noticed that it broke, complaining about libm. I've reverted the system back to what came from the install disk, and it's working fine. But I'm concerned that if I do an "emerge -U world" it will break again. OK. It works from the installation media. After the installation, it is giving errors. Got it. Thanks for the clarification. Hmm. I decided to go ahead and do an update. Everything is working fine. So to recap: I did an install from the disk and then an update. Something broke (looks like in a 64/32 bit compatability layer or something). I re-copied the /usr/ directory back over from the stage3 tarball, and did an update again. Now things are working. I noticed that when I did the update this time, it didn't have glibc in the list of items to update. Also, I don't think I changed anything specific to get this to work. But it's working now. So there is something fragile somewhere, but I'm not sure where. seems like the problem has been fixed between the first and the second sync. in any case, if you can't reproduce it anymore, we can't fix it ;) |