From: Brent Harding <bharding@doorpi.net>
To: blinux-list@redhat.com
Subject: Re: missing ao.h
Date: Fri, 16 Nov 2001 22:47:24 -0600 [thread overview]
Message-ID: <3.0.6.32.20011116224724.00a82100@mail.doorpi.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0111161356260.7615-100000@rupin.localnet>
Oh, got it from vorbis stuff I got from CVS. I figured CVS would be a later
version than rh put on their distro, so I did it, finally getting used to
checking source out of CVS, as long as there's autogen.sh, it works like a
breeze to take current source and make an rpm, but speakup isn't so simple,
my kernel source is already patched with some speakup version, want to
update to 1.0 though.
At 01:57 PM 11/16/01 -0700, you wrote:
>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
>
>
>
>_______________________________________________
>Blinux-list mailing list
>Blinux-list@redhat.com
>https://listman.redhat.com/mailman/listinfo/blinux-list
>
>
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
` Brent Harding [this message]
` 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=3.0.6.32.20011116224724.00a82100@mail.doorpi.net \
--to=bharding@doorpi.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).