<feed xmlns='http://www.w3.org/2005/Atom'>
<title>buildroot/package/jsoncpp/0001-Remove-Werror.patch, branch 2016.02</title>
<subtitle>OpenPOWER buildroot sources</subtitle>
<id>https://git.raptorcs.com/git/buildroot/atom?h=2016.02</id>
<link rel='self' href='https://git.raptorcs.com/git/buildroot/atom?h=2016.02'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/'/>
<updated>2015-08-19T09:05:49+00:00</updated>
<entry>
<title>package/jsoncpp: bump to version 1.6.5</title>
<updated>2015-08-19T09:05:49+00:00</updated>
<author>
<name>Jörg Krause</name>
<email>joerg.krause@embedded.rocks</email>
</author>
<published>2015-08-11T07:46:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=f9280fd9e9f9a4bb108327362559cccac6186b3b'/>
<id>urn:sha1:f9280fd9e9f9a4bb108327362559cccac6186b3b</id>
<content type='text'>
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 &gt;= 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 &lt;baruch@tkos.co.il&gt;
Cc: Bernd Kuhls &lt;bernd.kuhls@t-online.de&gt;
Signed-off-by: Jörg Krause &lt;joerg.krause@embedded.rocks&gt;
Reviewed-by: Baruch Siach &lt;baruch@tkos.co.il&gt;
Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@free-electrons.com&gt;
</content>
</entry>
</feed>
