severity 689071 wishlist
block 689071 by 631275
thanks
On Fri, 28 Sep 2012 at 23:43:30 +0200, Francois Gouget wrote:
> The amd64 version conflicts with the i386 one which makes it impossible
> to install both. As a result the /usr/lib/i386-linux-gnu/libdbus-1.so
> symbolic link is missing so that developping 32bit applications using
> this library is impossible on a 64bit system.
Noted, but blocked by the wheezy release freeze. If you need to develop
i386 applications on an amd64 system under Debian wheezy, you will need
an i386 chroot, or possibly (less reliably) a mostly-amd64 multiarch chroot
that contains libdbus-1-dev:i386 instead of libdbus-1-dev:amd64.
> My understanding is that as long as there are no hardware-dependent
> headers there is no obstacle (i.e. no toolchain issue) to tagging
> the development package as 'Multi-Arch: same'.
We do have hardware-dependent headers, making dbus a non-trivial case
of multiarch -dev (just like glib2.0):
/usr/lib/TUPLE/dbus-1.0/include/dbus/dbus-arch-deps.h embeds knowledge
of word sizes, because D-Bus is portable to platforms like Windows/MSVC++
which do not have a C99 stdint.h or inttypes.h.
libdbus-1-dev also depends on pkg-config, but pkg-config is not
multiarch-ready yet (#631275). Ubuntu's pkg-config 0.26-1ubuntu1 would
probably work. Blocking this bug accordingly.
S
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
