All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Re: bluez-utils-2.14 compile error: make returns "cannot find -lbluetooth"
Date: Wed, 19 Jan 2005 21:39:34 +0100	[thread overview]
Message-ID: <1106167174.8190.135.camel@pegasus> (raw)
In-Reply-To: <8272108050119101561d8eb9b@mail.gmail.com>

Hi,

> Added /usr/local/bluez/lib (even tried /usr/local/bluez), ran ldconfig as root.
> ldconfig -p | grep bluetooth
>         libbluetooth.so.1 (libc6) => /usr/local/bluez/lib/libbluetooth.so.1
>         libbluetooth.so (libc6) => /usr/local/bluez/lib/libbluetooth.so
> Same thing gets spat out during make. :((
> bluez-libs...I had that installed first...at least that's what I
> presume I did. :)
> I've even turned religous - started praying, that is. :P

if you use a different prefix than /usr you might to tell the utils
about it. Look at --with-bluez=... for example.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2005-01-19 20:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-19 10:49 [Bluez-users] bluez-utils-2.14 compile error: make returns "cannot find -lbluetooth" tcalexander
2005-01-19 12:01 ` Marcel Holtmann
2005-01-19 12:55 ` [Bluez-users] " Sebastian Roth
2005-01-19 18:15   ` tcalexander
2005-01-19 20:39     ` 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=1106167174.8190.135.camel@pegasus \
    --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 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.