From: Bastien Nocera <hadess@hadess.net>
To: bluez-devel@lists.sourceforge.net
Cc: sirgraham@endorasoft.es
Subject: Re: [Bluez-devel] Problems to compilate a code in Red Hat 9
Date: Fri, 30 Sep 2005 09:40:46 +0100 [thread overview]
Message-ID: <1128069646.32222.104.camel@bnocera.surrey.redhat.com> (raw)
In-Reply-To: <006c01c5c599$b7446c30$0300a8c0@akira>
On Fri, 2005-09-30 at 10:34 +0200, Sir Graham wrote:
> Hi,
>=20
> =C2=BF=C2=BF=C2=BF=C2=BF yes ????
>=20
> I don=C2=B4t see any of this. I have the Red hat 9 and I think this pac=
kage not=20
> included.
>=20
> Sorry, I don=C2=B4t works with linux and don=C2=B4t have much experienc=
e....
>=20
> How I know if this package are in my distribution?
Don't use Red Hat Linux 9, it's ancient. Fedora Core 4 (ie. 4 versions
afterwards) is available for download and from a number of magazines
with CDs.
---
Bastien Nocera <hadess@hadess.net>=20
Lucas has made a vacuous, boring, pretentious, retroactively destructive
sequel. He has lost the plot. The man is a fool. -- Simon Pegg (on the
Phantom Menace)
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-09-30 8:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 18:29 [Bluez-devel] Problems to compilate a code in Red Hat 9 Sir Graham
2005-09-30 6:42 ` Marcel Holtmann
2005-09-30 7:00 ` Sir Graham
2005-09-30 7:33 ` Marcel Holtmann
2005-09-30 8:09 ` Sir Graham
2005-09-30 8:15 ` Marcel Holtmann
2005-09-30 8:34 ` Sir Graham
2005-09-30 8:40 ` Bastien Nocera [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=1128069646.32222.104.camel@bnocera.surrey.redhat.com \
--to=hadess@hadess.net \
--cc=bluez-devel@lists.sourceforge.net \
--cc=sirgraham@endorasoft.es \
/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