From: Igor Gueths <igueths@attbi.com>
To: speakup <speakup@braille.uwo.ca>
Subject: Re: trouble compiling speakfreely 7.2
Date: Fri, 19 Apr 2002 14:15:20 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0204191412230.460-100000@igueths> (raw)
In-Reply-To: <Pine.LNX.4.44.0204190829270.249-100000@maranatha.chartermi.net>
Hi all. I didn't edit the makefile for speak freely, it seems to have
built ok. Will see if it works.
On Fri, 19 Apr 2002, Cheryl Homiak wrote:
> I suggest that you start with a clean tree and change nothing except the "duplex
> =" line, and see what happens. Also, remember that any time you have to do a new
> "make" with a source tree you've already used, you have to run "make clean"
> first.
> In this case, though, I think you might just want to start fresh, chanbge just
> the one line by uncommenting it, and then see whether or not anything else
> really needs editing.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
prev parent reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Cheryl Homiak
` Igor Gueths [this message]
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.0204191412230.460-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).