Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ARC: switch to RC1 of upcoming arc-2015.06 tools
Date: Mon, 29 Jun 2015 12:36:57 +0000	[thread overview]
Message-ID: <1435581416.30996.19.camel@synopsys.com> (raw)
In-Reply-To: <20150627092110.GI31780@waldemar-brodkorb.de>

Hi Waldemar,

On Sat, 2015-06-27 at 11:21 +0200, Waldemar Brodkorb wrote:
> Is there any reason uClibc-ng 1.0.3 can not be used as default?
> Do you have pending patches for ARC?

Even thought there's no strong preference for us between uClibc and
uClibc-ng the point is we've been using our GitHub uClibc repo (which
is now a "mirror" of uClibc's git with a bit of a lag in updates - we
do it manually from time to time) for all builds, i.e. we run
regression tests and use for building everything uClibc but not uClibc
-ng. And so we're pretty sure uClibc works for us.

I'm not saying that uClibc-ng is any worse, no. But for current release
cycle we'll claim support of "vanilla" uClibc.

But I believe it's a good time now to discuss a possibility to switch
to uClibc-ng for our following releases.

I'm explicitly adding Vineet in Cc who is our uClibc maintainer so he
may add his 2 cents in that discussion.

-Alexey

  reply	other threads:[~2015-06-29 12:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26 19:27 [Buildroot] [PATCH] ARC: switch to RC1 of upcoming arc-2015.06 tools Alexey Brodkin
2015-06-27  9:21 ` Waldemar Brodkorb
2015-06-29 12:36   ` Alexey Brodkin [this message]
2015-06-28 13:12 ` Thomas Petazzoni

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=1435581416.30996.19.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.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