From: Willem van der Walt <wvdwalt@csir.co.za>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: A couple problems
Date: Tue, 31 Oct 2006 08:17:17 +0200 (SAST) [thread overview]
Message-ID: <Pine.LNX.4.64.0610310813030.538@localhost.localdomain> (raw)
In-Reply-To: <7.0.1.0.2.20061030161745.02600070@sbcglobal.net>
Hi,
Why do you not just install the binary version of espeak?
It should sort out the first compile problem.
I start speach-dispatcher -d
I think you can try that.
Ssh into the box, not telnet, telnet is most likely not running.
You could try to press alt-f2 to get another terminal and try to log in
blindly.
HTH, Willem
On Mon, 30 Oct 2006, Guy Schlosser wrote:
> Hello all:
>
> I've got a couple problems and need a little assistance figuring out
> what's going on. First, I got my Fedora core 6 installed without
> problems. I installed speech-dispatcher from the tar balls at
> www.freebsoft.org, and all seems to have went OK there. Here's where
> I'm having trouble. 1., when I try to compile Espeak after doing yum
> install portaudio, I get make errors that say "no definition for
> thread join and thread cancel." Lastly, I put the following lines in
> my rc.local file to get speech-dispatcher running, and at least
> festival for now.
> festival --server
> speech-dispatcher.
>
> Now, when I boot, I get the message from festival that says that the
> server started, and then I don't get to the login prompt. Is there
> something I should have put after festival --server? Or, is there a
> better way to start festival and speech-dispatcher on
> boot? Furthermore, how can I regain access to my box? Do I have to
> telnet in from another machine? Any help would be greatly appreciated.
>
> Thanks in advance,
>
>
> Guy
>
>
> --
> No virus found in this outgoing message.
> Checked by AVG.
> Version: 7.5.427 / Virus Database: 268.13.17/505 - Release Date: 10/27/2006 3:15 PM
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
--
This message is subject to the CSIR's copyright, terms and conditions and
e-mail legal notice. Views expressed herein do not necessarily represent the
views of the CSIR.
CSIR E-mail Legal Notice
http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html
CSIR Copyright, Terms and Conditions
http://mail.csir.co.za/CSIR_Copyright.html
For electronic copies of the CSIR Copyright, Terms and Conditions and the CSIR
Legal Notice send a blank message with REQUEST LEGAL in the subject line to
CallCentre@csir.co.za.
This message has been scanned for viruses and dangerous content by MailScanner,
and is believed to be clean. MailScanner thanks Transtec Computers for their support.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
Guy Schlosser
` Willem van der Walt [this message]
` guy schlosser
Michael Whapples
` guy schlosser
` Willem van der Walt
Michael Whapples
Michael Whapples
` Willem van der Walt
` Sina Bahram
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=Pine.LNX.4.64.0610310813030.538@localhost.localdomain \
--to=wvdwalt@csir.co.za \
--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).