Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] toolchain/uclibc-ng: add support for uClibc-ng
Date: Thu, 28 Aug 2014 09:39:25 +0200	[thread overview]
Message-ID: <20140828093925.6bbffb1b@free-electrons.com> (raw)
In-Reply-To: <53FE6512.9050600@mind.be>

Dear Arnout Vandecappelle,

On Thu, 28 Aug 2014 01:09:06 +0200, Arnout Vandecappelle wrote:

>  What a surprising lack of reaction on this patch! I'd have expected people to
> welcome this very much...

Yes, sorry for the lack of reaction. I definitely welcome this very
much!

>  However, I'll start with immediately burning it to the ground :-) I think the
> situation of uClibc-ng is very similar to eglibc: it's essentially the same
> package, just a different version of it. So, instead of creating a whole new
> copy, I think it's easier to maintain if it is one more uclibc version in
> package/uclibc/Config.in.

I definitely agree. For now, uclibc-ng build system and process is
essentially the same as the one of uclibc, so I'd prefer to see it
being handled by package/uclibc/.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      parent reply	other threads:[~2014-08-28  7:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-11 11:31 [Buildroot] [PATCH 1/2] toolchain/uclibc-ng: add support for uClibc-ng Waldemar Brodkorb
2014-08-27 23:09 ` Arnout Vandecappelle
2014-08-28  7:08   ` Waldemar Brodkorb
2014-08-28  7:28     ` Thomas De Schampheleire
2014-08-28  8:33       ` Waldemar Brodkorb
2014-08-28  7:39   ` Thomas Petazzoni [this message]

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=20140828093925.6bbffb1b@free-electrons.com \
    --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