Linux bluetooth development
 help / color / mirror / Atom feed
From: Sumeet VERMA <sumeet.verma@st.com>
To: <bluez-users@lists.sf.net>
Subject: Re: [Bluez-users] hcidump-1.34 startup problem
Date: Mon, 9 Apr 2007 16:56:09 +0530	[thread overview]
Message-ID: <008d01c77a99$df6baff0$8935c70a@dlh.st.com> (raw)

 Hi 
I found the solution to this problem . hcidump was taking the libraries from /lib/libbluet....
My library was installed in /usr/local/lib. I copied the libbluetooth library to /lib and it worked.

Regards,
Sumeet 
-----Original Message-----
From: sumeet verma [mailto:sumeet.verma@st.com] 
Sent: Monday, April 02, 2007 5:00 PM
To: bluez-users@lists.sf.net
Subject: hcidump-1.34 startup problem

Hi
I am using bluez-hcidump-1.34.
Its installed properly but when I try to run it , it gives and error

[root@dlhl0330 3.9]# hcidump -X -V
hcidump: error while loading shared libraries: libbluetooth.so.2: cannot open shared object file. No such file or directory [root@dlhl0330 3.9]#

libluetooth.so.2->libbluetooth.so.2.5.0 in /usr/local/lib

Regards,

Sumeet 


-------------------------------------------------------------------------
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

             reply	other threads:[~2007-04-09 11:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-09 11:26 Sumeet VERMA [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-04-02 11:30 [Bluez-users] hcidump-1.34 startup problem Sumeet VERMA

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='008d01c77a99$df6baff0$8935c70a@dlh.st.com' \
    --to=sumeet.verma@st.com \
    --cc=bluez-users@lists.sf.net \
    --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