Summary: | glibc 2.3.6-r4 lib / lib64 broken link | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Lorand Kelemen <lorand.kelemen> |
Component: | [OLD] Core system | Assignee: | AMD64 Project <amd64> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | thedude0001 |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Lorand Kelemen
2006-09-22 07:34:14 UTC
Uhm, it is being created at /usr/lib64 (for the 64bit version, the 32bit is created at /usr/lib32), /usr/lib is only a symlink to /usr/lib64 on a normal profile. Did any error actually pop up for you? Please check 'equery f glibc | grep gconv', it should show you that those files are instaled into /usr/lib64 and /usr/lib32. Closing because I don't think we actually have a bug here. If the files are installed somewhere else (or some other error popped up related to this) please feel free to reopen this bug. This is the known hardened problem. I can't find the other bug right now, but it basically bails down to the following: Your /usr/lib is a directory when it should be a link to /usr/lib64. To fix this, do: # cd /usr # cp -rp lib/* lib64 # rmdir lib # ln -s lib64 lib and the same with a cd / instead of /usr of course. You mean bug 132135? (Though that one doesn't mention hardened...) |