Boost C++ Libraries: Ticket #11181: Header conflict "using-declaration causes a multiple declaration of 'boost::iterators::use_default'"

Steven Watanabe — Fri, 10 Apr 2015 15:07:13 GMT

It looks like it was caused by this: http://github.com/boostorg/iterator/commit/dc96d371faf87a88c04057861136c9dfa68103d7

anonymous — Fri, 10 Apr 2015 15:16:27 GMT

Replying to steven_watanabe:

It looks like it was caused by this:

May be, anyway i'll be waiting fix of this issue

Steven Watanabe — Fri, 10 Apr 2015 15:52:42 GMT

A quick workaround is to delete the declarations of boost::use_default in boost/type_erasure/iterator.hpp and add a #include <boost/iterator/iterator_adaptor.hpp>. I'll need to think a bit more about what the right fix should be. It's too late for 1.58 anyway.

anonymous — Sat, 11 Apr 2015 11:37:48 GMT

Replying to steven_watanabe:

It's too late for 1.58 anyway.

I hope it will be fixed at least in 1.59

fsmoke — Sat, 11 Apr 2015 11:39:23 GMT

Replying to steven_watanabe:

It's too late for 1.58 anyway.

I hope it will be fixed at least in 1.59

Domagoj Šarić — Mon, 20 Apr 2015 08:37:19 GMT

Replying to steven_watanabe:

It's too late for 1.58 anyway.

Steven, this means that TypeErasure has been (and still is) broken on MSVC (and thus completely unusable for cross platform projects) for three consecutive Boost versions... Don't mean to sound harsh but that's quite off-putting (if not plain lame)...Are there some tests missing that should be added to catch these problems early?

nat@… — Mon, 23 Nov 2015 11:42:08 GMT

In Boost 1.59.0, (what I assume to be) another manifestation of the same bug is driven by this source:

#include <boost/iterator/iterator_adaptor.hpp>
#include <boost/type_erasure/any.hpp>

It's broken in either order, though the errors differ:

#include <boost/type_erasure/any.hpp>
#include <boost/iterator/iterator_adaptor.hpp>

My platform is Apple LLVM version 7.0.0 (clang-700.1.76) from Xcode 7.1.1.

attachment set

nat@… — Mon, 23 Nov 2015 12:03:25 GMT

attachment → 11181.patch

patch implementing Steven's suggested workaround

nat@… — Mon, 23 Nov 2015 12:04:49 GMT

Applying the attached 11181.patch allowed me to work around this problem.

fsmoke@… — Tue, 01 Dec 2015 11:08:44 GMT

when it be in release?

Michel Morin — Tue, 01 Dec 2015 14:50:50 GMT

Hey, did you try Boost 1.60 beta RC? I couldn't get errors using that version on clang trunk. You can get the beta RC here; see this ML post. (Note that Boost 1.60 beta has not yet been released.)

status changed; resolution set

Steven Watanabe — Sat, 13 Feb 2016 21:04:17 GMT

status new → closed
resolution → fixed

status, severity, type, component, version, milestone changed; resolution deleted

Smithe353 — Thu, 03 Nov 2016 21:56:28 GMT

status closed → reopened
severity Problem → Not Applicable
type Bugs → Library Submissions
component type_erasure → xpressive
version Boost 1.57.0 → Boost.Build-M3
milestone To Be Determined → Website 1.X
resolution fixed

You are a really persuasive writer. I can see this in your writeup. You've a way of writing compelling info that sparks significantly interest. bgeebbbeckabdgba