From: "Doug Sutherland" <doug@proficio.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: ttsynth help: download problem
Date: Mon, 25 Jun 2007 21:50:16 -0500 [thread overview]
Message-ID: <001501c7b79c$b9f60dc0$ab00a8c0@tenstac> (raw)
In-Reply-To: <Pine.LNX.4.63.0706251245430.6568@desktop.localnet>
Mike,
> I read the message about getting viavoice working on Slackware 9.1 and
> tried to follow directions. There were tons of errors. Guess ttsynth is
> a bust after all as I'll probably never get working.
Most likely the reason is that you're not on slackware 9.1, so you
have newer versions of gcc, glibc, and binutils, and when you tried
to compile the old glibc it ... gave you tons of errors. As I said
earlier, these toolchains are very tricky compatibility wise. It is
most likely still possible but would require more work that I did
three years ago because the current system at that time was
still compatible with the glibc for compilation. I plan to try to do
a more recent build with slackware 11.0 in the near future, so I
may have updated instructions at some point, but I can't make
any promises because it takes a lot of experimentation to do
those toolchain builds. If you really want that old tts engine to
work, it may actually be easier to go with the supported distros
like debian or ubuntu. I think IBM made a fairly huge mistake
when they packaged this engine.
-- Doug
prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
Mike Keithley
` Luke Yelavich
[not found] ` <Pine.LNX.4.63.0706232011230.6171@desktop.localnet>
` Luke Yelavich
` Mike Keithley
` Doug Sutherland
` Mike Keithley
` Christopher Moore
` Doug Sutherland [this message]
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='001501c7b79c$b9f60dc0$ab00a8c0@tenstac' \
--to=doug@proficio.ca \
--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).