From: jkunz@unixag-kl.fh-kl.de (Jochen Kunz)
Subject: [pups] bsd2.11 kernel compile
Date: Tue, 18 Jun 2002 09:55:12 +0200 [thread overview]
Message-ID: <20020618095512.I163999@MissSophie.unixag-kl.fh-kl.de> (raw)
In-Reply-To: <3D0E81C0.9046BF5D@bellsouth.net>; from langj@bellsouth.net on Tue, Jun 18, 2002 at 02:41:36 CEST
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]
On 2002.06.18 02:41 joseph lang wrote:
> How do I figure out which overlay (or base) is the problem?
Add this to your Makefile and you can "make" a list of the individual
overlay sizes:
sizes: sizes.awk
@echo -n "BASE " ; size ${BASE} | awk -f sizes.awk
@echo -n "OV1 " ; size ${OV1} | awk -f sizes.awk
@echo -n "OV2 " ; size ${OV2} | awk -f sizes.awk
@echo -n "OV3 " ; size ${OV3} | awk -f sizes.awk
@echo -n "OV4 " ; size ${OV4} | awk -f sizes.awk
@echo -n "OV5 " ; size ${OV5} | awk -f sizes.awk
@echo -n "OV6 " ; size ${OV6} | awk -f sizes.awk
@echo -n "OV7 " ; size ${OV7} | awk -f sizes.awk
@echo -n "OV8 " ; size ${OV8} | awk -f sizes.awk
@echo -n "OV9 " ; size ${OV9} | awk -f sizes.awk
sizeb: FRC
size ${BASE}
size1: FRC
size ${OV1}
size2: FRC
size ${OV2}
size3: FRC
size ${OV3}
size4: FRC
size ${OV4}
size5: FRC
size ${OV5}
size6: FRC
size ${OV6}
size7: FRC
size ${OV7}
size8: FRC
size ${OV8}
size9: FRC
size ${OV9}
sizes.awk: FRC
echo 'BEGIN {sum=0' > sizes.awk
echo 'sum2=0' >> sizes.awk
echo 'sum3=0}' >> sizes.awk
echo '/^[0-9]/ {sum=sum+$$1' >> sizes.awk
echo 'sum2=sum2+$$1+$$2' >> sizes.awk
echo 'sum3=sum3+$$4}' >> sizes.awk
echo 'END {print "text: "sum " text+data: " sum2
" dec: " sum3}' >> sizes.awk
--
tschüß,
Jochen
Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/
next prev parent reply other threads:[~2002-06-18 7:55 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
2002-06-18 7:55 ` Jochen Kunz [this message]
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=20020618095512.I163999@MissSophie.unixag-kl.fh-kl.de \
--to=jkunz@unixag-kl.fh-kl.de \
/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).