From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/jsoncpp: bump to version 1.6.5
Date: Wed, 19 Aug 2015 11:20:52 +0200 [thread overview]
Message-ID: <20150819112052.7ddb8c55@free-electrons.com> (raw)
In-Reply-To: <1439279206-7180-1-git-send-email-joerg.krause@embedded.rocks>
Dear J?rg Krause,
On Tue, 11 Aug 2015 09:46:46 +0200, J?rg Krause wrote:
> Remove patch 0001-Revert-Use-std-namespace-for-snprintf.patch:
> This patch was initially intented to remove upstream commit
> 1c58876185d2a4ed87dac4a54b82f607e74f55fd to disable std::snprintf() for all
> compilers. However, the patch actually reverts upstream commit
> 240ddb6a1b7aae7c6528e328995812ee695a73af which only uses std namespace if the
> compiler defines __cplusplus >= 201103L, thus is a recent C++11 compiler.
>
> Furthermore, upstream commit fac87108a49fb1b2640eff5d8e4cc7a12723a510 adds
> the `-std=c++11` compiler flag to gcc, so jsoncpp now requires a C++11 compiler
> either way.
>
> With jsoncpp requiring a recent C++11 compiler we need at least gcc 4.7.
>
> Backport patch from upstream [1] to remove `-Werror` from the compiler flags to
> allow building with CS ARM toolchains.
>
> [1]
> https://github.com/open-source-parsers/jsoncpp/commit/d7b84f69c5e92178e110552cce27f900744e1779
>
> Cc: Baruch Siach <baruch@tkos.co.il>
> Cc: Bernd Kuhls <bernd.kuhls@t-online.de>
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
>
> ---
> Changes in v2:
> - Use the gcc version dependency mechanism
> - Update patch status (suggested by Baruch)
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-08-19 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 7:46 [Buildroot] [PATCH v2 1/1] package/jsoncpp: bump to version 1.6.5 Jörg Krause
2015-08-11 8:18 ` Baruch Siach
2015-08-19 9:20 ` 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=20150819112052.7ddb8c55@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