From: G. David Butler gdb@dbSystems.com
Subject: 386 maximum segment size of 16Mb
Date: Thu, 2 Nov 1995 11:21:55 -0500 [thread overview]
Message-ID: <19951102162155.E4_pO94I8n7E1sTFCFVEL2Vfxpjx7gpHh2Y5qNDx45o@z> (raw)
Hello again,
Has anybody noticed the problem compiling /sys/src/libtiff/tif_fax3.c on
a 386? It seems 8c needs more than 16Mb of data space to build this one.
The real question, has anybody looked into increasing this limit? (look
in /sys/src/9/pc/mem.h, SEGMEMSIZE, I think, set to 16.)
Thanks.
next reply other threads:[~1995-11-02 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-02 16:21 G.David [this message]
1995-11-02 17:14 G.David
1995-11-02 18:28 G.David
1995-11-02 18:38 philw
1995-11-03 8:33 Nigel
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=19951102162155.E4_pO94I8n7E1sTFCFVEL2Vfxpjx7gpHh2Y5qNDx45o@z \
--to=9fans@9fans.net \
/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).