Opened 11 years ago

Closed 9 years ago

Last modified 9 years ago

#6123 closed Patches (fixed)

py_nonblocking.cpp makes unqualified reference to make_tuple

Reported by: Luke Camden <lukeocamden@…> Owned by: Matthias Troyer
Milestone: Boost 1.49.0 Component: python USE GITHUB
Version: Boost Development Trunk Severity: Problem
Keywords: python c++11 Cc:

Description

This can be ambiguous if client code has done '#include <tuple>'

Attachments (1)

py_nonblocking.cpp.patch (716 bytes ) - added by Luke Camden <lukeocamden@…> 11 years ago.

Download all attachments as: .zip

Change History (12)

by Luke Camden <lukeocamden@…>, 11 years ago

Attachment: py_nonblocking.cpp.patch added

comment:1 by Holger Grund <holger.grund@…>, 11 years ago

Component: mpiPython
Keywords: mpi removed
Owner: changed from Douglas Gregor to Ralf W. Grosse-Kunstleve
Type: BugsPatches

Note that Boost fails to build with -std=c++0x with recent version of GCC due to this problem.

A similar problem #3584 was fixed with r57641 in the same way.

comment:2 by Ralf W. Grosse-Kunstleve, 11 years ago

Patch applied with trunk r57641.

This isn't really in my domain but the patch is so simple I went ahead anyway.

comment:3 by Ralf W. Grosse-Kunstleve, 11 years ago

Owner: changed from Ralf W. Grosse-Kunstleve to doug_gregor

There is no mainainter for mpi listed in libs/maintainers.txt.

Doug, how's doing the merging of the mpi directories to the release branch?

comment:4 by Luke Camden, 10 years ago

Looks like this was missed out of 1.49.0 and 1.50.0. Could it be included in 1.51.0? In the meantime it's fairly easy to patch at my end.

in reply to:  4 comment:5 by Luke Camden, 10 years ago

Also missing in 1.51.0

comment:6 by anonymous, 9 years ago

Still broken in 1.54.0 beta 1

comment:7 by Matthias Troyer, 9 years ago

Owner: changed from doug_gregor to Matthias Troyer
Status: newassigned

comment:8 by Matthias Troyer, 9 years ago

Resolution: fixed
Status: assignedclosed

This was already applied to the trunk in r75914

comment:9 by anonymous, 9 years ago

Should I open another ticket to track the merge to the release branch?

comment:10 by Matthias Troyer, 9 years ago

I will do the merge as soon as the tests run through successfully

comment:11 by anonymous, 9 years ago

Thanks!

Note: See TracTickets for help on using tickets.