From: "Michael Whapples" <mwhapples@aim.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: installing voxin on arch
Date: Tue, 12 Oct 2010 17:50:19 +0100 [thread overview]
Message-ID: <4D46B51EF9EE4D94A8F139194180C089@Mikelaptop> (raw)
In-Reply-To: <4CB47ABA.1000907@gmail.com>
Hello,
Actually it shouldn't be hard. One option is to extract the old libstdc++ files from the debian package and then install the IBMtts using the voxin installer script. The alternative for the old libstdc++ library is to look at the libstdc++296 package in AUR (I think that will provide the required library). Again if using libstdc++296 from AUR you will have to run the voxin installer to install IBMtts.
Anyway, the voxin installer script is not suitable for installing gnome-speech and speech-dispatcher backends, look at recompiling those packages (this wiki page on ABS may help http://wiki.archlinux.org/index.php/Arch_Build_System).
I have created an AUR package for the IBMtts speakup connector under the name spk-connect-ttsynth.
I hope this helps.
Michael Whapples
----- Original Message -----
From: "Christopher Moore" <chris.w1gm@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Tuesday, October 12, 2010 4:11 PM
Subject: installing voxin on arch
> Hello,
> I'm looking for tips on how to install voxin on arch linux. I wish they
> provided arch packages but I'll have to work around it.
>
> Chris
>
>
__________ Information from ESET NOD32 Antivirus, version of virus signature database 5524 (20101012) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Christopher Moore
` Michael Whapples [this message]
` Re[2]: " Christian
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=4D46B51EF9EE4D94A8F139194180C089@Mikelaptop \
--to=mwhapples@aim.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).