From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] toolchain: Add glibc support for ARCv2
Date: Tue, 10 Oct 2017 23:17:55 +0200 [thread overview]
Message-ID: <20171010231755.110e806b@windsurf.lan> (raw)
In-Reply-To: <20171010133150.42030-1-didin@synopsys.com>
Hello,
Thanks, I've applied to master. One comment below.
On Tue, 10 Oct 2017 16:31:50 +0300, Evgeniy Didin wrote:
> Finally there's working ARC port of glibc thanks to Vineet and Cuper!
> This port is based on pretty recent glibc's master branch and ARC
> changes are being reviewed now in glibc's mailing list.
>
> Thus we again have to use sources from our GitHub but as soon as there's
> a glibc release with our patches applied we'll switch to upstream releases
> and will drop our glibc GitHub repo alltogether.
>
> Note now we cut tags in glibc repo simultaneously with tags
> in Binutils and GCC repos and so to make sure everything works in the best
> way we plan to update glibc tag together with Binutils and GCC.
>
> Also note as of today ARCompact (AKA ARCv1 ISA) is not supported in glibc
> but we plan to fix it soonish so for now we make glibc intentionally
> dependent on archs38.
>
> Also note we are not creating directory "2.26" because all patches for glibc
> ver 2.26 applies to arc glibc port.
This last thing will probably cause problems in the future: when we
will add new glibc patches, they may not work with the ARC version of
glibc, or when we bump to glibc 2.26.1, the ARC version of glibc will
probably not be rebased at exactly the same time.
So I've left it as-is for now, but I'm pretty sure we'll have to switch
to per-version directories very soon.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-10-10 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 13:31 [Buildroot] [PATCHv2] toolchain: Add glibc support for ARCv2 Evgeniy Didin
2017-10-10 14:15 ` Alexey Brodkin
2017-10-10 21:17 ` Thomas Petazzoni [this message]
2017-10-10 21:26 ` Arnout Vandecappelle
2017-10-11 6:55 ` Thomas Petazzoni
2017-10-11 16:05 ` Alexey Brodkin
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=20171010231755.110e806b@windsurf.lan \
--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