public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christoph Torens" <c.torens@web.de>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] missing libsdp
Date: Mon, 13 Sep 2004 01:35:40 +0200	[thread overview]
Message-ID: <opsd8mhqi6eocfdv@debian> (raw)

Hello,

I just compiled bluez-libs-2.10 and bluez-utils-2.10
everything went fine, but starting hcitool I get this message:

hcitool: error while loading shared libraries: libsdp.so.2: cannot open  
shared object file: No such file or directory

I cross compiled it, so that _might_ be a source of error.
To be exact I did for bluez-libs:
./configure --host=arm-linux

and for bluez-utils I did:
./configure --host=arm-linux  
--with-bluez=/home/sordid/downloads/bluez-libs-2.10_installDESTDIR/usr/  
--with-usb=/opt/arcom/arm-linux/src/linux-source-2.4.21-rmk1-pxa1-arcom1/drivers/usb/  
--enable-debug --enable-test --enable-initscripts

I thought the USB command is ment for cross-compiling,
so I gave the sources for arm-linux USB as the path.
Thats right?

Whats my failure?

-- 
Regards,
Christoph


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2004-09-12 23:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-12 23:35 Christoph Torens [this message]
2004-09-13 10:38 ` [Bluez-users] missing libsdp 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=opsd8mhqi6eocfdv@debian \
    --to=c.torens@web.de \
    --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