Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] add basic support for uClibc-ng
Date: Tue, 10 Feb 2015 18:25:55 +0100	[thread overview]
Message-ID: <20150210172555.GE22344@waldemar-brodkorb.de> (raw)
In-Reply-To: <20150209205338.604f740e@free-electrons.com>

Hi Thomas,
Thomas Petazzoni wrote,

> Dear Waldemar Brodkorb,
> 
> On Mon, 9 Feb 2015 19:16:37 +0100, Waldemar Brodkorb wrote:
> 
> > +config BR2_TOOLCHAIN_BUILDROOT_UCLIBC_NG
> > +	bool "uClibc-ng"
> > +	select BR2_TOOLCHAIN_USES_UCLIBC
> > +	depends on BR2_arcle   || BR2_arceb  || BR2_arm    || BR2_armeb    || \
> > +		   BR2_avr32   || BR2_bfin   || BR2_i386   || BR2_m68k     || \
> > +		   BR2_mips    || BR2_mipsel || BR2_mips64 || BR2_mips64el || \
> > +		   BR2_powerpc || BR2_sh     || BR2_sparc  || BR2_xtensa   || \
> > +		   BR2_x86_64
> > +	help
> > +	  This option selects uClibc-ng as the C library for the
> > +	  cross-compilation toolchain.
> > +
> > +	  http://uclibc-ng.org
> > +
> 
> I don't think introducing this symbol is needed. Instead, we can just
> make uClibc-ng another version of uClibc. Like the following (untested) :

I thought about this in my first try, but I have following problem:
When you choose uClibc-ng 1.0.0 instead of uClibc, the default
config string is _not_ automatically changed.

How could this be done?

best regards
 Waldemar

  reply	other threads:[~2015-02-10 17:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-09 18:16 [Buildroot] [PATCH] add basic support for uClibc-ng Waldemar Brodkorb
2015-02-09 19:53 ` Thomas Petazzoni
2015-02-10 17:25   ` Waldemar Brodkorb [this message]
2015-02-11  6:10     ` Thomas Petazzoni
2015-02-11  9:26       ` Waldemar Brodkorb
2015-02-11 13:17         ` Thomas Petazzoni
2015-02-11  9:35   ` Thomas De Schampheleire

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=20150210172555.GE22344@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --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