From: Martin Hicks <mort@bork.org>
To: ARIBAUD Albert <a.aribaud@giat-industries.fr>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Embedded initrd with static programs
Date: Tue, 23 Dec 2003 11:35:55 -0500 [thread overview]
Message-ID: <20031223163555.GE702@localhost> (raw)
In-Reply-To: <158EF4B20EA8C84D9DC71A55216D2E1C066C71@csy-exchange1.giat.intra>
On Tue, Dec 23, 2003 at 05:06:55PM +0100, ARIBAUD Albert wrote:
>
> > So basically I need the other two programs also statically
> > compiled, does anyone of any idea on how I would go about
> > this??
>
> Mybe I am missing something, but why not use the dynamically
> linked versions and include the necessary libraries in the
> initial ramdisk?
It really depends on how many apps you're including. If you only need
one app then copying all of glibc in is a waste. If you've got a bunch
of apps then it's probably better to copy on the shared libs.
On the other hand, if you can get all your apps to compile against
uClibc (or one of the other small libs replacements) then you'll be much
better off. glibc is huge.
mh
--
Martin Hicks || mort@bork.org || PGP/GnuPG: 0x4C7F2BEE
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-12-23 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 16:06 Embedded initrd with static programs ARIBAUD Albert
2003-12-23 16:35 ` Martin Hicks [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-23 16:46 Ashwin Bihari
2003-12-23 16:00 Ashwin Bihari
2003-12-23 15:04 Ashwin Bihari
2003-12-23 15:56 ` Wolfgang Denk
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=20031223163555.GE702@localhost \
--to=mort@bork.org \
--cc=a.aribaud@giat-industries.fr \
--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).