From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Simple glibc-based external toolchain support
Date: Wed, 15 Apr 2009 16:23:19 +0200 [thread overview]
Message-ID: <20090415162319.757eadd8@surf> (raw)
In-Reply-To: <87zleivwbi.fsf@macbook.be.48ers.dk>
Le Wed, 15 Apr 2009 16:13:53 +0200,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :
> I don't have a use for it myself, but I don't have a problem with it
> getting added (as long as someone is willing to supports its
> users).
Ok, thanks. My approach has one drawback: when one selects uClibc, the
Kconfig system picks up the default uClibc values for
BR2_TOOLCHAIN_EXTERNAL_LIB_C and BR2_TOOLCHAIN_EXTERNAL_LIBS. If the
user then later changes to glibc, then Kconfig doesn't change the
BR2_TOOLCHAIN_EXTERNAL_LIB_C and BR2_TOOLCHAIN_EXTERNAL_LIBS : they are
kept to their uClibc defaults. That may confuse users.
This raises the following point: do we need these options at all ?
Can't we just hardcode in ext-took.mk the list of libraries that have
to be imported in the target, depending on the choosen C library ?
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-04-15 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 20:12 [Buildroot] Simple glibc-based external toolchain support Thomas Petazzoni
2009-04-15 14:03 ` Thomas Petazzoni
2009-04-15 14:13 ` Peter Korsgaard
2009-04-15 14:23 ` Thomas Petazzoni [this message]
2009-04-15 14:38 ` 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=20090415162319.757eadd8@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox