From: chd_1@nktelco.net (Chuck Dickman)
Subject: [pups] bsd2.11 kernel compile
Date: Mon, 17 Jun 2002 22:40:55 -0400 [thread overview]
Message-ID: <3D0E9DB7.988203A@nktelco.net> (raw)
In-Reply-To: <3D0E81C0.9046BF5D@bellsouth.net>
joseph lang wrote:
> When compiling a new kernel (to include network) I get an error
>
> ld: too big for type 431
> *** exit 2
>
> I assume this error is due to one of the overlays being too
> large. (this is pointed out in the install docs)
During the compile 'size' outputs a list of the sizes of the
overlays. Look at the output. For mine....
# size unix ! the OS kernel
text data bss dec hex
55296 6492 20738 82526 1425e total text: 106752
overlays: 7744,7360,7872,7296,3072,7680,4864,5568
# size netnix ! the network code
text data bss dec hex
60864 2362 38448 101674 18d2a
> How do I figure out which overlay (or base) is the problem?
The base must be less than 7 8k pages or 57344(decimal) bytes.
Each overlay must be less than 8k bytes or 8192(decimal).
The network code is not overlayed, so you have 8 pages or the
full 64k.
> Is there a more scientific way to arrange the overlays?
To make it work, just get the sizes below the limits. The
optimal arrangement would be placing the code in such that
the overlay changes were minimized. So... move your system
disk drivers into base and change the configuration to
remove any hardware you don't actually have.
> Am I missing something obvious?
No, it just requires some tweeking.....
> joe lang
Good luck,
-chuck
next prev parent reply other threads:[~2002-06-18 2:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 0:41 joseph lang
2002-06-18 2:40 ` Chuck Dickman [this message]
2002-06-18 7:55 ` Jochen Kunz
2002-06-19 0:42 ` joseph lang
2002-06-18 3:11 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=3D0E9DB7.988203A@nktelco.net \
--to=chd_1@nktelco.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).