From: Igor Gueths <igueths@attbi.com>
To: speakup <speakup@braille.uwo.ca>
Subject: Re: compiling speakfreely 7.2
Date: Thu, 18 Apr 2002 16:24:37 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0204181622230.228-100000@igueths> (raw)
In-Reply-To: <Pine.LNX.4.44.0204180909260.1557-100000@maranatha.chartermi.net>
Hi Cheryl. Thanks for the info on that one, will try it today at some
point. Just out of curiosity, when make refered to the target in my error
message from yesterday, is target refering to the duplex of your audio
hardware? Because when I saw target, I immediately thought system
architecture i.e., i686. I searched for that, but found nothing related.
Then I got confused.
On Thu, 18 Apr 2002, Cheryl Homiak wrote:
> I think I can answer the question from yesterday about the "commands commence
> before target" or something similar, because the same thing happened to me.
> It probably means you uncommented the wrong line. In my case, I commented an
> earlier line with duplex in it instead of waiting till I got to the one that
> starts "duplex =" without the quotes of course.
> Hope this helps.
>
>
> _______________________________________________
> 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: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Cheryl Homiak
` Igor Gueths [this message]
` Cheryl Homiak
` Igor Gueths
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.44.0204181622230.228-100000@igueths \
--to=igueths@attbi.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).