From: claudio@conectiva.com
To: Harry Kalogirou <harkal@gmx.net>
Cc: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: binary size changes from 0.1.0
Date: Fri, 11 Jun 2004 11:36:48 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.58L.0406111128080.486@damien.conectiva> (raw)
In-Reply-To: <1086904319.1095.417.camel@cool>
On Fri, 11 Jun 2004, Harry Kalogirou wrote:
> > One common trick is to not keep the list of error messages in memory
> > but to keep them in a file on disk. When perror() is called, the file is
> > opened, read until the right error message is found, and that one used...
>
> I think ELKS's libc does that... at least it used to do...
It does that it you use -Mf to use the "small and fast" libc_f. The
default behaviour is to include the strings in every binary. This option
also changes the function call protocol. I made some tests and the
resulting binaries are significantly smaller, similar to those in the
0.1.0 disk images.
prev parent reply other threads:[~2004-06-11 14:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 18:55 binary size changes from 0.1.0 claudio
2004-06-10 7:35 ` Gábor Lénárt
2004-06-10 9:52 ` David Given
2004-06-10 11:05 ` Gábor Lénárt
2004-06-11 0:52 ` Harry Kalogirou
2004-06-11 14:36 ` claudio [this message]
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=Pine.LNX.4.58L.0406111128080.486@damien.conectiva \
--to=claudio@conectiva.com \
--cc=harkal@gmx.net \
--cc=linux-8086@vger.kernel.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