From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: Re: "Virtual Memory exhausted" message during compilation
Date: Mon, 2 Oct 2000 06:33:35 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0010020632590.1427-100000@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.21.0010012309350.4216-100000@jscp.yi.org>
I have another idea. Why not have Jacob send you the bianary. I know it
isn't as sexy as compiling for yourself, but chances are it would run just
fine.
--
Kirk Wood
Cpt.Kirk@1tree.net
------------------
Seek simplicity -- and distrust it.
Alfred North Whitehead
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Victor Tsaran
` Jacob Schmude
` Victor Tsaran
` Jacob Schmude
` Kirk Wood [this message]
` Kerry Hoath
` Victor Tsaran
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.21.0010020632590.1427-100000@localhost.localdomain \
--to=cpt.kirk@1tree.net \
--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).