From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] libs upgrading
Date: Thu, 09 Dec 2004 17:45:26 +0100 [thread overview]
Message-ID: <1102610726.9988.235.camel@pegasus> (raw)
In-Reply-To: <cp9uj3$es1$1@sea.gmane.org>
Hi,
> I've installed bluez-libs-2.12 and bluez-utils-2.12 on a kernel version
> 2.6.9 (bluez support) (fedora core3 distribution). I have seen that the
> installation has placed .h files at /usr/include/bluetooth, but the
> previous installation (fedora's default) had placed the tools, and
> libraries all arround. So now I guess I have different versions of -for
> example- bluetooth.h file, and maybe problems?
I never heard of any weird installations of the Bluetooth library and
Fedora Core 3 should be clean, because their version should be 2.10 or
so.
> So, do I have to uninstall before upgrading ?
Maybe that is a good idea. Or you try to find an already built RPM for
bluez-{libs|utils}-2.12.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-12-09 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 16:29 [Bluez-devel] libs upgrading soraberri
2004-12-09 16:45 ` 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=1102610726.9988.235.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@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