[
https://issues.apache.org/jira/browse/QPID-4734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13633033#comment-13633033
]
Justin Ross commented on QPID-4734:
-----------------------------------
Andrew requested this for 0.22. I've taken a look at the delta, and it's
correct wrt the gcc documentation for such pragmas. One question came to mind:
should we make the version less precise, instead targeting, say, 4.4? The
change is harmless, and it may help users with other minor versions of gcc.
> Release builds fail on GCC 4.4.7 / Boost 1.41
> ---------------------------------------------
>
> Key: QPID-4734
> URL: https://issues.apache.org/jira/browse/QPID-4734
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.21, 0.22, 0.23
> Environment: gcc 4.4.7 and boost 1.41 on RHEL 6
> Reporter: Andrew Stitcher
> Assignee: Andrew Stitcher
> Fix For: 0.23
>
>
> build fails with warnings turned to errors when compiling SocketTransport.cpp:
> These are potentially uninitialised variable warnings in boost::bind and
> boost::function templates and so the underlying code can't be changed by us.
> It appears that the cause here is either (or some combination):
> * The compiler's flow analysis is incorrect.
> * The compiler misinterprets the warning as being in the location that the
> template instantiation happened (our code) and so ignores the
> -Wno-system-headers flag which should stop it reporting warnings in the
> system headers.
> * There is an issue in the boost code.
> In any of these cases there is little that we can do except suppress the
> warning.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
