public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
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: Tue, 15 Oct 2002 05:12:00 -0000	[thread overview]
Message-ID: <004b01c27444$18093550$c800a8c0@pdc1.boxcarmedia.com> (raw)
In-Reply-To: <20021015014958.GA36140@stack.nl>

If you run 'nm' on your pre-stripped executable you will see all the
compiled in functions from the C library and any other libraries. When you
do a static compile it doesn't just include only the needed function(s), but
the entire C library .a file. That's why I recommended going with a smaller
or more base-functionality C library such as newlib.

--josh

----- Original Message -----
From: "Michiel Buddingh'" <ajuin+mail@stack.nl>
To: <gcc-help@gcc.gnu.org>
Sent: Monday, October 14, 2002 9:49 PM
Subject: Re: Giant executables.. what am I doing wrong?


> On Mon, Oct 14, 2002 at 08:34:55PM -0400, Joshua Nye wrote:
> > 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. =)
>
> Although newlib does look interesting, I doubt the problem lies
> with the C library. Unless I'm mistaken, system calls should have
> little to do with the C library, as the program calls the kernel
> directly.
> This supports my suspicion that gcc is linking in a lot of stuff
> I could do without.
> --
> -- Michiel
>


  parent reply	other threads:[~2002-10-15 12:12 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
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 [this message]
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='004b01c27444$18093550$c800a8c0@pdc1.boxcarmedia.com' \
    --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).