linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mark Hatle <fray@mvista.com>
To: Michael Habermann <MHabermann@gmx.de>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Reducing glibc with mklibs.sh
Date: Tue, 23 Oct 2001 21:21:47 -0500	[thread overview]
Message-ID: <3BD625BB.C6FDA0DA@mvista.com> (raw)
In-Reply-To: 5.1.0.14.0.20011024095739.02d78c50@pop.gmx.de


> >Note: I successfully reduced libpthread.so, also.
>
> How have you done the libthread? Standard compilation for glibc produces
> _pic only for libc on my system. My libm is still quite large.

I suggest you download the Hard Hat Linux (ftp.mvista.com) source rpm
for glibc.  I believe there is either a patch or a special "step" in the
%install section of the rpm spec file.

(It works for LOT, but is probably applicable to mklibs.sh)

--Mark

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

  reply	other threads:[~2001-10-24  2:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-18 13:07 Reducing glibc with mklibs.sh Jean-Denis Boyer
2001-10-24  2:04 ` Michael Habermann
2001-10-24  2:21   ` Mark Hatle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-08 16:44 Orlov, Leonid
2005-07-26 16:53 Orlov, Leonid
2001-10-29 22:36 Jean-Denis Boyer
2001-10-30  2:00 ` Michael Habermann
2001-10-24 14:16 Jean-Denis Boyer
2001-10-26  1:33 ` Michael Habermann
2001-10-17  8:03 Michael Habermann
2001-10-17 12:30 ` Wolfgang Denk
2001-10-17 16:28   ` Joe Green
2001-10-18  4:39     ` Michael Habermann
     [not found]       ` <01101808315200.14753@minotaur.mvista.com>
2001-10-19  0:04         ` Michael Habermann
2001-10-24  2:18         ` Michael Habermann
2001-10-26 17:48           ` Joe Green

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=3BD625BB.C6FDA0DA@mvista.com \
    --to=fray@mvista.com \
    --cc=MHabermann@gmx.de \
    --cc=linuxppc-embedded@lists.linuxppc.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 NNTP newsgroup(s).