The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: sms@2BSD.COM (Steven M. Schultz)
Subject: [pups] 2BSD build problem - unix.o not too big
Date: Mon, 17 Mar 2003 08:38:06 -0800 (PST)	[thread overview]
Message-ID: <200303171638.h2HGc6401078@moe.2bsd.com> (raw)

Hi -

> From: David Evans <dfevans at bbcr.uwaterloo.ca>
> 
>   I don't recall seeing any overlay info when I set up my 11/73 back in
> January.  I even asked the dreaded overlay FAQ here!  :)  I was also at 431.

	Ok, I probably only thought about including the writeup in the
	documentation.   I know I did write up a moderately lengthy 
	article about dealing with the overlay setup in response to a
	problem someone was having.  I just never went and incorporated it 
	into the setup/installatino documentation ;(

	One thing, obvious now that I think of it, I forgot to mention last
	night is that "too big for type 431" can also happen if the D space
	total is too large.   If 'MAXUSERS' is set too high for example
	then more than 48KB of D space will be needed and the linker will
	complain.    Look at the sum of the DATA and BSS segments (it might
	be necessary to sum up the .o files individually) - if it's pushing
	48KB then that's the problem.

	Cheers,
	Steven Schultz



             reply	other threads:[~2003-03-17 16:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-17 16:38 Steven M. Schultz [this message]
2003-03-19  2:24 ` [pups] 2.11BSD "make unix" aborts Error 141 Jonathan Engdahl
  -- strict thread matches above, loose matches on Subject: below --
2003-03-17  7:36 [pups] 2BSD build problem - unix.o not too big Steven M. Schultz
2003-03-17 14:45 ` David Evans
2003-03-17  6:13 Ian King

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=200303171638.h2HGc6401078@moe.2bsd.com \
    --to=sms@2bsd.com \
    /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).