public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ricky Soh" <rickysoh@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] newbie questions on Bluez installation
Date: Sat, 1 Sep 2007 16:00:52 +0800	[thread overview]
Message-ID: <db972f430709010100m3ac8eea6v12836b4697955133@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1912 bytes --]

Hi,

I have downloaded and compiled bluez-lib-3.16 using

./configure
make
make install.

Everything went smoothly for the installation.

I did the same for bluez-util-3.16.

The error is at the "make"

How do i make sure i am compiling against the latest lib?

Sorry for asking such a newbie question. Would appreciate your help. Thanks.

Sincerely
Ricky

>Message: 3
>Date: Fri, 31 Aug 2007 16:06:38 +0200
>From: Marcel Holtmann <marcel@holtmann.org>
>Subject: Re: [Bluez-users] newbie questions on Bluez installation
>To: BlueZ users <bluez-users@lists.sourceforge.net>
>Message-ID: <1188569198.13373.92.camel>@violet>
>Content-Type: text/plain

>Hi Ricky,

> I have just downloaded bluez-lib and bluez-utils-3.16 and ported to
> FC6 linux 2.6.18-1.2798.
>
> After i did the ./configure, i did the usual "make" for both. This is
> the error for blue-utils-3.16 :
>
> Entering the directory '/root/bluez-utils-3.16/hci'
> /bin/sh ../libtool --tag=CC   --mode=link gcc -I/usr/include/dbus-1.0
> -I/usr/lib/dbus-1.0/include   -DDBUS_API_SUBJECT_TO_CHANGE -I../eglib
> -Wall -O2 -D_FORTIFY_SOURCE=2   -o hcid main.o
> libhciserver.a ../sdpd/libsdpserver.a ../common/libhelper.a
../eglib/libeglib.la -L/lib -ldbus-1   -lbluetooth   -lexpat
> gcc -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include
> -DDBUS_API_SUBJECT_TO_CHANGE -I../eglib -Wall -O2 -D_FORTIFY_SOURCE=2
> -o hcid main.o
> libhciserver.a ../sdpd/libsdpserver.a ../common/libhelper.a
../eglib/.libs/libeglib.a -L/lib -ldbus-1 /usr/lib/libbluetooth.so
/usr/lib/libexpat.so
> libhciserver.a(device.o): In function `start_adapter':
> device.c:(.text+0x10c1): undefined reference to
> `hci_read_simple_pairing_mode'
> libhciserver.a(dbus-common.o): In function `unregister_sdp_record':
> dbus-common.c:(.text+0x90): undefined reference to
> `sdp_device_record_unregister_binary'

>you are not compiling against the latest bluez-libs.

>Regards

>Marcel

[-- Attachment #1.2: Type: text/html, Size: 2519 bytes --]

[-- Attachment #2: Type: text/plain, Size: 315 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2007-09-01  8:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-01  8:00 Ricky Soh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-08-31  6:56 [Bluez-users] newbie questions on Bluez installation Ricky Soh
2007-08-31 14:06 ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=db972f430709010100m3ac8eea6v12836b4697955133@mail.gmail.com \
    --to=rickysoh@gmail.com \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox