Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas <tokant@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] AT91RM9200df, some applications depend on libintl/libiconv
Date: Wed, 04 Mar 2009 00:28:29 +0100	[thread overview]
Message-ID: <1236122909.5689.22.camel@bernd-desktop> (raw)

Hello,

I am trying to create a "light" root file system for an AT91RM9200df
system with the latest 2009.02 buildroot release. So I disabled a lot of
the packages and libraries (for example libintl and libiconv) and got a
partly working root file system.

Some of the package applications do not work, because they seem to
depend on libintl/libiconv: wget, chattr, lsattr uuidgen, e2fsck, mke2fs
and badblocks for example. They terminate with "can't load library
'libintl.so.8'". These applications work, if I enable libintl and
libiconv, but I would like to save the 800 kB which where occupied by
libiconv.

Is this by design now, or did I configure something wrong, or is this a
buildroot problem? 

Thanks, Thomas.

             reply	other threads:[~2009-03-03 23:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 23:28 Thomas [this message]
2009-03-05 13:57 ` [Buildroot] AT91RM9200df, some applications depend on libintl/libiconv Peter Korsgaard
2009-03-09 20:56   ` Thomas

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=1236122909.5689.22.camel@bernd-desktop \
    --to=tokant@gmx.net \
    --cc=buildroot@busybox.net \
    /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