From: "Joshua Nye" <josh@boxcarmedia.com>
To: "Michiel Buddingh'" <ajuin+mail@stack.nl>, <gcc-help@gcc.gnu.org>
Subject: Re: Giant executables.. what am I doing wrong?
Date: Mon, 14 Oct 2002 17:35:00 -0000 [thread overview]
Message-ID: <004d01c273e2$af2f48f0$0100a8c0@windows9q3yn19> (raw)
In-Reply-To: <20021015002144.GA35401@stack.nl>
Sounds like you might need a smaller C library then. Check out newlib or
some other library and see if that fits your problem. I'm not that familiar
with shrinking the C library. =)
http://sources.redhat.com/newlib/
--josh
----- Original Message -----
From: "Michiel Buddingh'" <ajuin+mail@stack.nl>
To: <gcc-help@gcc.gnu.org>
Sent: Monday, October 14, 2002 8:21 PM
Subject: Re: Giant executables.. what am I doing wrong?
> On Mon, Oct 14, 2002 at 08:08:06PM -0400, Joshua Nye wrote:
> > Are you sure you want to create a static executable?
>
> Yes. :)
>
> > If you are trying to
> > save memory, shared executables are probably better.
>
> True. But the system I'm programming for is going to be severely
> limited in memory. Limited to 4 MB of RAM, to be exact. It is not
> going to have virtual memory, and disk space will be less than 1 MB.
> Furthermore, I expect it's perfectly feasible to implement the
> program I'm writing using system calls only. Given that, it doesn't
> make sense to build it as a shared executable.
>
> --
> -- Michiel
>
next prev parent reply other threads:[~2002-10-15 0:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-14 16:49 Michiel Buddingh'
2002-10-14 17:08 ` Joshua Nye
2002-10-14 17:21 ` Michiel Buddingh'
2002-10-14 17:35 ` Joshua Nye [this message]
2002-10-14 18:50 ` Michiel Buddingh'
2002-10-15 2:38 ` Claudio Bley
2002-10-15 5:15 ` Michiel Buddingh'
2002-10-15 5:12 ` Joshua Nye
2002-10-15 5:19 ` Joshua Nye
2002-10-15 5:20 ` Michiel Buddingh'
2002-10-15 3:53 ` Steve Dondley
2002-10-15 4:15 ` Claudio Bley
2002-10-15 5:09 ` Michiel Buddingh'
2002-10-14 19:00 Dockeen
2002-10-15 5:31 Ruppert
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='004d01c273e2$af2f48f0$0100a8c0@windows9q3yn19' \
--to=josh@boxcarmedia.com \
--cc=ajuin+mail@stack.nl \
--cc=gcc-help@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).