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] glibc: ARC is now supported via patches
Date: Fri, 15 Dec 2017 09:41:31 +0000	[thread overview]
Message-ID: <1513330890.29404.17.camel@synopsys.com> (raw)
In-Reply-To: <20171109215821.16615-1-abrodkin@synopsys.com>

Hello,

On Fri, 2017-11-10 at 00:58 +0300, Alexey Brodkin wrote:
> Given ARC port is just a very few patches away from upstream
> and if those are based on 2.29 everything works like a charm
> let's forget about SNPS GitHub stuff and use vanilla glibc
> plus patches.
> 
> This among other things solves a problem with stable fixes for glibc.
> Now when Buildroot switched to the tip of glibc's stable branch instead of
> applying cherry-picked patches ARC version would stay behind every time
> glibc's "version" gets updated in Buildroot.
> 
> But if we just apply ARC patches then we're good with whatever commit
> from upstream stable branch is taken.
> 
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Cc: Peter Korsgaard <peter@korsgaard.com>

Any comments on this one?

Otherwise any chance to get it applied (not sure though if it
gets applied now and then builds)?

-Alexey

  reply	other threads:[~2017-12-15  9:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-09 21:58 [Buildroot] [PATCH] glibc: ARC is now supported via patches Alexey Brodkin
2017-12-15  9:41 ` Alexey Brodkin [this message]
2018-01-01 11:39 ` Thomas Petazzoni
2018-01-09 14:00   ` Alexey Brodkin
2018-01-09 14:50     ` Thomas Petazzoni
2018-01-09 15:03       ` Alexey Brodkin
2018-01-09 15:05         ` Thomas Petazzoni
2018-01-09 19:23       ` Vineet Gupta

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=1513330890.29404.17.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