linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: James Don <JDon@spacebridge.com>
Cc: "'linuxppc embedded'" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: SELF: ramdisk which required libraries if ...?
Date: Sat, 11 Jan 2003 21:18:43 +0100	[thread overview]
Message-ID: <20030111201848.9E383C6559@atlas.denx.de> (raw)
In-Reply-To: Your message of "Sat, 11 Jan 2003 14:47:50 EST." <DB0585C9F6F9D411BE8F00D0B7896A4CC0602F@SNCMAIL>


Dear Jim,

in message <DB0585C9F6F9D411BE8F00D0B7896A4CC0602F@SNCMAIL> you wrote:
>
> I am wondering what libraries are required if you compile with uclibc that
> has shared libraries compiled out ...
> Do I need some, none, or all?

I'm afraid you will have to try this out yourself.

> To make my life easy here is a list of libraries ... which would I need ?

Making your life  easy  and  saving  memory  footprint  by  compiling
against uclibc are two ends of the scale.

Basicly you have three options:

* Use the SELF that comes  with  our  ELDK,  and  the  commands  from
  SELF.spec to build it yourself.

  This gives you most of "making your life easy" as it  will  include
  only such tools and libraries that are already present in the ELDK,
  i.  e.  there  is  no  compilation  eeded  at all, and since we use
  "genext2fs" to build the ramdisk image  you  don't  need  any  root
  permissions.

  You will pay for this comfort by the memory footprint:  we  include
  standard tools like login with PAM support, xinetd, etc.

  On the other hand, this also gives you extended  functionality  and
  security.

* Use the SELF from our FTP server.

  Here you will have to spend much more work, as  you  will  need  to
  download a couple of packages, and the Makefile will compile every-
  thing that goes into the ramdisk image fresh from scratch.

  You benefit from this  additional  work  with  a  somewhat  smaller
  memory footprint.

* Modify SELF to build against ulibc.

  This is where you give up "making your life easy" and  go  for  low
  memory footprint. I'm looking forward to receiving your patches :-)


Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Heavier than air flying machines are impossible.
                    -- Lord Kelvin, President, Royal Society, c. 1895

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

  reply	other threads:[~2003-01-11 20:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-11 19:47 SELF: ramdisk which required libraries if ...? James Don
2003-01-11 20:18 ` Wolfgang Denk [this message]
     [not found] <DB0585C9F6F9D411BE8F00D0B7896A4CC06030@SNCMAIL>
2003-01-11 21:03 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2003-01-12  0:57 James Don

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=20030111201848.9E383C6559@atlas.denx.de \
    --to=wd@denx.de \
    --cc=JDon@spacebridge.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).