LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices



Reply
 
Search this Thread
Old 03-31-2009, 01:41 PM   #1
mkisow
LQ Newbie
 
Registered: May 2008
Posts: 28

Rep: Reputation: 15
Bluez 4.34 Compile Error


...
make[1]: Entering directory `/usr/src/bluez-4.34/audio'
make check-am
make[2]: Entering directory `/usr/src/bluez-4.34/audio'
gcc -DHAVE_CONFIG_H -I. -I.. -I../common -I../src -fvisibility=hidden -I../sbc -I../include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I../gdbus -Wall -O2 -D_FORTIFY_SOURCE=2 -D_FORTIFY_SOURCE=2 -fPIC -MT ipctest.o -MD -MP -MF .deps/ipctest.Tpo -c -o ipctest.o ipctest.c
ipctest.c: In function ‘main’:
ipctest.c:1084: warning: implicit declaration of function ‘signal’
ipctest.c:1084: error: ‘SIGTERM’ undeclared (first use in this function)
ipctest.c:1084: error: (Each undeclared identifier is reported only once
ipctest.c:1084: error: for each function it appears in.)
ipctest.c:1085: error: ‘SIGINT’ undeclared (first use in this function)
make[2]: *** [ipctest.o] Error 1
make[2]: Leaving directory `/usr/src/bluez-4.34/audio'
make[1]: *** [check] Error 2
make[1]: Leaving directory `/usr/src/bluez-4.34/audio'
make: *** [check-recursive] Error 1


Please let me know if you wnt all ./configure and make output.
 
Old 04-01-2009, 08:09 AM   #2
knudfl
LQ 5k Club
 
Registered: Jan 2008
Location: Copenhagen, DK
Distribution: pclos2014.08, Slack14.1 DebWheezy, +50+ other Linux OS, for test only.
Posts: 14,272

Rep: Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663
Debian Lenny :
# apt-get install bluez-utils
provides version 3.36 , will that do ?

You can see the other 'blues' packages here
http://packages.debian.org/lenny/bluez-utils
.....
 
Old 04-01-2009, 09:57 AM   #3
mkisow
LQ Newbie
 
Registered: May 2008
Posts: 28

Original Poster
Rep: Reputation: 15
Unfortunately...

That is the version I have installed (from the repositories...) I want the latest and greatest to overcome a problem with my Broadcomm BT adapter that comes up with errors and doesn't recognize my mouse as an HID device causing me to hciconfig hci0 reset and hidd --connect 00:01:76:07:68:1C
 
Old 04-01-2009, 02:20 PM   #4
knudfl
LQ 5k Club
 
Registered: Jan 2008
Location: Copenhagen, DK
Distribution: pclos2014.08, Slack14.1 DebWheezy, +50+ other Linux OS, for test only.
Posts: 14,272

Rep: Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663
Bluez-4.33 is without the file 'audio/ipctest.c'

and will compile with no errors on Debian Lenny.

bluez-4.33.tar.bz2
http://www.kernel.org/pub/linux/bluetooth/

I hope, you can use that.
.....
P.S.: version 4.34 is 3 days old, 4.33 two weeks.
.....

Last edited by knudfl; 04-01-2009 at 02:32 PM.
 
Old 04-02-2009, 08:05 AM   #5
mkisow
LQ Newbie
 
Registered: May 2008
Posts: 28

Original Poster
Rep: Reputation: 15
I will try that...

I will try that and report back, I had thought about that as well just haven't done anything yet.
 
Old 04-08-2009, 11:17 AM   #6
mkisow
LQ Newbie
 
Registered: May 2008
Posts: 28

Original Poster
Rep: Reputation: 15
Nothing...

Meaning 4.33 didn't work either.
 
Old 04-08-2009, 11:58 AM   #7
scotttwilson
LQ Newbie
 
Registered: Jan 2009
Posts: 3

Rep: Reputation: 0
4.33 compiles with bluez-libs-devel package addition

I have had the same problem and solved it in the last week by compiling 4.33 successfully. I believe that you are missing the library:

bluez-libs-devel

I am working on Fedora 10, and got it by using yum (as root):

yum install bluez-libs-devel.

After that, Bluez 4.33 compiles fine, but there is still a problem with Broadcomm dongles that others are working on at this moment...

It could be that the problem with compiling 4.34 was because I was missing this package, but I haven't gotten around to trying 4.34 again yet.
 
Old 04-08-2009, 01:35 PM   #8
mkisow
LQ Newbie
 
Registered: May 2008
Posts: 28

Original Poster
Rep: Reputation: 15
I just tried that it failed miserably...
Thoughts?
 
Old 04-09-2009, 10:47 AM   #9
scotttwilson
LQ Newbie
 
Registered: Jan 2009
Posts: 3

Rep: Reputation: 0
You say that you got that error even **after** going back to 4.33??

Just trying to cover all bases, but are you keeping things completely separate between 4.33 and 4.34 if you did revert back to 4.33??

S
 
Old 04-09-2009, 02:18 PM   #10
scotttwilson
LQ Newbie
 
Registered: Jan 2009
Posts: 3

Rep: Reputation: 0
Possibly something else to try

I thought of something else you may want to do. Try to compile on a "clean" machine. I was able to do this using FC-10 on a usb stick. To set this up you need to have a computer that will boot off of a usb stick (look in your bios for this - but newer computers should support this).

Get liveusb-creator from the net, download FC-10 via liveusb and install it on the usb stick (in liveusb, make sure you leave a decent amount of persistent storage on the usb stick).

Once you can boot into Fedora, go to a terminal window and (as root) do the following:

yum install gcc
yum install make
yum install dbus-glib-devel
yum install gettext
yum install bluez-libs-devel

Then try compiling after that. I was able to do that twice using version 4.33 and create a bluetoothd daemon and install it. It works for me. All in all, this should take you 2-4 hours from start to finish - really!
 
Old 04-11-2009, 07:54 AM   #11
knudfl
LQ 5k Club
 
Registered: Jan 2008
Location: Copenhagen, DK
Distribution: pclos2014.08, Slack14.1 DebWheezy, +50+ other Linux OS, for test only.
Posts: 14,272

Rep: Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663
Bluez 4.34, Debian Lenny.
With todays bug fix it can now be compiled with no errors.

http://git.kernel.org/?p=bluetooth/bluez.git;a=summary
> > please click 'snapshot' in "line 1" and get
bluez.git-a32df6e52f95134d51592404162a1bf99571110f.tar.gz

cd bluetooth/bluez.git
./bootstrap
./bootstrap-configure
If you get a 'missing gtk-doc', it can be ignored.
./configure .. make
......
 
Old 04-11-2009, 01:56 PM   #12
joto
LQ Newbie
 
Registered: Apr 2009
Location: Georgia, Tbilisi
Distribution: Debian Lenny
Posts: 2

Rep: Reputation: 0
hello everyone! It's my firs post on this forum.
 
Old 04-13-2009, 02:56 PM   #13
mkisow
LQ Newbie
 
Registered: May 2008
Posts: 28

Original Poster
Rep: Reputation: 15
It finally compiled, Thank You!
Question though, this is for installation... Should I uninstall all of my Debian bluetooth packages prior to installing this?
 
Old 04-14-2009, 01:12 AM   #14
knudfl
LQ 5k Club
 
Registered: Jan 2008
Location: Copenhagen, DK
Distribution: pclos2014.08, Slack14.1 DebWheezy, +50+ other Linux OS, for test only.
Posts: 14,272

Rep: Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663Reputation: 2663
Quote:
Should I uninstall all of my Debian bluetooth packages ......
Probably yes.
 
Old 04-14-2009, 10:43 AM   #15
mkisow
LQ Newbie
 
Registered: May 2008
Posts: 28

Original Poster
Rep: Reputation: 15
Okay, I un-installed all the Debian bluetooth packages, ran "make install" for bluez-4.35 and the firmware -> SUCCESS!
I then did the following...

# hciconfig -a
hci0: Type: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:0 acl:0 sco:0 commands:0 errors:0

# hciconfig hci0 up
# hciconfig -a

hci0: Type: USB
BD Address: 00:1B:FB:8A:79:88 ACL MTU: 1021:6 SCO MTU: 64:1
UP RUNNING
RX bytes:89 acl:0 sco:0 events:10 errors:0
TX bytes:35 acl:0 sco:0 commands:10 errors:0
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x83
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy:
Link mode: SLAVE ACCEPT
Can't read local name on hci0: Input/output error (5) <--- DAMMIT! The whole reason I wanted to reinstall bluetooth was to "hopefully" resolve this situation...

# hciconfig hci0 reset
# hciconfig -a

hci0: Type: USB
BD Address: 00:1B:FB:8A:79:88 ACL MTU: 1021:6 SCO MTU: 64:1
UP RUNNING <<-- ISCAN and PSCAN are not running... as per hcid.conf
RX bytes:443 acl:0 sco:0 events:22 errors:0
TX bytes:76 acl:0 sco:0 commands:22 errors:0
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x83
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy:
Link mode: SLAVE ACCEPT
Name: 'BCM92046 Bluetooth Device'
Class: 0x000000 <<-- CLASS is not correct per hcid.conf
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Ver: 2.1 (0x4) HCI Rev: 0x38 LMP Ver: 2.1 (0x4) LMP Subver: 0x213d
Manufacturer: Broadcom Corporation (15)

I have a sony vaio with an integrated bluetooth and wireless I read somewhere that this is an issue meaning Can't read local name on hci0: Input/output error (5) with these cards... Is that true? Can it be fixed? Am I missing something here?

# cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

firewire-sbp2
loop
hidp
rfcomm
bcm203x
hci_vhci

# dmesg | grep Bluetooth
[ 7.562824] usb 5-6.2.1: Product: BCM2046 Bluetooth Device
[ 7.785930] Bluetooth: Core ver 2.11
[ 7.875645] Bluetooth: HCI device and connection manager initialized
[ 7.882473] Bluetooth: HCI socket layer initialized
[ 7.905445] Bluetooth: HCI USB driver ver 2.9
[ 13.824720] Bluetooth: L2CAP ver 2.9
[ 13.830447] Bluetooth: L2CAP socket layer initialized
[ 13.848085] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 13.886151] Bluetooth: RFCOMM socket layer initialized
[ 13.892763] Bluetooth: RFCOMM TTY layer initialized
[ 13.901568] Bluetooth: RFCOMM ver 1.8
[ 13.932640] Bluetooth: Broadcom Blutonium firmware driver ver 1.1
[ 13.964622] Bluetooth: Virtual HCI driver ver 1.2

# lsusb
Bus 005 Device 009: ID 044e:3012 Alps Electric Co., Ltd
Bus 005 Device 008: ID 044e:3013 Alps Electric Co., Ltd
Bus 005 Device 006: ID 044e:3011 Alps Electric Co., Ltd
Bus 005 Device 007: ID 044e:3010 Alps Electric Co., Ltd
Bus 005 Device 005: ID 05ca:183a Ricoh Co., Ltd
Bus 005 Device 003: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 005 Device 002: ID 054c:02d5 Sony Corp.
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 147e:2016
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

# lsusb -v -s 005:007

Bus 005 Device 007: ID 044e:3010 Alps Electric Co., Ltd
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize0 64
idVendor 0x044e Alps Electric Co., Ltd
idProduct 0x3010
bcdDevice 0.56
iManufacturer 1 Broadcom Corp
iProduct 2 BCM2046 Bluetooth Device
iSerial 3 001BFB8A7988
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 216
bNumInterfaces 4
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 2
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 3
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 4
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 5
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0020 1x 32 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 3
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 254 Application Specific Interface
bInterfaceSubClass 1 Device Firmware Update
bInterfaceProtocol 1
iInterface 0
** UNRECOGNIZED: 07 21 07 88 13 40 00
Device Status: 0x0001
Self Powered

Last edited by mkisow; 04-14-2009 at 11:49 AM. Reason: More Information
 
  


Reply

Tags
bluetooth, bluez, compile, debian, error


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
bluez-utils cross-compiling error cloudlast Linux - Embedded & Single-board computer 4 05-07-2009 04:37 AM
How to compile/use bluez-4.1?? fmillion Linux - Software 3 08-29-2008 01:36 PM
how to cross-compile bluez-utils? cloudlast Linux - Software 1 04-29-2008 07:24 PM
Compile madwifi, ... compile error , how can i do. ERBRMN Linux - Networking 3 03-08-2006 08:56 PM


All times are GMT -5. The time now is 11:19 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration