From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] help compilling bluez-utils 3.9
Date: Mon, 19 Mar 2007 16:07:48 +0100 [thread overview]
Message-ID: <1174316868.3690.11.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <op.tpce1vcu80yvcu@zaska>
Hi Vladimir,
> I have some problems compilling bluez-utils 3.9 (latest official)
> The configure script does not get me an error, so my next step is "make"\
> Here is the error:
>
>
> make[2]: Entering directory `/home/vladimir/programs/bluez-utils-3.9/hcid'
> make all-am
> make[3]: Entering directory `/home/vladimir/programs/bluez-utils-3.9/hcid'
> /bin/sh ../libtool --tag=CC --mode=link gcc -I/usr/include/dbus-1.0
> -I/usr/lib/dbus-1.0/include -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 -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 -lbluetooth /usr/lib/libexpat.so
> libhciserver.a(dbus-common.o): In function `unregister_sdp_record':
> dbus-common.c:(.text+0x90): undefined reference to
> `sdp_device_record_unregister_binary'
> libhciserver.a(dbus-common.o): In function `register_sdp_binary':
> dbus-common.c:(.text+0x106): undefined reference to
> `sdp_device_record_register_binary'
> collect2: ld returned 1 exit status
> make[3]: *** [hcid] Error 1
> make[3]: Leaving directory `/home/vladimir/programs/bluez-utils-3.9/hcid'
> make[2]: *** [all] Error 2
> make[2]: Leaving directory `/home/vladimir/programs/bluez-utils-3.9/hcid'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/vladimir/programs/bluez-utils-3.9'
> make: *** [all] Error 2
you also have to install bluez-libs-3.9 first.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-03-19 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-17 17:04 [Bluez-users] help compilling bluez-utils 3.9 Vladimir Vasilev
2007-03-19 15:07 ` Marcel Holtmann [this message]
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=1174316868.3690.11.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--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