From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] glibc: ARC is now supported via patches
Date: Mon, 1 Jan 2018 12:39:36 +0100 [thread overview]
Message-ID: <20180101123936.609b7f41@windsurf> (raw)
In-Reply-To: <20171109215821.16615-1-abrodkin@synopsys.com>
Hello,
On Fri, 10 Nov 2017 00:58:21 +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>
> ---
> package/glibc/0001-longlong.h-sync-from-gcc.patch | 133 +
> .../0002-ARC-add-definitions-to-elf-elf.h.patch | 94 +
> package/glibc/0003-ARC-Initial-port-to-glibc.patch | 7625 ++++++++++++++++++++
This is a bit too much feature patches IMO, it's a complete
architecture port. I agree it's a backport from upstream, so it's not
too bad. But since glibc 2.27, which includes this, is expected to be
released on February 1st, I prefer to post-pone this change until glibc
2.27 gets released and we move to it.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2018-01-01 11:39 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 [this message]
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=20180101123936.609b7f41@windsurf \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.