The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: iking@killthewabbit.org (Ian King)
Subject: [pups] 2BSD build problem - unix.o not too big
Date: Sun, 16 Mar 2003 22:13:55 -0800	[thread overview]
Message-ID: <000a01c2ec4c$63e5cf30$450010ac@dawabbit> (raw)

Steven,

I'm building a 2.11BSD kernel on my 11/73 (so I can include the networking
code and put my machine on the LAN!), and I'm seeing the error "too big for
type 431".  Through the wonders of Google, I saw your discussion of this
error and followed your advice (from 1996!).  However, when I ask 'size
unix.o', I get a size comfortably within the limits for base - 50112, well
below the 57344 you cite.  None of the overlays exceeds 8192, and the 'total
text' figure is well below your example, too.  FWIW, I did a 'naive build'
first, copying GENERIC and changing a few parameters; after seeing the error
'text segment too big' I went through the config file with a little more
thought and eliminated drivers I clearly didn't need (I don't have RL01/02s,
for instance).  Then I started getting this error.  I did a 'make clean'
just to be sure, but still make gives me the 'too big for type 431' error.
(Yes, I RTFM on ld.)

I am standing here beside myself.  :-)  And I am humbly soliciting
suggestions....  -- Ian

PS: I'm at patch level 431, per the VERSION file.




             reply	other threads:[~2003-03-17  6:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-17  6:13 Ian King [this message]
2003-03-17  7:36 Steven M. Schultz
2003-03-17 14:45 ` David Evans
2003-03-17 16:38 Steven M. Schultz

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='000a01c2ec4c$63e5cf30$450010ac@dawabbit' \
    --to=iking@killthewabbit.org \
    /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).