From: Christopher.Vance@adfa.oz.au Christopher.Vance@adfa.oz.au
Subject: Can't mk 9pc
Date: Wed, 20 Dec 1995 01:34:52 -0500 [thread overview]
Message-ID: <19951220063452.B62Yd-eDb2IV7oQYo4g55SCfFrmhgtCBoB-My5p1evg@z> (raw)
"Luther Huffman, Jr." <lutherh@mail.infinet.com> wrote:
| I've been trying to apply the latest updates (816407398) to
| /sys/src/9/pc and I've run into a problem.
| The extraction and creation of the updated files goes smoothly.
| When I use "mk" on the patched source, the compilation goes off
| without a hitch. During linking, however, Plan 9 gives up the ghost
| and gives me the message "Out of memory". My Pentium PC has 16 MB of
| RAM. Shouldn't that be enough to link 9pc?
I've been linking kernels on a 486DX2/66 with 8M. It only worked when I
started swapping onto a u9fs server. The largest process size I saw was
about 12M for 8l. My links took about an hour each.
-- Christopher
next reply other threads:[~1995-12-20 6:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-12-20 6:34 Christopher.Vance [this message]
1995-12-20 10:45 Luther
1995-12-20 12:27 Nigel
1995-12-20 12:28 Nigel
1995-12-20 14:17 steve
1995-12-20 14:21 Nigel
1995-12-20 18:19 Luther
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=19951220063452.B62Yd-eDb2IV7oQYo4g55SCfFrmhgtCBoB-My5p1evg@z \
--to=christopher.vance@adfa.oz.au \
/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 NNTP newsgroup(s).