From: "L. C. Robinson" <lcr@onewest.net>
To: <blinux-list@redhat.com>
Subject: Re: missing ao.h
Date: Fri, 16 Nov 2001 13:57:59 -0700 (MST) [thread overview]
Message-ID: <Pine.LNX.4.33.0111161356260.7615-100000@rupin.localnet> (raw)
In-Reply-To: <3.0.6.32.20011116141821.007d17d0@mail.doorpi.net>
On Fri, 16 Nov 2001, Brent Harding wrote:
> I'm using redhat 7.1, and was trying to compile stuff when a configure
> script complained about not getting ao.h. What package is this file in, so
> I can replace it?
On a redhat 6.2 system, it is from the libao-devel package.
--
L. C. Robinson
reply to no_spam+munged_lcr@onewest.net.invalid
People buy MicroShaft for compatibility, but get incompatibility and
instability instead. This is award winning "innovation". Find
out how MS holds your data hostage with "The *Lens*"; see
"CyberSnare" at http://www.netaction.org/msoft/cybersnare.html
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
Brent Harding
` L. C. Robinson [this message]
` Brent Harding
` Georgina
` Brent Harding
` Georgina
` Georgina
` Brent Harding
` getting speakup wasRe: " Kenny Hitt
` Brent Harding
` Kenny Hitt
` Henry Yen
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=Pine.LNX.4.33.0111161356260.7615-100000@rupin.localnet \
--to=lcr@onewest.net \
--cc=blinux-list@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).