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: Tue, 9 Jan 2018 15:03:15 +0000	[thread overview]
Message-ID: <1515510195.3868.14.camel@synopsys.com> (raw)
In-Reply-To: <20180109155057.659c646b@windsurf>

Hi Thomas,

On Tue, 2018-01-09 at 15:50 +0100, Thomas Petazzoni wrote:
> Hello,
> 
> On Tue, 9 Jan 2018 14:00:15 +0000, Alexey Brodkin wrote:

[snip]

> I guess the easiest approach is to keep using your fork from Github.
> It's up to you to decide what is the glibc version you want to use in
> Buildroot, so if you want to move to something that is closer to what
> is being submitted to glibc upstream, then that's perfectly fine: we
> can take a patch changing the glibc package to use a new ARC glibc
> version from Github.
> 
> Is that OK for you ?

Sure. Again I'm mostly concerned about things that will be fixed in
glibc's "stable" branch but still affecting our fork. But I'm sure we'll be able to
resolve it if it ever happens at all.

-Alexey

  reply	other threads:[~2018-01-09 15:03 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
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 [this message]
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=1515510195.3868.14.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