From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Upgrading from Buildroot 0.10 to 2009.08 (ARM)
Date: Fri, 6 Nov 2009 10:04:59 +0100 [thread overview]
Message-ID: <20091106100459.2624b645@surf> (raw)
In-Reply-To: <op.u2yqk2doyqa4qb@jap-lappis.nevion.com>
Le Fri, 6 Nov 2009 08:47:16 +0100,
Joachim Pihl <jpihl@nevion.com> a ?crit :
> /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?
As Sven said, glib is a different thing than glibc. It's a foundation
library of the Gtk stack.
> If anyone would like to help investigate the problem, I can send my
> configuration files to you to see if you are able to recreate the
> behaviour.
Please send your .config to the list and describe what are the
dependencies of your own applications.
Sincerly,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2009-11-06 9:04 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
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 [this message]
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=20091106100459.2624b645@surf \
--to=thomas.petazzoni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.