Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph G. Boike <joe.boike@acsatlanta.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot size ballooned
Date: Thu, 17 Jul 2008 13:40:15 -0500	[thread overview]
Message-ID: <487F920F.7040706@acsatlanta.com> (raw)
In-Reply-To: <d6cda7730807161150u3c5589d6ld94ca37dfef26c27@mail.gmail.com>

I had thought about that and have tried removing packages but haven't 
found the source of the largess yet.
Is there an easy way to find out the sizes of parts of the final image 
to see if something looks out of line?
(I don't think I have the same problem that Chien-Yu Chen referenced, 
since my buildroot and kernel images are not increasing in size with 
each build.)
Regards,
Joe

Thiago A. Corr?a wrote:
> Most likely there are new packages being enabled on the defconfig. Did
> you check that?
>
> On Wed, Jul 16, 2008 at 12:31 PM, Joseph G. Boike
> <joe.boike@acsatlanta.com> wrote:
>   
>>> Date: Tue, 15 Jul 2008 21:52:10 -0600
>>> From: "Nathanael D. Noblet" <nathanael@gnat.ca>
>>> Subject: Re: [Buildroot] buildroot size ballooned
>>> To: "Joseph G. Boike" <joe.boike@acsatlanta.com>
>>> Cc: build root <buildroot@uclibc.org>
>>> Message-ID: <487D706A.30908@gnat.ca>
>>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>>
>>> Joseph G. Boike wrote:
>>>
>>>       
>>>> Hi, my buildroot filesize had been around 3-4M (w/ r 22508)
>>>> With r 225765 and building using at91sam9260dfc_defconfig the filesize
>>>> has jumped to ~14M.
>>>> Any thoughts on why?
>>>> (I have kernel 2.6.26 now.  The kernel size has been fairly consistent
>>>> around 1.5M.)
>>>>
>>>>         
>>> No idea, but a clarification, are you talking about buildroot's
>>> outputted final rootfs, or buildroot project in svn?
>>>
>>>
>>>       
>> The final output file (rootfs.arm-2008xxxx.ext2.gz) to be burned into my
>> serial flash.
>> Regards,
>> Joe
>> _______________________________________________
>> buildroot mailing list
>> buildroot at uclibc.org
>> http://busybox.net/mailman/listinfo/buildroot
>>
>>     

  parent reply	other threads:[~2008-07-17 18:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.29.1216219095.1344.buildroot@uclibc.org>
2008-07-16 15:31 ` [Buildroot] buildroot size ballooned Joseph G. Boike
2008-07-16 18:50   ` Thiago A. Corrêa
2008-07-16 19:01     ` Chien-Yu Chen
2008-07-17 18:40     ` Joseph G. Boike [this message]
2008-07-16  3:36 Joseph G. Boike
2008-07-16  3:52 ` Nathanael D. Noblet

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=487F920F.7040706@acsatlanta.com \
    --to=joe.boike@acsatlanta.com \
    --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