Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] big root fs
Date: Wed, 12 Sep 2012 18:19:01 +0200	[thread overview]
Message-ID: <5050B5F5.6080305@mind.be> (raw)
In-Reply-To: <20120912102727.46894561@skate>

On 09/12/12 10:27, Thomas Petazzoni wrote:
> Le Wed, 12 Sep 2012 01:21:03 -0700 (PDT),
> Zoran Djordjevic<djdjdjole@yahoo.com>  a ?crit :
>
>> It is hard to send output/target folder, because it is about 100MB uncompressed.
>> Maybe someone will have suggestion, according to next size info:
>> The biggest folder inside "target" is /lib(20MB) and  /usr - 86MB (/usr/lib -20MB ; /usr/share - 60).
>> Inside /usr/share - the most parts go to folders: locale (35MB);
  The large /lib is indicative of a linux kernel config with too many modules.
Probably because you use a defconfig.  Do:
  make linux-menuconfig
and get rid of the modules you don't need.
Then, change your buildroot configuration to use a custom config instead of
a defconfig, and do
  make linux-update-defconfig
to save the custom config.

  Don't forget to wipe output/target/lib/modules before rebuilding,
or the old modules will just stay there...

> Enable option BR2_ENABLE_LOCALE_PURGE. And you can probably set
> BR2_ENABLE_LOCALE_WHITELIST to just "C en_US". This should get rid of
> most of your usr/share/locale directory.
>
> I'm wondering whether we should make BR2_ENABLE_LOCALE_PURGE=y and
> BR2_ENABLE_LOCALE_WHITELIST="C en_US" the defaults.

  Yes!

>> fonts(20MB) and X11(5MB).
  fonts seems a bit on the large side.  Check which font packages you have
selected.
>> I can send some of them although I am aware that info I provided is not so clear.
> Can you send the output of:
>
> 	cd output/target/
> 	ls -lRS
  Make that ls -lRSh (so we get size in MB instead of bytes).


  Regards,
  Arnout

-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2012-09-12 16:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-11 12:29 [Buildroot] big root fs Zoran Djordjevic
2012-09-11 13:17 ` Peter Korsgaard
2012-09-11 13:43   ` Zoran Djordjevic
2012-09-11 13:44 ` Thomas Petazzoni
2012-09-12  5:32   ` Zoran Djordjevic
2012-09-12  6:10     ` Avery Pennarun
2012-09-12  6:44     ` Thomas Petazzoni
2012-09-12  7:26       ` Zoran Djordjevic
2012-09-12  8:21       ` Zoran Djordjevic
2012-09-12  8:27         ` Thomas Petazzoni
2012-09-12 16:19           ` Arnout Vandecappelle [this message]
2012-09-13  6:25           ` Zoran Djordjevic

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=5050B5F5.6080305@mind.be \
    --to=arnout@mind.be \
    --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