Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] Upgrading from Buildroot 0.10 to 2009.08 (ARM)
Date: Fri, 06 Nov 2009 09:52:16 +0100	[thread overview]
Message-ID: <1257497536.1962.15.camel@bender> (raw)
In-Reply-To: <op.u2yqk2doyqa4qb@jap-lappis.nevion.com>

On Fri, 2009-11-06 at 08:47 +0100, Joachim Pihl wrote:

> I had a look in the archives, but did not find any recent information that  
> seems to cover the problems I am experiencing.
> 
> About 18 months ago, we had our target build system configured by a  
> consultant. This is an Xscale target. We made the root FS fit in the  
> allotted space, just fine. Preparing to add a new controller card to our  
> product range, I decided to download a fresh Buildroot, then configure to  
> match the old setup (which has issues building on Ubuntu 9.04 or later,  
> possibly due to some package we have added). Busybox and uclibc config  
> files are copied from the previous buildroot environment.
> 
> As it turns out, the rootfs of this configuration is several MBs larger  
> than the previous one, mainly due to an explosion of shared libraries.
> 
> /usr/lib has a lot of glib*.so files that were not previously there, and  
> also iconv has been added. In addition, both libstd++.so.6.0.9 and  
> libstd++.so.6.0.10 are added. /usr/lib is now twice the size of that of  
> the previous target, meaning it won't fit on the target anymore. I believe  
> glib* are parts of GLIBC, how come it is installed when I am trying to  
> build a uclibc system?

glib is http://library.gnome.org/devel/glib/stable/glib.html and should
not be confused with glibc.

I assume that some package you selected pulled in libglib2, which itself
pulls in other things like iconv. Just check your package selection and
make sure that you only select the packages you absolutely need.


Sven

  reply	other threads:[~2009-11-06  8:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-06  7:47 [Buildroot] Upgrading from Buildroot 0.10 to 2009.08 (ARM) Joachim Pihl
2009-11-06  8:52 ` Sven Neumann [this message]
2009-11-06  8:59   ` Joachim Pihl
2009-11-06  9:02     ` Sven Neumann
2009-11-06  9:03       ` Joachim Pihl
2009-11-06  9:42     ` Thomas Petazzoni
2009-11-06  9:54       ` Joachim Pihl
2009-11-07 10:08         ` Peter Korsgaard
2009-11-06  9:04 ` Thomas Petazzoni
2009-11-06  9:26   ` Joachim Pihl
2009-11-06  9:53     ` Thomas Petazzoni
2009-11-06 12:16       ` Joachim Pihl
2009-11-06 12:28         ` Joachim Pihl
2009-11-06 12:48           ` Joachim Pihl
2009-11-06 13:02             ` Joachim Pihl
2009-11-07 10:10         ` Peter Korsgaard
2009-11-07 10:24           ` Joachim Pihl
2009-11-08 21:50             ` Peter Korsgaard

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=1257497536.1962.15.camel@bender \
    --to=s.neumann@raumfeld.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