Problems (#1) - bluez version problem? (#84) - Message List

bluez version problem?
 unsolved

Looks like a nice package you've put together. I'm moving over to this one from another wiimote library whose support died out a year ago.

I've been running ./configure and get a repeated error of "configure: error: bluetooth headers not found". When I look through the output, I find that bluetooth.h was found and accepted, however, l2cap.h was not. The autoconf is apparently looking in the correct directory, so is this a version issue?

  • Message #24363

    Not that I know of - I would sooner expect an incomplete package. What distro and bluez package/version are you running? Is l2cap.h actually there?

    • Message #24365

      I'm running BlueZ 3.27 on Mandriva 2005 limited. The l2cap.h file is present in the directory that config is searching. Here's the last few lines of output from running ./config:

      ...

      checking for bluetooth/bluetooth.h usability... yes

      checking for bluetooth/bluetooth.h presence... yes

      checking for bluetooth/bluetooth.h... yes

      checking for bluetooth/l2cap.h... no

      configure: error: bluetooth headers not found

      I also tried this using the --prefix=/usr option thinking it was the library search path issue mentioned in the README, but still no go.

      • Message #24366

        Just to confirm, what's the output of

        file /usr/include/bluetooth/l2cap.h
        
        • Message #24367

          Sorry, accidental refresh here.

        • Message #24368

          /usr/include/bluetooth/l2cap.h: ASCII C program text

          • Message #24370

            I've got nothing...it's in the same directory as bluetooth.h, so it doesn't sound like a path issue. Maybe an autoconf problem? Are you running from a tarball distribution, or subversion sources? If the latter, what version of autoconf are you running?

            • Message #24371

              Greetings. I just stumbled on this thread. I'm having the exact same problem! I downloaded the zipped distribution. I'm looking at 'configure' to see if I can figure something out, but nothing so far.

            • Message #24372

              Looking in my config.log, Looks like a confidence test is failing.

              configure:4197: gcc -c -g -O2 conftest.c >&5 In file included from conftest.c:26: /usr/include/bluetooth/l2cap.h:46: error: syntax error before "sa_family_t" /usr/include/bluetooth/l2cap.h:49: error: syntax error before '}' token

              not sure what the error is, or why configure doesn't flag the actual error. I'll keep digging.

            • Message #24373

              Okay, some valuable information, I think... I found a reference copy of l2cap.h online @

               https://stage.maemo.org/svn/maemo/projects/connectivity/bluez-libs/tags/bluez-libs-3.28-0osso1/include/l2cap.h

              my l2cap.h file was missing #include <sys/socket.h> near the top. There may be other differences as well. Now, I'm passing that test and failing on hci.h. Seems to be the same problem... sa_family_t is not defined.

              I'll try to find a reference copy of that tomorrow.

              Hope this helps!

              • Message #24374

                Definitely - thanks for your help. Keep us posted.

                • Message #24375

                  So far 3 of my .h files seem to be out of date.

                  l2cap.h, hci.h, uinput.h (which is causing the make to fail because uinput_ff_upload isn't defined)

                  Is this an indication that I need to update some package, like my bluetooth? I'm a Linux newbie, so I don't know much about these things.

                  Thanks!

                • Message #24376

                  So far 3 of my .h files seem to be out of date.

                  l2cap.h, hci.h, uinput.h (which is causing the make to fail because uinput_ff_upload isn't defined)

                  Is this an indication that I need to update some package, like my bluetooth? I'm a Linux newbie, so I don't know much about these things.

                  Thanks!

Attachments

No attachments created.