On Thu, 1 Mar 2007 23:47:12 +0000 Neil Williams <[EMAIL PROTECTED]> wrote:
> This is an automatic check - if bluez is detected on the build machine,
> pilot-link will try to use it. Not ideal, but I've tried to build with
> --without-bluez but the build fails - seems upstream doesn't handle
> --without-bluez cleanly.
I've tried to build pilot-link in the amd64 chroot with
libbluetooth2-dev in debian/control for libpisock-dev and I've tried to
build pilot-link in the amd64 chroot also using --with-bluez but NEITHER
actually enables Bluez support in pilot-link when built inside a chroot!!
debian/control:
Source: pilot-link
Section: otherosfs
Build-Depends: debhelper (>= 5.0.37.2), perl (>= 5.6), libpng-dev,
libreadline5-dev | libreadline-dev, dpatch, python-dev (>= 2.3),
python-support (>= 0.3), libusb-dev, libbluetooth2-dev
Package: libpisock-dev
Architecture: any
Section: libdevel
Priority: extra
Depends: libpisock9 (= ${Source-Version}), libpisync0 (=
${Source-Version}), libncurses-dev|libncurses5-dev, libusb-dev,
libbluetooth2-dev
debian/rules:
./configure --prefix=/usr \
--enable-conduits --enable-libusb \
--with-perl --with-python --with-libpng \
--with-libiconv --with-bluez \
CC="$(CC)" CFLAGS="$(CFLAGS)"
An amd64 pbuilder run with this setup gives:
Package: libpisock9
Version: 0.12.2-4
Section: libs
Priority: optional
Architecture: amd64
Depends: libc6 (>= 2.3.5-1), libusb-0.1-4 (>= 2:0.1.12)
Package: libpisock-dev
Version: 0.12.2-4
Section: libdevel
Priority: extra
Architecture: amd64
Depends: libpisock9 (= 0.12.2-4), libpisync0 (= 0.12.2-4),
libncurses-dev | libncurses5-dev, libusb-dev, libbluetooth2-dev
A manual build with debuild (with no changes except those above) gives:
Package: libpisock9
Version: 0.12.2-4
Section: libs
Priority: optional
Architecture: amd64
Depends: libbluetooth2 (>= 3.0), libc6 (>= 2.3.5-1), libusb-0.1-4 (>=
2:0.1.12)
Package: libpisock-dev
Version: 0.12.2-4
Section: libdevel
Priority: extra
Architecture: amd64
Depends: libpisock9 (= 0.12.2-4), libpisync0 (= 0.12.2-4),
libncurses-dev | libncurses5-dev, libusb-dev, libbluetooth2-dev
Note that libbluetooth is a dependency of libpisock9 ONLY in the manual
build - the buildd / chroot version fails to enable bluez.
That will probably allow other packages to build, but the user is
probably expecting bluetooth to work if it is a dependency - as it
stands, it looks like bluetooth will only work on architectures that
are built manually - i.e. the architecture uploaded by the maintainer.
dpkg-buildpackage works, pbuilder does not.
:-(
The dependency gets added to libpisock-dev but libpisock9 does not
appear to include support for bluetooth - no symbols are imported.
I see the same thing in the pool: the i386 libpisock9 binary depends on
libbluetooth2, the amd64 version does not!
Compare:
$ deb-gview
http://ftp.uk.debian.org/debian/pool/main/p/pilot-link/libpisock9_0.12.2-4_i386.deb
Depends: libbluetooth2 (>= 3.0), libc6 (>= 2.3.6-6), libusb-0.1-4 (>= 2:0.1.12)
$ deb-gview
http://ftp.uk.debian.org/debian/pool/main/p/pilot-link/libpisock9_0.12.2-4_amd64.deb
Depends: libc6 (>= 2.3.5-1), libusb-0.1-4 (>= 2:0.1.12)
The Debian package page shows the same:
http://packages.debian.org/unstable/libs/libpisock9
# [dep] libbluetooth2 (>= 3.0) [i386]
Versions: 0.12.2-4 [alpha, amd64, arm, hppa, i386, ia64, m68k, mips,
mipsel, powerpc, s390, sparc]
The only solution I can see, personally, is for i386 to also drop
libbluetooth2 support until the package can be fixed to support bluez
when built on a buildd.
--
Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/
pgpMNNDENAGsf.pgp
Description: PGP signature
