Problem when cross-compiling with libc++ in mingw about iostreams

[jcelerier]

I solve it in my own code by doing

#include <boost/iostreams/detail/config/fpos.hpp>
#if defined(BOOST_IOSTREAMS_HAS_DINKUMWARE_FPOS)
#undef BOOST_IOSTREAMS_HAS_DINKUMWARE_FPOS
#endif

beforehand but I guess there should be a better way. Certainly the check should look for more than _YVALS now, since mingw includes yvals.h.

[jeking3]

The CI builds on AppVeyor pass, but they use the following build command (it is mingw inside msys2):
./b2 libs/iostreams toolset=gcc-mingw32 cxxstd=03 address-model=32 variant=release,debug -j3

I was going to suggest replacing the block you identified with the following:

#include <boost/predef/library/std.h>
#if (BOOST_LIB_STD_DINKUMWARE)
...

However after looking at the detection there, it relies on the same check for _YVALS. Copying @grafikrobot since the Dinkumware detection probably needs to omit MinGW platforms. In fact, I'd suggest looking at the checks in iostreams to make sure we're not missing anything else in predef.

[jcelerier]

The CI builds on AppVeyor pass, but they use the following build command (it is mingw inside msys2):

hi, compared to this configuration I'm building with clang and libc++, not gcc and libstdc++ - I guess this could be the difference ?

[SquallATF]

@jcelerier append && !defined(_LIBCPP_VERSION) at

iostreams/include/boost/iostreams/detail/config/fpos.hpp

Line 29 in 15e7258

&& !(defined(BOOST_MSVC) && _MSVC_STL_VERSION >= 141)

[tomay3000]

I have the same problem when compiling v1.72 using the same toolchain https://github.com/mstorsjo/llvm-mingw under Windows 7 x64 boostorg/build#557

So I have to apply the patch and see!

BTW, what command lines u used to bootstrap and compile it?

TIA.

[Gei0r]

I face the same problem in v1.74 using clang and libc++ on Windows.
#106 fixes it. Please merge it.