linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paulo Wollny <paulo.wollny@ibdcon.org.br>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] problem building btsco.
Date: Fri, 24 Jun 2005 12:03:59 -0300	[thread overview]
Message-ID: <42BC20DF.9030305@ibdcon.org.br> (raw)
In-Reply-To: <1119623544.3896.221.camel@baroque.rococosoft.com>

Hi Steve,

My distribution is suse 9.1 and i upgraded all the bluez packages from 
suse 9.3. Is working... kbluetoothd, kbtobexclient (i can call it), 
kbtobexsrv, multisync.

I found out that kbtobexsrv is no more a standalone program.. but is 
called from kbluetoothd....
When clicking on the kbluetoothd icon, i can see my phone, but trying to 
browse it, i get LMP response timeout.....
Is there any way to browse my phone contents?

Best regards and thx for helping me.

Paulo Wollny

Stephen Crane wrote:
> Hi Paolo,
> What distribution is this? (You can kludge around your problem by
> softlinking libsdp.so.2 to libbluetooth.so but this a hack.)
> 
> Update kbtobexsrv or rebuild it from source.
> 
> Cheers,
> Steve
> 
> On Fri, 2005-06-24 at 11:26 -0300, Paulo Wollny wrote:
> 
>>Hi Steve,
>>
>>i did update of all teh bluez packages, but when trying to run 
>>ktbobexsrv, i get the following message:
>>
>>kbtobexsrv: error while loading shared libraries: libsdp.so.2: cannot 
>>open shared object file
>>
>>Any hint?
>>
>>I was able to build btsco.
>>
>>Best regards,
>>
>>Paulo Wollny
>>
>>
>>Stephen Crane wrote:
>>
>>>Hi Paolo
>>>It looks as if your version of bluez-libs is very old. Recent versions
>>>have the sdp library merged in.
>>>
>>>Cheers,
>>>Steve
>>>
>>>On Fri, 2005-06-24 at 10:20 -0300, Paulo Wollny wrote:
>>>
>>>
>>>>Hi,
>>>>
>>>>i'm trying o build the btsco and am getting the following error. Does 
>>>>anyone knows how to solve it?
>>>>
>>>>Kind regards,
>>>>
>>>>Paulo Wollny
>>>>
>>>>gcc -DHAVE_CONFIG_H -I. -I. -I..     -Wall -O2 -c `test -f 'sbcinfo.c' 
>>>>|| echo './'`sbcinfo.c
>>>>gcc  -Wall -O2   -o sbcinfo  sbcinfo.o  -lasound -lm -ldl -lpthread
>>>>gcc -DHAVE_CONFIG_H -I. -I. -I..     -Wall -O2 -c `test -f 'sbcenc.c' || 
>>>>echo './'`sbcenc.c
>>>>gcc  -Wall -O2   -o sbcenc  sbcenc.o libsbc.a -lasound -lm -ldl -lpthread
>>>>gcc -DHAVE_CONFIG_H -I. -I. -I..     -Wall -O2 -c `test -f 'rcplay.c' || 
>>>>echo './'`rcplay.c
>>>>gcc  -Wall -O2   -o rcplay  rcplay.o -lbluetooth -lasound -lm -ldl -lpthread
>>>>rcplay.o(.text+0xd0): In function `main':
>>>>: undefined reference to `sdp_connect'
>>>>rcplay.o(.text+0xed): In function `main':
>>>>: undefined reference to `sdp_uuid16_create'
>>>>rcplay.o(.text+0xf7): In function `main':
>>>>: undefined reference to `sdp_list_append'
>>>>rcplay.o(.text+0x11b): In function `main':
>>>>: undefined reference to `sdp_list_append'
>>>>rcplay.o(.text+0x12c): In function `main':
>>>>: undefined reference to `sdp_list_append'
>>>>rcplay.o(.text+0x141): In function `main':
>>>>: undefined reference to `sdp_service_search_attr_req'
>>>>rcplay.o(.text+0x14c): In function `main':
>>>>: undefined reference to `sdp_close'
>>>>rcplay.o(.text+0x18f): In function `main':
>>>>: undefined reference to `sdp_get_access_protos'
>>>>rcplay.o(.text+0x1a6): In function `main':
>>>>: undefined reference to `sdp_get_proto_port'
>>>>collect2: ld returned 1 exit status
>>>>make[2]: *** [rcplay] Fehler 1
>>>>make[2]: Leaving directory `/home/paulo/Bluetooth-Linux/btsco-0.4/sbc'
>>>>make[1]: *** [all-recursive] Fehler 1
>>>>make[1]: Leaving directory `/home/paulo/Bluetooth-Linux/btsco-0.4'
>>>>make: *** [all] Fehler 2
>>>>
>>>>
>>>>-------------------------------------------------------
>>>>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>>>
>>>>from IBM. Find simple to follow Roadmaps, straightforward articles,
>>>
>>>>informative Webcasts and more! Get everything you need to get up to
>>>>speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>>>>_______________________________________________
>>>>Bluez-users mailing list
>>>>Bluez-users@lists.sourceforge.net
>>>>https://lists.sourceforge.net/lists/listinfo/bluez-users
>>
>>
>>-------------------------------------------------------
>>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>>from IBM. Find simple to follow Roadmaps, straightforward articles,
>>informative Webcasts and more! Get everything you need to get up to
>>speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>>_______________________________________________
>>Bluez-users mailing list
>>Bluez-users@lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/bluez-users


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-06-24 15:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24 13:20 [Bluez-users] problem building btsco Paulo Wollny
2005-06-24 13:46 ` Stephen Crane
2005-06-24 14:26   ` Paulo Wollny
2005-06-24 14:32     ` Stephen Crane
2005-06-24 15:03       ` Paulo Wollny [this message]
2005-06-24 15:15         ` Paulo Wollny

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=42BC20DF.9030305@ibdcon.org.br \
    --to=paulo.wollny@ibdcon.org.br \
    --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;
as well as URLs for NNTP newsgroup(s).