To me, it looks like this could be specific to i386 - I get no problems with building pilot-qof on amd64 or powerpc and these have no bluetooth dependencies. I've just updated my pbuilder chroot and rebuilt pilot-qof on amd64 using libpisock-dev 0.12.2-4 without any errors and without bluetooth.
(pilot-qof, like gnome-pilot, depends on libpisock-dev but not bluez.) The amd64 buildd log for pilot-link shows: BlueZ support........... : no Building pilot-link on my own amd64 system (without a chroot) gives: BlueZ support........... : yes Inside a chroot: BlueZ support........... : no 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. bluetooth.c: In function 'pi_bluetooth_register_hotsync_sdp': bluetooth.c:328: error: 'struct pi_bluetooth_data' has no member named 'handle' bluetooth.c:328: error: 'struct pi_bluetooth_data' has no member named 'sess' bluetooth.c:330: error: 'struct pi_bluetooth_data' has no member named 'handle' bluetooth.c:331: error: 'struct pi_bluetooth_data' has no member named 'sess' bluetooth.c: In function 'pi_bluetooth_unregister_hotsync_sdp': bluetooth.c:349: error: 'struct pi_bluetooth_data' has no member named 'handle' bluetooth.c:350: error: 'struct pi_bluetooth_data' has no member named 'handle' bluetooth.c:350: error: 'struct pi_bluetooth_data' has no member named 'sess' make[3]: *** [libpisock_la-bluetooth.lo] Error 1 make[3]: Leaving directory `/opt/debian/src/rc/pilot-link/pilot-link-0.12.2/libpisock' :-( That's an upstream bug in ./configure.ac - I'll try to take a look. (I've worked with upstream pilot-link directly in the past and things like this are why SCons was being considered for building pilot-link.) Ludovic - was the i386 0.12.2-4 package uploaded built in a chroot or am I completely off-beam here? (I've just built gnome-pilot successfully on amd64 using pbuilder.) AFAICT, the current situation is that pilot-link on i386 depends on bluez when the other Debian architectures do not. Is an i386 binary upload worth trying? Or is the intention that pilot-link in Debian should henceforth bring in bluetooth for all packages using libpisock9? -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
pgp0kNQ7NBREQ.pgp
Description: PGP signature
