Opened 10 years ago

Closed 9 years ago

Last modified 9 years ago

#8066 closed Patches (fixed)

Conflict with Boost.Log on GCC 4.4

Reported by: Andrey Semashev Owned by: Hartmut Kaiser
Milestone: To Be Determined Component: spirit
Version: Boost 1.53.0 Severity: Problem
Keywords: Cc: spirit log attribute_value

Description

I have a problem with compiling Boost.Log v2 with Boost.Spirit with GCC 4.4. The compiler mistakenly confuses boost::spirit::detail::attribute_value function template declared in boost/spirit/home/support/algorithm/any_if.hpp with boost::log::attribute_value class in Boost.Log which results in the following errors:

./boost/log/attributes/attribute_value.hpp:64: error: ‘class boost::log::v2_mt_posix::attribute_value’ is not a function,
./boost/spirit/home/support/algorithm/any_if.hpp:159: error:   conflict with ‘template<class Pred, class Iterator1, class Last2, class Iterator2> typename boost::spirit::detail::result_of::attribute_value<Iterator1, Iterator2, Last2, Pred>::type boost::spirit::detail::attribute_value(const Iterator2&)’
./boost/spirit/home/support/algorithm/any_if.hpp:184: error:   in call to ‘attribute_value’

The problem can be resolved by qualifying the call to attribute_value function in any_if. Please, find the attached patch that fixes the problem.

Attachments (1)

spirit_log_fix.patch (1.4 KB ) - added by Andrey Semashev 10 years ago.
The patch fixes Boost.Log v2 compilation.

Download all attachments as: .zip

Change History (4)

by Andrey Semashev, 10 years ago

Attachment: spirit_log_fix.patch added

The patch fixes Boost.Log v2 compilation.

comment:1 by Andrey Semashev, 9 years ago

Owner: changed from Joel de Guzman to Hartmut Kaiser

Any updates on this? You can see MinGW test failures because of this issue.

comment:2 by Hartmut Kaiser, 9 years ago

Resolution: fixed
Status: newclosed

(In [84118]) Fix #8066: Conflict with Boost.Log on GCC 4.4

comment:3 by Andrey Semashev, 9 years ago

(In [84142]) Refs #8066. The ticket is resolved, which should fix Boost.Log tests.

Note: See TracTickets for help on using tickets.