From: "Thomas D. Ward" <tward1978@earthlink.net>
To: <speakup@braille.uwo.ca>
Subject: Re: ssh for linux 7
Date: Fri, 13 Jun 2003 08:41:16 -0400 [thread overview]
Message-ID: <000f01c331a9$15a9f600$09849641@tward1978> (raw)
In-Reply-To: <Pine.LNX.4.53.0306130816580.603@localhost>
Hi, both flite and eflite built fine using gcc 3.2 on my Red Hat system.
That is truely weird why they wouldn't compile on your system.
----- Original Message -----
From: jude dashiell <dashielljt@gmpexpress.net>
To: <speakup@braille.uwo.ca>
Sent: Friday, June 13, 2003 8:19 AM
Subject: Re: ssh for linux 7
> If you intend to install festival or eflite, keep your de package from
> your earlier version handy since gcc 3.22 will not build either of these
> packages. I did manage to get both built and installed with gcc 2.95.3
> though.On Fri, 13 Jun 2003, Doug wrote:
>
> > It is not very difficult to reinstall slackware.
> > Granted, I've done it many times over, but for me
> > it only takes about 15 minutes.
> >
> > It is probably worthwhile to upgrade from version 7
> > to the newer slackware 9. There have been many many
> > improvements to everything.
> >
> > There is a .iso image that can be easily burned
> > onto CD-ROM. It is also easy to install from the
> > hard drive. He can download the packages to the
> > hard drive, create boot floppies, and install
> > with no need for CD-ROM.
> >
> > -- Doug
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
Diana Dawne
` Gregory Nowak
` Doug
` Gregory Nowak
` Diana Dawne
` Gregory Nowak
` Doug
` jude dashiell
` Doug
` Thomas D. Ward [this message]
` Adam Myrow
` Igor Gueths
[not found] <Pine.LNX.4.44.0306121012350.11326-100000@t-rex.dianasaur.c om>
` Doug
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='000f01c331a9$15a9f600$09849641@tward1978' \
--to=tward1978@earthlink.net \
--cc=speakup@braille.uwo.ca \
/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).