All of lore.kernel.org
 help / color / mirror / Atom feed
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:42:49 +0100	[thread overview]
Message-ID: <20091106104249.55983beb@surf> (raw)
In-Reply-To: <op.u2ytxehoyqa4qb@jap-lappis.nevion.com>

Le Fri, 6 Nov 2009 09:59:28 +0100,
Joachim Pihl <jpihl@nevion.com> a ?crit :

> Thanks for clearing that up! I found glib_genmarshal in /usr/bin, but
> I have absolutely no idea of why it has been included. There is no
> package I can find that mentions it. Also, this does not explain the
> duplicate libstdc++ libraries.

Ok, here is the full list of packages you selected:

BR2_PACKAGE_GDB_SERVER=y
BR2_PACKAGE_GDB_HOST=y
BR2_PACKAGE_BUSYBOX=y
BR2_PACKAGE_BUSYBOX_FULLINSTALL=y
BR2_PACKAGE_BUSYBOX_CONFIG="busybox.config"
BR2_PACKAGE_GETTEXT=y
BR2_PACKAGE_GETTEXT_STATIC=y
BR2_PACKAGE_LIBINTL=y
BR2_PACKAGE_PKG_CONFIG=y
BR2_PACKAGE_READLINE=y
BR2_PACKAGE_BOOST=y
BR2_PACKAGE_BOOST_CONFIG_THREADING=y
BR2_PACKAGE_BOOST_DATE_TIME=y
BR2_PACKAGE_BOOST_THREAD=y
BR2_PACKAGE_LIBICONV=y
BR2_PACKAGE_LIBNW=y
BR2_PACKAGE_LIBSNMPPDU=y
BR2_PACKAGE_SPREAD=y
BR2_PACKAGE_SQLITE=y
BR2_PACKAGE_NETSNMP=y
BR2_PACKAGE_NTP=y
BR2_PACKAGE_THTTPD=y
BR2_PACKAGE_VSFTPD=y
BR2_PACKAGE_MTD=y
 [ Lots of MTD stuff ]
BR2_PACKAGE_NCURSES=y
BR2_PACKAGE_LIBGD=y
BR2_PACKAGE_LIBPNG=y
BR2_PACKAGE_LIBGLIB2=y
BR2_PACKAGE_LZO=y
BR2_PACKAGE_ZLIB=y
BR2_PACKAGE_LIBXML2=y

I think you don't need pkg-config on the target, so disable
BR2_PACKAGE_PKG_CONFIG. This should allow you to disable libglib2
(BR2_PACKAGE_LIBGLIB2), which in turn will allow you to disable gettext
(BR2_PACKAGE_GETTEXT), libintl (BR2_PACKAGE_LIBINTL), libiconv
(BR2_PACKAGE_LIBICONV).

Of course, this makes the assumption that your own internal
applications do not use libglib2.

Then, for the Boost packages, then don't exist in Buildroot, so we
can't say what dependencies they pull. Could you submit a patch to add
the Boost libraries into Buildroot ?

Finally, for the duplicated C++ library thing, could you put online
your rootfs.tar (after removing your internal applications if they are
sensitive) ?

Sincerly,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2009-11-06  9:42 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 [this message]
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=20091106104249.55983beb@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.