1.66 i686-w64-mingw32-g++-win32

[Martin Kjær Jørgensen <mkj@…>]

i'm using boost 1.65.1 for a project in which the new beast framework v124 is used as an internal webserver. building using gcc on linux and gcc-mingw targeting win32 works in this setup.

today, i've tried upgrade to boost 1.66, skipping the need for the external beast v124 source. still, gcc+linux build works, but my gcc-mingw build fails with alot of errors about the use of futures in asio.

attached is a stripped output of the errors.

[Martin Kjær Jørgensen <mkj@…>]

compiler error output

[Christopher Chadwick <cchadwick@…>]

I can concur the same observation when compiling with MinGW's g++7.2.0. Not ruling out operator error here, but I've been poking around for a couple of days not and haven't been able to resolve the issue.

[john@…]

Me too, when cross-compiling 'dcpomatic'. Almost identical output to above. Lots of mentions of std::promise.

[Christopher Chadwick <cchadwick@…>]

My apologies for a late post to those in search of a resolution. I was able to get a proper compile. After digging more into the config header for asio (I can't recall at the moment the exact file, but no modifications were necessary), I found that if I defined BOOST_ASIO_DISABLE_STD_FUTURE in the preprocessor, things compiled. The issue I think is the usual issue with mingw on Windows not having the std::thread/future/promise support as with MSVC or a Linux variety gcc/g++. I use the boost variety of these in most circumstances. I want to say (at least hope, although I'm not sure) that doing so will set asio to use the boost varieties of these as needed. I'll defer that to Mr. Kohlhoff.