Problems Building Latest Bluez-utils

[kkazakov13]

I built bluez-libs , dbus-1.0.2 , but i'm failing on bluez-utils with the following errors:

Code: [Select]

make[3]: Entering directory `/storage/build/bluetooth/bluez-utils-3.8/hcid'
if gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../common   -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include   -Wall -O2 -D_FORTIFY_SOURCE=2 -MT security.o -MD -MP -MF ".deps/security.Tpo" -c -o security.o security.c; \
then mv -f ".deps/security.Tpo" ".deps/security.Po"; else rm -f ".deps/security.Tpo"; exit 1; fi
security.c: In function `return_link_keys':
security.c:302: error: `evt_return_link_keys' undeclared (first use in this function)
security.c:302: error: (Each undeclared identifier is reported only once
security.c:302: error: for each function it appears in.)
security.c:302: error: `evt' undeclared (first use in this function)
security.c: In function `inquiry_result_with_rssi':
security.c:534: error: `INQUIRY_INFO_WITH_RSSI_AND_PSCAN_MODE_SIZE' undeclared (first use in this function)
security.c:536: error: `inquiry_info_with_rssi_and_pscan_mode' undeclared (first use in this function)
security.c:537: error: request for member `dev_class' in something not a structure or union
security.c:538: error: request for member `dev_class' in something not a structure or union
security.c:539: error: request for member `dev_class' in something not a structure or union
security.c:541: error: request for member `bdaddr' in something not a structure or union
security.c:542: error: request for member `rssi' in something not a structure or union
security.c:544: error: request for member `bdaddr' in something not a structure or union
security.c:550: error: `inquiry_info_with_rssi' undeclared (first use in this function)
security.c:551: error: request for member `dev_class' in something not a structure or union
security.c:552: error: request for member `dev_class' in something not a structure or union
security.c:553: error: request for member `dev_class' in something not a structure or union
security.c:555: error: request for member `bdaddr' in something not a structure or union
security.c:556: error: request for member `rssi' in something not a structure or union
security.c:558: error: request for member `bdaddr' in something not a structure or union
security.c:560: error: `INQUIRY_INFO_WITH_RSSI_SIZE' undeclared (first use in this function)
security.c: In function `extended_inquiry_result':
security.c:571: error: `extended_inquiry_info' undeclared (first use in this function)
security.c:572: error: request for member `dev_class' in something not a structure or union
security.c:573: error: request for member `dev_class' in something not a structure or union
security.c:574: error: request for member `dev_class' in something not a structure or union
security.c:576: error: request for member `bdaddr' in something not a structure or union
security.c:577: error: request for member `rssi' in something not a structure or union
security.c:577: error: request for member `data' in something not a structure or union
security.c:579: error: request for member `bdaddr' in something not a structure or union
security.c:581: error: `EXTENDED_INQUIRY_INFO_SIZE' undeclared (first use in this function)
security.c: In function `io_security_event':
security.c:745: error: `EVT_INQUIRY_RESULT_WITH_RSSI' undeclared (first use in this function)
security.c:749: error: `EVT_EXTENDED_INQUIRY_RESULT' undeclared (first use in this function)
security.c:773: error: `HCI_SECMGR' undeclared (first use in this function)
security.c:789: error: `EVT_RETURN_LINK_KEYS' undeclared (first use in this function)
security.c: In function `start_security_manager':
security.c:802: error: `read_stored_link_key_cp' undeclared (first use in this function)
security.c:802: error: syntax error before "cp"
security.c:824: error: `EVT_RETURN_LINK_KEYS' undeclared (first use in this function)
security.c:830: error: `EVT_INQUIRY_RESULT_WITH_RSSI' undeclared (first use in this function)
security.c:831: error: `EVT_EXTENDED_INQUIRY_RESULT' undeclared (first use in this function)
security.c:870: error: `cp' undeclared (first use in this function)
security.c:873: error: `OCF_READ_STORED_LINK_KEY' undeclared (first use in this function)
security.c:874: error: `READ_STORED_LINK_KEY_CP_SIZE' undeclared (first use in this function)
make[3]: *** [security.o] Error 1
make[3]: Leaving directory `/storage/build/bluetooth/bluez-utils-3.8/hcid'
make[2]: *** [all] Error 2                                                                        

Anyone can help? I tried searching for these variables, but couldn't find anything so far.


P.P. Solved it, it was finding hci.h from the gcc-headers packages, which is kinda outdated ... continuing to compile , after make distclean ; ./configure again

[kkazakov13]

I've built it ... built latest bluetooth tools for beta3. Had a lot of problems, but finally did it. Will upload it soon

[Meanie]

I've built it ... built latest bluetooth tools for beta3. Had a lot of problems, but finally did it. Will upload it soon
[div align=\"right\"][a href=\"index.php?act=findpost&pid=151818\"][{POST_SNAPBACK}][/a][/div]

apart from being the latest and greatest version of the bluetools tools, what does it actually do or do better than the current version? is there any particular feature that is currently not working or have you found a nagging bug that the new version fixes? just curious ...

[kkazakov13]

Actually, I don't know if there are some great differences.

But the original ones never worked for me. Newest work perfectly. So this is pretty enough for me to use them instead of the original ones.

Of course I don't force anyone to use mine. I'm just giving what I built and use, to all who want it. The choice is yours!

[Meanie]

Actually, I don't know if there are some great differences.

But the original ones never worked for me. Newest work perfectly. So this is pretty enough for me to use them instead of the original ones.

Of course I don't force anyone to use mine. I'm just giving what I built and use, to all who want it. The choice is yours!
[div align=\"right\"][a href=\"index.php?act=findpost&pid=151996\"][{POST_SNAPBACK}][/a][/div]

ah ok. the beta3 bluetooth tools work for me (socket cf bluetooth) so I was just curious what was new/improved in your build. if it got yours working it probably means it supports additional devices which is always good

[kkazakov13]

Yes, mine works so far perfectly. I had to use some files from the original bluez-utils, to get CF bluetooth cards running, but so far I think it's stable. I had no problems or such, and if anyone reports something not quite working, then I'll try to fix it and get it as stable as it can be.

I'm using it since 2 days already, intensively, have no problems yet

The only problem that might occur as I see, is with newest DBus package, which some of the older programs, compiled for dbus 0.2x might not work correctly, or at all.

Of course this can be solved by recompiling these programs

My current beta3 setup is so heavily customized that it has almost nothing to do with the default one. I have a shell script which stores exactly what I want in a file, and then have shell script which restores all my settings , reinstalls exactly the packages I want, so I can easily test some packages on plain beta3, and then go back with all my stuff installed in about 20 minutes.