From: Kenny Hitt <kennyhitt@yahoo.com>
To: blinux-list@redhat.com
Subject: getting speakup wasRe: missing ao.h
Date: Sun, 18 Nov 2001 07:10:48 -0600 [thread overview]
Message-ID: <20011118071048.A1184@learning> (raw)
In-Reply-To: <3.0.6.32.20011117210915.00a8cab0@mail.doorpi.net>
Hi. You should just get the speakup-1.00.tar.gz from the speakup
ftp sight. It's the latest version and should be easier for you to install.
Kenny
On Sat, Nov 17, 2001 at 09:09:15PM -0600, Brent Harding wrote:
> Cool. haven't had any cvs sources fail on me yet besides getting failed
> patches when I tried to get the new speakup. I suppose, some how I have to
> find the old version and reverse the patches and reapply, the rpm I had
> already had speakup in. I suppose to people who don't write code, cvs is
> just another way to download files, giving the latest up to the minute
> version, which could be bad if someone just committed a change that breaks
> it all.
> At 07:47 PM 11/17/01 -0000, you wrote:
> >Hi
> >
> >Further to my previous reply to this message. I guess you'll find that your
> >functional level will be low. But if it meets your needs that's fine. As
> >you seem to be using rpm and cvs sources here's the cvs strings for
> >SpeakFreely.
> >
> >cvs -d:pserver:anonymous@linux-speakup.org:/usr/src/CVS login
> >cvs -d:pserver:anonymous@linux-speakup.org:/usr/src/CVS co speak_freely
> >
> >Gena
> >
> >-----Original Message-----
> >From: blinux-list-admin@redhat.com
> >[mailto:blinux-list-admin@redhat.com]On Behalf Of Brent Harding
> >Sent: 17 November 2001 15:30
> >To: blinux-list@redhat.com
> >Subject: RE: missing ao.h
> >
> >
> >I'm using kernel 2.4.3-12, but speakup was already patched in, got the rpm
> >from Bill's ftp site, so the script seemed to not work, unless I need to
> >run it from a certain place. I don't as of yet have speakfreely going, but
> >redhat's sndconfig detected my sblive, there's apparently no alsa rpm, and
> >the mixer levels are a pain to get going, the osfree ones already work.
> >At 12:20 PM 11/17/01 -0000, you wrote:
> >>Hi
> >>
> >>Is your Speakup comment a question? The checkout script is on the Speakup
> >>site and I've had no problem. Of course pre 2.2.18 kernels are not
> >suitable
> >>for the later versions of Speakup but I don't think that this is applicable
> >>to you. I see you haven't raised the issue on the Speakup list. To access
> >>the CVS server you simply press enter for anonymous and the password is
> >>"please" as it doesn't hurt to be polite, does it?
> >>
> >>Don't forget there's also the Speakup reflector where you can raise your
> >>questions. Even microdollar screen readers can't offer this level of
> >>support.
> >>
> >>Gena
> >>
> >>-----Original Message-----
> >>From: blinux-list-admin@redhat.com
> >>[mailto:blinux-list-admin@redhat.com]On Behalf Of Brent Harding
> >>Sent: 17 November 2001 04:47
> >>To: blinux-list@redhat.com
> >>Subject: Re: missing ao.h
> >>
> >>
> >>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
> >>>
> >>>
> >>
> >>
> >>
> >>_______________________________________________
> >>Blinux-list mailing list
> >>Blinux-list@redhat.com
> >>https://listman.redhat.com/mailman/listinfo/blinux-list
> >>
> >>
> >>
> >>_______________________________________________
> >>Blinux-list mailing list
> >>Blinux-list@redhat.com
> >>https://listman.redhat.com/mailman/listinfo/blinux-list
> >>
> >>
> >
> >
> >
> >_______________________________________________
> >Blinux-list mailing list
> >Blinux-list@redhat.com
> >https://listman.redhat.com/mailman/listinfo/blinux-list
> >
> >
> >
> >_______________________________________________
> >Blinux-list mailing list
> >Blinux-list@redhat.com
> >https://listman.redhat.com/mailman/listinfo/blinux-list
> >
> >
>
>
>
> _______________________________________________
> 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
` Georgina
` Brent Harding
` Georgina
` Georgina
` Brent Harding
` Kenny Hitt [this message]
` getting speakup wasRe: " 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=20011118071048.A1184@learning \
--to=kennyhitt@yahoo.com \
--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).