From: rahul <rahul.tank@celunite.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] problem in browsing services through dbus interface.
Date: Mon, 15 Oct 2007 20:05:04 +0530 [thread overview]
Message-ID: <47137A98.9060204@celunite.com> (raw)
In-Reply-To: <4712F226.5040506@celunite.com>
rahul wrote:
> rohit puri wrote:
>
>> hi all,
>>
>> I am browsing the services using the dbus interface.but my code gives
>> the following error
>> `get_remote_service_channel':
>> /root/marcel/main.c:78: undefined reference to `sdp_extract_pdu'
>> /root/marcel/main.c:81: undefined reference to `sdp_get_access_protos'
>> /root/marcel/main.c:85: undefined reference to `sdp_get_proto_port'
>> /root/marcel/main.c:88: undefined reference to `sdp_list_free'
>> /root/marcel/main.c:89: undefined reference to `sdp_list_free'
>> /root/marcel/main.c:92: undefined reference to `sdp_record_free'
>> collect2: ld returned 1 exit status
>> Does someone know how to rectify this problem.
>>
>> Thanks in advance
>>
>>
> Have you compiled the sources on your own? . If yes, then i think you
> have linked the bluez-utils to the correct bluez-libs.
>
Oops .. it shuld have been .."you have *not* linked ..." .
>
>
> thanks,
> rahul
>
-------------------------------------------------------------------------
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/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-10-15 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-12 14:13 [Bluez-users] problem in browsing services through dbus interface rohit puri
2007-10-15 4:52 ` rahul
2007-10-15 14:35 ` rahul [this message]
2007-10-16 4:50 ` rohit puri
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=47137A98.9060204@celunite.com \
--to=rahul.tank@celunite.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.