From: Christopher Moore <christopher.h.moore@verizon.net>
To: speakup@braille.uwo.ca
Subject: Re: using speakup with festival or flite
Date: Wed, 16 Apr 2003 11:32:17 -0400 [thread overview]
Message-ID: <20030416153217.GA252@chris> (raw)
In-Reply-To: <Pine.LNX.4.53.0304160037450.684@princenet.sytes.net>
I've had no problems compiling flite or eflite on slackware 8.1.
Unfortunately, you haven't bee too specifid. Does the configure script
run? Are you missing libraries or header files? How far does you make
get? etc.
Chris
On Wed, Apr 16, 2003 at 12:40:59AM -0400, Lorenzo Prince wrote:
> I couldn't get flite to compile on a slackware machine running an Athlon
> XP 1800+ processor. I have a friend who also couldn't get it to compile
> on a pIII 850MHZ. Both machines were running slack8.1. Neither one of us
> could get eflite to compile either. We had to use the Debian packages for
> both programs and use Alien to convert them to Slack packages to instal
> them.
>
> Lorenzo
>
> E Pluribus Unix
>
> Jacob Schmude staggered into view and mumbled:
>
> > Hi
> > I didn't have to do anything special, ./configure, make, and make install
> > did the trick. Then again, this is a standard 2.13ghz athlon I'm working
> > on, I'm not messing with any special boards. Watch it, though, internal
> > gcc errors can possibly forecast future hardware, especially memory,
> > problems.
> >
> > On Tue, 15 Apr 2003, Doug Sutherland wrote:
> >
> > > Jacob wrote:
> > >
> > > > I've never had a problem compiling flite, both on slack 8.1
> > > > and 9.0.
> > >
> > > Did you have to do anything special with the makefiles?
> > > It never seems to work for me with the standard gcc that
> > > comes with slack.
> > >
> >
> > _______________________________________________
> > 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
--
The Moon is Full
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
Don Raikes
` Doug Sutherland
` Jacob Schmude
` Doug Sutherland
` Jacob Schmude
` Lorenzo Prince
` Doug Sutherland
` Lorenzo Prince
` Christopher Moore [this message]
` Steve Holmes
` Adam Myrow
` Lorenzo Prince
` Christopher Moore
` Lorenzo Prince
` Christopher Moore
` Thomas D. Ward
` Lorenzo Prince
` Thomas D. Ward
` Doug Sutherland
` Thomas D. Ward
` Doug Sutherland
` rmann
` Doug Sutherland
` Thomas D. Ward
` Doug Sutherland
` Thomas D. Ward
` Lorenzo Prince
` Doug Sutherland
` Lorenzo Prince
` Thomas D. Ward
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=20030416153217.GA252@chris \
--to=christopher.h.moore@verizon.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).