| Summary: | >=gnustep-base/gnustep-gui-0.22.0 links against its own installed libraries (including on ICU upgrades with "ld: warning: libicuuc.so.48, needed by /usr/lib64/libgnustep-gui.so, not found") | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | José Romildo Malaquias <jrmalaq> |
| Component: | Current packages | Assignee: | Gentoo Gnustep project <gnustep> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | g.djavadyan, rion4ik |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | gnustep-base:gnustep-gui-0.22.0:20120425-112349.log | ||
It's linking against its own installed libraries, which fails because those need to be rebuilt because dev-libs/icu was upgraded. Confirmed, unmerging gnustep-gui and re-emerging resolves the problem. Might I suggest setting up an emerge block so it uninstalls in order to install gnustep-gui? Also got this while bumping the gnustep packages. It does not look like easy to fix, and adding a "!!" blocker will not be allowed if applications depending on gnustep are installed... Hmm tricky *** Bug 491396 has been marked as a duplicate of this bug. *** From upstream discussions, should be fixed with gnustep-gui-0.24.0 |
Created attachment 310037 [details] gnustep-base:gnustep-gui-0.22.0:20120425-112349.log gnustep-base/gnustep-gui-0.22.0 does not build on my ~amd64 system: [...] /usr/lib/gcc/x86_64-pc-linux-gnu/4.6.2/../../../../x86_64-pc-linux-gnu/bin/ld: warning: libicuuc.so.48, needed by /usr/lib64/libgnustep-gui.so, not found (try using -rpath or -rpath-link) /usr/lib64/libgnustep-gui.so: undefined reference to `u_getPropertyValueName_48' /usr/lib64/libgnustep-gui.so: undefined reference to `u_charName_48' /usr/lib64/libgnustep-gui.so: undefined reference to `u_strFromUTF32_48' /usr/lib64/libgnustep-gui.so: undefined reference to `u_enumCharNames_48' /usr/lib64/libgnustep-gui.so: undefined reference to `u_getIntPropertyValue_48' [...] This is happening with an up to date system, after running revdep-rebuild.