Boost C++ Libraries: Ticket #1931: Boost.Python headers won't compile with GCC 4.3

vbe@… — Mon, 19 May 2008 17:07:12 GMT

I wanted to submit a patch, but it does not work:

Internal Error

Submission rejected as potential spam (Akismet says content is spam)

anonymous — Thu, 22 May 2008 09:57:41 GMT

FROM http://sourceforge.net/tracker/index.php?func=detail&aid=1968282&group_id=165310&atid=835077 ==================================================================================

This is a bug in boost python, there are similar reports for other projects.

If you want a quick workaround do:

1) /usr/include/boost/python/detail/def_helper.hpp:

line 189: typename keyword_extract<all_t>::result_type keywords() const change to: typename keyword_extract<all_t>::result_type extract_keywords() const

2) /usr/include/boost/python/class.hpp:

line 542: , helper.keywords() change to: , helper.extract_keywords()

line 571: helper.default_implementation(), helper.policies(), helper.keywords()) change to: helper.default_implementation(), helper.policies(), helper.extract_keywords())

soc — Thu, 22 May 2008 10:17:34 GMT

FROM http://www.gnu.org/software/gcc/gcc-4.3/porting_to.html

Name lookup changes

GCC 4.3 by default no longer accepts code such as

template <class _Tp> class auto_ptr {};
template <class _Tp>
struct counted_ptr
{
  auto_ptr<_Tp> auto_ptr();
};

but will issue the diagnostic

error: declaration of 'auto_ptr<_Tp> counted_ptr<_Tp>::auto_ptr()' error: changes meaning of 'auto_ptr' from 'class auto_ptr<_Tp>'

The reference to struct auto_ptr needs to be qualified here, or the name of the member function changed to be unambiguous.

template <class _Tp> class auto_ptr {};
template <class _Tp>
struct counted_ptr
{
  ::auto_ptr<_Tp> auto_ptr();
};

In addition, -fpermissive can be used as a temporary workaround to convert the error into a warning until the code is fixed. Note that then in some case name lookup will not be standard conforming.

status changed; resolution set

Dave Abrahams — Wed, 25 Jun 2008 00:48:09 GMT

status new → closed
resolution → fixed

As far as I can tell this was fixed in [39434]