| Summary: | zlib - "broken" symlink when ROOT is not / | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | David Bélanger <dbelan2> |
| Component: | New packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Fixes the bug | ||
Created attachment 46192 [details, diff]
Fixes the bug
err that's a bad idea and not really how ROOT is supposed to be utilized
setup your LDFLAGS to do -L${ROOT}/lib and -L${ROOT}/usr/lib and you should be fine
|
When I emerge zlib to a different ROOT than /, the ${ROOT}/usr/lib/libz.so symlink points to /lib/libz.so. See patch attached. Reproducible: Always Steps to Reproduce: 1. mkdir /usr/local/cross-root 2. ROOT=/usr/local/cross-root emerge -av zlib 3. Actual Results: I get symlink /usr/local/cross-root/usr/lib/libz.so -> /lib/libz.${PV} Expected Results: symlink /usr/local/cross-root/usr/lib/libz.so -> /usr/local/cross-root/lib/libz.${PV} So I can compile (cross-compile in my case) applications linked with libz.