From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] error on bluez-utils compile(fc4)
Date: Sun, 19 Jun 2005 23:48:29 +0200 [thread overview]
Message-ID: <1119217709.8954.6.camel@pegasus> (raw)
In-Reply-To: <20050619213712.56900.qmail@web50708.mail.yahoo.com>
Hi John,
> thanks, is it ok to leave the other parts of bluez as
> released versions?
that won't work. Autoconf must detect the supported D-Bus functions.
Regards
Marcel
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-06-19 21:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-12 8:57 [Bluez-users] can't receive files from phone Graham White
2005-06-12 12:56 ` Fredy P
2005-06-13 2:50 ` [Bluez-users] python error on bluepin John H.
2005-06-13 6:41 ` Fredy P
2005-06-13 19:54 ` John H.
2005-06-13 20:10 ` Marco Trudel
2005-06-13 20:15 ` John H.
2005-06-13 20:26 ` Marco Trudel
2005-06-16 7:50 ` Fredy P
2005-06-17 2:58 ` [Bluez-users] upgrade to fc4 kills bluez-utils John H.
2005-06-19 21:30 ` [Bluez-users] error on bluez-utils compile(fc4) John H.
2005-06-19 21:35 ` Marcel Holtmann
2005-06-19 21:37 ` John H.
2005-06-19 21:48 ` Marcel Holtmann [this message]
2005-06-19 21:49 ` John H.
2005-06-19 21:52 ` Marcel Holtmann
2005-06-21 8:59 ` John H.
2005-06-21 10:58 ` 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=1119217709.8954.6.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox