From: "John G. Heim" <jheim@math.wisc.edu>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Fw: information on making speakup work with soft synths
Date: Fri, 18 Jul 2008 14:15:05 -0500 [thread overview]
Message-ID: <007501c8e90a$95e8b5e0$5501a8c0@mcgee> (raw)
Correction:
The list of packages I give below is incorrect. 2 of the packages don't
exist. The correct list is as follows.
autoconf automake g++ libdotconf-dev libglibmm-2.4-dev libspeechd-dev
libspeechd2 libtool speech-dispatcher texi2html texinfo
----- Original Message -----
From: "John Heim" <jheim@math.wisc.edu>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Monday, July 14, 2008 10:02 AM
Subject: Re: information on making speakup work with soft synths
>
> ----- Original Message ----- > I fear however that it is a little outdated
> in details, especially
>> on the speakup side. I'd appreciate if anyone could point comments
>> on whether this howto needs to be changed.
>
>
> I just compiled speechd-up on a new-ish debian machine. I grepped my bash
> history for things I installed while trying to compile it. Here is the
> list:
>
> autoconf
> automake
> g++
> libdotconf
> libdotconf-dev
> libglibmm-2.4-dev
> libspeechd-dev
> libspeechd2
> libtool
> makeinfo
> speech-dispatcher
> texi2html
> texinfo
>
> I kind of remember installing each of these in response to error messages
> I got during the compile. So I think most, if not all of the packages in
> the above list are necessary. I think the docs say that texinfo and
> texi2html aren't required but I think they are. Speech-dispatcher might
> not be required. I haven't tried it without installing that first.
>
> I know this is a difficult issue for you as a documentation writer &
> source code maintainer. The problem is that if any of these packages is
> missing, you get very cryptic error messages. In some cases, I had to do
> some serious detective work to figure out what I had to install to get the
> compile to keep going.
>
> Of course, even the above list probably isn't exhaustive. My system
> probably had a bunch of packages installed that would have caused problems
> had they been missing.
>
>
> So good luck with the docs.
>
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='007501c8e90a$95e8b5e0$5501a8c0@mcgee' \
--to=jheim@math.wisc.edu \
--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).