All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Fischer <fischer@4g-systems.com>
To: openembedded-devel@lists.openembedded.org
Subject: striping some libs and modules
Date: Fri, 19 Jan 2007 17:21:56 +0100	[thread overview]
Message-ID: <45B0F024.7060402@4g-systems.com> (raw)

Hello
I would like to discuss about striping some libs and modules.

I know i can't stip everything like object symbols,
but here is my stip suggestion:

mipsel-linux-strip -g -S -d --strip-debug $FILES
mipsel-linux-strip --remove-section=.comment --remove-section=.note 
--strip-unneeded $FILES

It will remove all debug, comment, note and unnedded code.


First of all there is the libstdc++

#ls -l tmp/rootfs/usr/lib/libstdc++.so.5.0.6
-rwxr-xr-x 1 pf pf 4636996 Jan 19 16:41 
tmp/rootfs/usr/lib/libstdc++.so.5.0.6
#mipsel-linux-strip -g -S -d --strip-debug tmp/rootfs/usr/lib/libstdc++.so.5
#ls -l tmp/rootfs/usr/lib/libstdc++.so.5.0.6
-rwxr-xr-x 1 pf pf 1249844 Jan 19 16:41 
tmp/rootfs/usr/lib/libstdc++.so.5.0.6
#mipsel-linux-strip --remove-section=.comment --remove-section=.note 
--strip-unneeded tmp/rootfs/usr/lib/libstdc++.so.5.0.6
#ls -l tmp/rootfs/usr/lib/libstdc++.so.5.0.6
-rwxr-xr-x 1 pf pf 1029184 Jan 19 16:41 
tmp/rootfs/usr/lib/libstdc++.so.5.0.6

it was 4636996 byte, after striping it is only  1029184 byte

This is very much!
Can any body tell my why i shouldn't do this?

There are a log of libs and modules which are not stiped.
Go to your rootfs and call this line to see which files are not stiped:
find . -exec file '{}' \; | grep "not stripped"

I think there is potential. I have tested it quickly. Works fine until now.

Best regards
Patrick Fischer




                 reply	other threads:[~2007-01-19 16:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=45B0F024.7060402@4g-systems.com \
    --to=fischer@4g-systems.com \
    --cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.