ports/88660: comms/gammu (1.02.0) looks for bluetooth.h in /usr/include/bluetooth/
Thiemo Nordenholz
nz at thiemo.net
Tue Nov 8 12:30:19 UTC 2005
>Number: 88660
>Category: ports
>Synopsis: comms/gammu (1.02.0) looks for bluetooth.h in /usr/include/bluetooth/
>Confidential: no
>Severity: serious
>Priority: low
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Tue Nov 08 12:30:18 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator: Thiemo Nordenholz
>Release: 6.0-STABLE
>Organization:
>Environment:
FreeBSD feynman.ham01.thiemo.net 6.0-STABLE FreeBSD 6.0-STABLE #0: Wed Nov 2 23:34:19 CET 2005 thiemo at feynman.ham01.thiemo.net:/usr/src/sys/i386/compile/FEYNMAN i386
>Description:
The autoconf/configure mechanism seems to lead to a configure script searching for an include file "bluetooth.h" in /usr/include/bluetooth/, but the respective file needed is in /usr/include/ directly.
Therefore, configure disables any bluetooth support for gammu:
=====snip=====
checking for bluez... no
checking bluetooth/bluetooth.h usability... no
checking bluetooth/bluetooth.h presence... no
checking for bluetooth/bluetooth.h... no
configure: creating ./config.status
[ ... ]
Phone protocols with Bluetooth stack
------------------------------------------
AT commands - no
Nokia FBUS2 - no
Nokia PHONET FBUS - no
OBEX - no
=====snap=====
This leads, when a bluetooth device is configured, to an error message:
"Some functions not available for your OS (disabled in config or not written)."
>How-To-Repeat:
Build gammu from portversion 1.02.0.
Create a ~/.gammurc, setting a connection type using bluetooth, e.g. "bluerfphonet"
Start "gammu --identify"
>Fix:
As a _workaround_, I have added a symling from /usr/include/bluetooth/bluetooth.h to /usr/include/bluetooth.h as I do not know autoconf -- this is surely no fix for the port, though.
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list