From: "Shaun Oliver" <shauno@sgtnet.com.au>
To: <speakup@braille.uwo.ca>
Subject: Re: zipspeak alert/bug
Date: Sun, 18 Mar 2001 19:44:14 +1100 [thread overview]
Message-ID: <001001c0af87$9ce3e280$1800a8c0@Shaun> (raw)
In-Reply-To: <200103172335.PAA25376@viper.wapvi.bc.ca>
tiler...
try looking on that ftp site where zipspeak is and looking in the various a
and n folders to find the appropreiate packages you need..
Shaun
----- Original Message -----
From: "Tyler Spivey" <tyler@wapvi.bc.ca>
To: <speakup@braille.uwo.ca>
Sent: Sunday, March 18, 2001 10:35 AM
Subject: zipspeak alert/bug
> it seems that matt destroyed zipspeak: their's no /usr/lib/libc.a. i need
it to compile bash, for a linuxfromscratch system. i need an umsdos system ,
to compile these things, but not an obliterated one. any
> suggestions? where can i find libc.a and friends?
> libc.so is their, but the .a files are gone.
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
prev parent reply other threads:[~ UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
Tyler Spivey
` Matthew Campbell
` Shaun Oliver
` Shaun Oliver [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='001001c0af87$9ce3e280$1800a8c0@Shaun' \
--to=shauno@sgtnet.com.au \
--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).