From: "Doug Sutherland" <doug@proficio.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: TTSynth Is Available Again
Date: Tue, 19 Jun 2007 22:12:59 -0500 [thread overview]
Message-ID: <003101c7b2e8$e7e52760$ab00a8c0@tenstac> (raw)
In-Reply-To: <20070619211310.GA9480@themuso.com>
Luke said:
While making a tarball would be easy, the person using it would have to
be sure they had the libstdc++-libc6.2-2.so.3 shared library, which is
from gcc 2.95. Luckily, Ubuntu/Debian and Fedora still carry this, but I
doubt very much whether other distros do, and it would certainly not be
trivial to build it.
Doug adds:
It's not trivial but it is doable. I have in fact done exactly that with the
ibm tts in the past, both on LFS and slackware. It does take some
considerable work, because we're talking raw guts of toolchain here.
There various parts of toolchain of specific version that are known to
work with specific versions of the other parts, like any given gcc will
work with some version of binutils and glibc etc. But I can say it is
doable and satisfying to get it done. It is also an opportunity to use
the knowledge gained in LFS toolchain build to good use. It is even
possible to actually have two different glibc versions on a system.
I wish I would have kept specific notes on what I did, but oh well.
Actually some of my notes may be in the archives of this list, I seem
to recall posting at least some info about what I did to make it work.
After changing distros, kernels, versions, etc so many times I gave
up on ibm tts, but I really do love that product. It's a shame that
ibm gave up on it, I recall an IBM engineer explaining that they
spent millions on it and could not keep doing that for free. I think
however that most of that work was on the recogniton part. The
tts was tiny compared to the recognition engine and it was clear
that their focus was on recognition. They were and are a bit out
of touch because tts has much more direct useful application
while the recognition was not worth it for me, it was cool to
play with but not accurate. It seems they have since shifted their
efforts in two other directions instead of regular old linux, they
focused on speech on embedded systems, and rolled their
speech strategy into websphere, where they make gazillions
of dollars selling to big enterprise. I suppose we should just
be glad that linux work is still available. It was a strange idea
how they did the tts, you could buy it .. or not. It was free
but you could buy it! And they wondered why nobody did.
Still chuckling over that.
-- Doug
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
Janina Sajka
` Cody Hurst
` Janina Sajka
` ace
` Gaijin
` doubletalk lt randy turner
` Gregory Nowak
` TTSynth Is Available Again Janina Sajka
` Gregory Nowak
` Luke Yelavich
` Doug Sutherland [this message]
` Janina Sajka
` Georgina Joyce
` Doug Sutherland
` Jim Grimsby Jr.
` Doug Sutherland
` Georgina Joyce
` Georgina Joyce
` Steve Dawes
` Fedora 7 Questions: Steve Dawes
` TTSynth Is Available Again Travis Siegel
` Doug Sutherland
` Travis Siegel
` Doug Sutherland
` Travis Siegel
` Doug Sutherland
` Travis Siegel
` Doug Sutherland
hanke
` Luke Yelavich
` Doug Sutherland
` Janina Sajka
` hanke
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='003101c7b2e8$e7e52760$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).