From: "Littlefield, Tyler" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: no speech
Date: Mon, 23 Jul 2007 10:29:08 -0600 [thread overview]
Message-ID: <003201c7cd46$99923850$6701a8c0@tdsportable> (raw)
In-Reply-To: <20070723091242.D686760F@pop16.mta.everyone.net>
mv problems /dev/null
Thanks,
Tyler Littlefield.
Vertigo head coder
"My programs don't have bugs, just randomly added features."
msn: compgeek134@hotmail.com
email: compgeek13@gmail.com
aim: st8amnd2005
skype: st8amnd127
----- Original Message -----
From: "Guy Schlosser" <guyster@buckeye-express.com>
To: <speakup@braille.uwo.ca>
Sent: Monday, July 23, 2007 10:12 AM
Subject: no speech
>
>>Hi all, I'm still trying to get Speech-dispatcher 0.6.4 beta 1 up
>>and running. I downloaded the dependencies for compiling
>>speech-dispatcher (apt-get build-dep speech-dispatcher", and also
>>portaudio19, since I'd like to compile Espeak against portaudio19,
>>in case I have to use it with gnome-speech. I recompiled sd 0.6.4,
>>using make uninstall, then the ./configure, make, make install
>>process. During the ./configure process, I saw something about
>>compiling with alsa support succeeding. I then got excited, added
>>the module (espeak, not espeak-generic), set it as my output module,
>>then rebooted. Now, I have no speech, even when I switch back to
>>gnome-speech. Anyone have any ideas? I want to compile the new
>>Espeak, just so I have the most recent installed. Do I do
>>./configure, make, and make install there too? Thanks in advance
>>for any help. Here's hoping to get back up and running soon.
>>
>>Thanks again,
>>
>>
>>Guy
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Guy Schlosser
` Littlefield, Tyler [this message]
-- strict thread matches above, loose matches on Subject: below --
Guy Schlosser
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='003201c7cd46$99923850$6701a8c0@tdsportable' \
--to=compgeek13@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).