From: Christopher Moore <chris.w1gm@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: IBMtts speakup connector AUR package
Date: Fri, 22 Oct 2010 14:15:16 -0400 [thread overview]
Message-ID: <20101022181513.GA3102@nextdog> (raw)
In-Reply-To: <4CACFD87.2040806@aim.com>
Michael,
Nice job on the speakup-connector package. I installed it without a hitch.
The Voxin installer wasn't designed with arch linux in mind.
Fortunately I was able to copy the necessary files from a previous
installation. It's
actually quite simple.
1. From your previous installation, make two tar.gz files from /opt/IBM
and /var/opt/IBM.
2. untar the files on your new system with a command like:
cd /; sudo tar zxvf file1.tar.gz
3. make symlinks in /usr/lib for the two libraries:
libibmeci.so and libetidev.so
You can use the say program to test it although in my case
I had to stop espeakup to free the soundcard.
The suggestion about installing the libstdc++296 package also worked for me.
This saved me the pain of dealing with a .deb package supplied with voxin.
Finally, another tool I have discovered is yaourt. This is a front-end
to the standard arch package manager (pacman).
It makes it easy to search for and install packages from the aur
as well as those included with arch.
Chris
On Wed, Oct 06, 2010 at 11:51:51PM +0100, Michael Whapples wrote:
> Hello,
> For those of you who use archlinux and IBMtts I have created a
> speakup connector package in AUR under the name spk-connect-ttsynth.
> This includes a start up script called spk-connect, so if you want
> it to start at start up then add spk-connect to the daemons array in
> /etc/rc.conf.
>
> Michael Whapples
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
prev parent reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Michael Whapples
` Christopher Moore [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=20101022181513.GA3102@nextdog \
--to=chris.w1gm@gmail.com \
--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).