linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mark Hatle <fray@mvista.com>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: glibc vs. newlib
Date: Tue, 08 Apr 2003 12:03:33 -0500	[thread overview]
Message-ID: <3E9300E5.6040102@mvista.com> (raw)
In-Reply-To: <3E92FABD.8050307@imc-berlin.de>


Steven Scholz wrote:
> Mark Hatle wrote:
>
>> ... So short answer, running a glibc "optimizer" which re-links the
>> original glibc
>> .o files is absolutly safe and supportable.. you just have to
>> understand what it
>> means and how it works to decide if it is right for your application.
>>
>
> Could you recommend one specific open source glibc "optimizer", please?
>
> Maybe even with a URL... :o)

Sorry I don't have an URL, but the one I know of at the top of my head is part
of Debian.  They use it to shrink the size of glibc for their install disks.
Check out "freshmeat.net", I know there are more then one of them out there.

--Mark


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      parent reply	other threads:[~2003-04-08 17:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-04 23:08 glibc vs. newlib Darin.Johnson
2003-04-04 23:19 ` Gary D. Thomas
2003-04-04 23:38 ` Wolfgang Denk
2003-04-05  1:30 ` Mark Hatle
2003-04-07  1:47   ` Erik Christiansen
2003-04-07  6:05     ` Mark Hatle
2003-04-08 16:36       ` Marius Groeger
2003-04-08 16:27         ` Mark Hatle
     [not found]           ` <3E92FABD.8050307@imc-berlin.de>
2003-04-08 17:03             ` Mark Hatle [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=3E9300E5.6040102@mvista.com \
    --to=fray@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=steven.scholz@imc-berlin.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).