Re: Could the multiarch wiki page be explicit about pkgconfig files?

[Jakub Wilk <jwilk@debian.org>]

* Simon McVittie <smcv@debian.org>, 2011-09-19, 18:56:
> > The correct place for debug files is a hash-based path, instead of the 
> > crapfuck we have today.
>
> ... but until then, for gdb to pick them up, debug symbols for $THING 
> must be in /usr/lib/debug/$THING (a general rule, independent of 
> multiarch), resulting in paths like
>
>    /usr/lib/debug/lib/x86_64-linux-gnu/libdbus-1.so.3.6.3
>    /usr/lib/debug/usr/bin/dbus-send
>
> for a typical multi-arch library and executable (those two are in 
> dbus-dbg).
>
> This means any -dbg package that contains symbols for an executable 
> can't have the Multi-Arch flag set on it yet,

Not everybody was paying attention to this issue when multiarchifying 
their packages. A few of them have "Multi-Arch: same" set, but contain 
files in /usr/lib/debug/bin or such:

libpango1.0-0-dbg
libpcre3-dbg
liblua5.1-0-dbg
libgtk2.0-0-dbg
libc0.1-dbg
libc6-dbg
libnss3-1d-dbg
librsvg2-dbg

> until we have the hash-based paths Josselin mentions.

If you can't wait for proper build-id support in debhelper, you can use 
this hacky debhelper script (to be called after dh_strip):
http://anonscm.debian.org/viewvc/python-modules/packages/gamera/trunk/debian/dh_buildid?view=co

--
Jakub Wilk