From: dony <dony.he@huawei.com.cn>
To: crossgcc@sourceware.cygnus.com,
linuxppc-embed <linuxppc-embedded@lists.linuxppc.org>
Subject: Reduce glibc libraries...
Date: Wed, 01 Mar 2000 11:31:49 +0800 [thread overview]
Message-ID: <38BC8F25.7CDC484@huawei.com.cn> (raw)
Hello,
I have a problem to ask when applying embed-linux in our product.
Since our application may need many share libraries when running,
and most of these libraries seem to be too large: libc.so.6 is about
1.5M, and the ld.so.1 is about 180K, and there are still other
libraries...
If I put the linux kernel and root-fs in my flash(about 2M), I am
fear that there may be no enough space to hold all of them. So do I have
to modify and remove any unuseful sources from the glibc libraries to
reduce the size of libraries I need? But it is too difficult. So what's
your suggestions or alternative methods ? Does it make any difference
if I compile my application with static-link options "-s"? Are there
someone to do these jobs now?
Thank you very much:-)
dony
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2000-03-01 3:31 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=38BC8F25.7CDC484@huawei.com.cn \
--to=dony.he@huawei.com.cn \
--cc=crossgcc@sourceware.cygnus.com \
--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).