From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] boost: bump to version 1.63.0
Date: Fri, 10 Mar 2017 22:22:40 +0100 [thread overview]
Message-ID: <20170310222240.3f70bc41@free-electrons.com> (raw)
In-Reply-To: <20170310201512.12260-1-joerg.krause@embedded.rocks>
Hello,
On Fri, 10 Mar 2017 21:15:12 +0100, J?rg Krause wrote:
> Remove getchar() patch which has been applied upstream.
>
> Add recommanded post-release patch from upstream to fix 64-bit atomic
> operations on 32-bit x86 with gcc versions older than 4.7.
>
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> ---
> ...ted-register-usage-in-x86-DCAS-asm-blocks.patch | 65 ++++++++++++++++++++++
> ...fix-getchar-with-uclibc-and-gcc-bug-58952.patch | 45 ---------------
> package/boost/boost.hash | 5 +-
> package/boost/boost.mk | 2 +-
> 4 files changed, 68 insertions(+), 49 deletions(-)
> create mode 100644 package/boost/0004-Corrected-register-usage-in-x86-DCAS-asm-blocks.patch
> delete mode 100644 package/boost/0004-fix-getchar-with-uclibc-and-gcc-bug-58952.patch
Applied to master, thanks. Since Boost is a package that often causes
some build issues in other packages when it's upgraded, it would be
good if you could keep an eye on the autobuilders in the next few days,
and see if there's anything boost related.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-03-10 21:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 20:15 [Buildroot] [PATCH] boost: bump to version 1.63.0 Jörg Krause
2017-03-10 21:22 ` Thomas Petazzoni [this message]
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=20170310222240.3f70bc41@free-electrons.com \
--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