You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Chris Richardson <cr...@fourc.eu> on 2017/01/17 18:35:50 UTC
qpid-cpp-1.36.0 build error with nss-3.28
Hi all,
A new build error has cropped up building qpid-cpp-1.36.0 on Gentoo since
the distro's upgrade to nss-3.28. The issue will filter through to other
less bleeding-edge distros when they catch up!
[ 25%] Building CXX object src/CMakeFiles/qpidcommon.dir/qpid/Modules.cpp.o
In file included from /usr/include/nss/ssl.h:18:0,
from
/var/tmp/portage/net-misc/qpid-cpp-1.36.0/work/qpid-cpp-1.36.0/src/qpid/sys/ssl/util.cpp:30:
/usr/include/nss/sslt.h:121:40: error: comma at end of enumerator list
[-Werror=pedantic]
ssl_sig_rsa_pkcs1_sha1md5 = 0x10101,
^
cc1plus: all warnings being treated as errors
Technically the fault here is in the nss lib, but I'd like to request 2
changes in qpid to ease the issue, if I could...
Firstly, CMake has a SYSTEM clause to the include_directories statement
(see https://cmake.org/cmake/help/v3.0/command/include_directories.html)
which causes some compilers not to apply strict warnings to the files in
the directories following said clause. Could this be used with the NSS
includes, and perhaps with the Cyrus SASL includes also? Other included
headers throughout qpid-cpp are either from libraries which should know
better (bindings languages and boost) or other qpid libs. I've attached a
short patch which does this.
The second change I'd like to suggest is to add a CMake switch to control
the application of solely the -Werror flag in addition to the more broadly
applied ENABLE_WARNINGS option already present, which switches off
additional compiler warnings altogether. Naturally the default should be
that -Werror is applied. This would be in keeping with the packaging
guidelines for Gentoo (
https://devmanual.gentoo.org/ebuild-writing/common-mistakes/), specifically
the section "-Werror compiler flag not removed". I don't have a more
authoritative citation for how -Werror should be enforced but their
suggestion seems reasonable to me.
Regards
--
*Chris Richardson*, System Architect
cr@fourc.eu
*FourC AS, Vestre Rosten 81, Trekanten, NO-7075 Tiller, Norwaywww.fourc.eu
<http://www.fourc.eu/>*
*Follow us on LinkedIn <http://bit.ly/fourcli>, Facebook
<http://bit.ly/fourcfb>, Google+ <http://bit.ly/fourcgp> and Twitter
<http://bit.ly/fourctw>!*
Re: qpid-cpp-1.36.0 build error with nss-3.28
Posted by Chris Richardson <cr...@fourc.eu>.
On 18 January 2017 at 10:24, Gordon Sim <gs...@redhat.com> wrote:
> On 17/01/17 18:35, Chris Richardson wrote:
>
>> I'd like to request 2 changes in qpid to ease the issue, if I could...
>>
>
> Could you create a JIRA (or perhaps two of them) and attach the patches to
> those? Thanks!
>
Done!
https://issues.apache.org/jira/browse/QPID-7629
https://issues.apache.org/jira/browse/QPID-7630
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
--
*Chris Richardson*, System Architect
cr@fourc.eu
*FourC AS, Vestre Rosten 81, Trekanten, NO-7075 Tiller, Norwaywww.fourc.eu
<http://www.fourc.eu/>*
*Follow us on LinkedIn <http://bit.ly/fourcli>, Facebook
<http://bit.ly/fourcfb>, Google+ <http://bit.ly/fourcgp> and Twitter
<http://bit.ly/fourctw>!*
Re: qpid-cpp-1.36.0 build error with nss-3.28
Posted by Gordon Sim <gs...@redhat.com>.
On 17/01/17 18:35, Chris Richardson wrote:
> I'd like to request 2 changes in qpid to ease the issue, if I could...
Could you create a JIRA (or perhaps two of them) and attach the patches
to those? Thanks!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org