As the summary states. FEATURES=splitdebug results in debuginfo installed to /usr/lib/debug, while gdb looks for it in /usr/$(get_libdir). If /usr/lib is not a symlink to lib64, gdb is unable to find debuginfo.
Packages should be installing to $(get_libdir) then. *** This bug has been marked as a duplicate of bug 293361 ***
It's not the same bug. As I see that bug is about packages which install into /usr/lib/debug/lib or */lib64. My bug is about the overall fact that all packages install into /usr/lib/debug while gdb seems to look in /usr/lib64/debug. And the former location seems more correct as that directory contains 32-bit libs as well (in /usr/lib64/debug/usr/lib32/*).
Not to mention the fix seems as simple as passing '--with-separate-debug-dir=/usr/lib/debug' in the ebuild.
So the question is which is better: install into (for an ABI whose LIBDIR is lib32) - /usr/lib32/debug/{bin,lib32,...} - /usr/lib/debug/{bin,lib32,...}
(In reply to comment #4) > So the question is which is better: > > install into (for an ABI whose LIBDIR is lib32) > - /usr/lib32/debug/{bin,lib32,...} That would require patching gcc, I guess. It does support a single directory only. Unless we're requiring 32-bit users to use 32-bit gdb but I don't see a reason to. > - /usr/lib/debug/{bin,lib32,...} That's what portage does now.
i dont think gcc would need anything. splitdebug install is handled completely by portage in prepstrip. since everything else atm assumes a hard coded path of /usr/lib/debug, ive simply official-ized this in gdb itself. a sep discussion can be held on the gentoo-dev lists as to a better framework. http://sources.gentoo.org/sys-devel/gdb/gdb-7.3.ebuild?r1=1.3&r2=1.4 http://sources.gentoo.org/sys-devel/gdb/gdb-9999.ebuild?r1=1.1&r2=1.2
(dont take my last comment to mean i care one way or the other and that i think we need to discuss this on the gentoo-dev ml to death. the current system works fine by me and the alternative proposals dont really add anything imo.)
