Boost C++ Libraries: Ticket #12505: 1.62 msvc configure regression : Name clash for main.obj

anonymous — Sat, 08 Oct 2016 10:38:18 GMT

full log: https://ci.appveyor.com/project/conda-forge/boost-feedstock/build/1.0.36 build script: https://github.com/conda-forge/boost-feedstock/blob/master/recipe/bld.bat

anonymous — Wed, 12 Oct 2016 09:24:21 GMT

I can confirm I have the same issue when specifying the ZLIB_LIBPATH

anonymous — Wed, 12 Oct 2016 10:23:30 GMT

maybe it comes from https://github.com/boostorg/iostreams/commit/08798f6fffd6b0bf1b08236dedf0b02f6d8aac8a

it seems ZLIB_LIBPATH is no more

anonymous — Wed, 12 Oct 2016 14:19:00 GMT

I confirm that if I remove the -s ZLIB_* options the error is gone,

thanks for the hint!

anonymous — Wed, 12 Oct 2016 14:19:59 GMT

but it's still a bug as the error is cryptic

anonymous — Thu, 13 Oct 2016 08:39:37 GMT

Removing the zlib options allows you to build boost but causes linker error when actually using the boost::iostreams::gzip_decompressor

anonymous — Thu, 13 Oct 2016 09:39:21 GMT

how do I configure properly with zlib support then ? (it tells me "zlib : yes")

owner, component changed

anonymous — Thu, 13 Oct 2016 09:40:15 GMT

owner changed from Douglas Gregor to Jonathan Turkanis
component configure script → iostreams

owner, component changed

anonymous — Thu, 13 Oct 2016 15:39:36 GMT

owner changed from Jonathan Turkanis to Vladimir Prus
component iostreams → build

anonymous — Thu, 13 Oct 2016 15:41:00 GMT

apparently the zlib build logic moved to boost.build: https://github.com/boostorg/build/blob/develop/src/tools/zlib.jam

anonymous — Tue, 03 Jan 2017 08:01:52 GMT

Does that mean that http://www.boost.org/doc/libs/1_63_0/libs/iostreams/doc/installation.html is not up to date ? I am looking for the new correct way to build boost with zlib support on Windows.

anonymous — Wed, 04 Jan 2017 14:52:37 GMT

I tried to use a user-config.jam to setup the zlib dependency but I end up with the same issue. Is there a workaround to build boost 1.62/1.63 with zlib support on Windows ?

anonymous — Mon, 09 Jan 2017 08:08:39 GMT

Question asked on stackoverflow: http://stackoverflow.com/questions/41543505/compiling-boost-1-62-1-63-with-zlib-on-windows

anonymous — Thu, 12 Jan 2017 14:49:23 GMT

No answer at all here or on stackoverflow... Am I the only one interested in having the latest boost on Windows with zlib support ? :(

anonymous — Sun, 15 Jan 2017 21:48:03 GMT

I also encountered the same issue when building boost by using a customized location of zlib and bzip2. It wasted me two days and I still got no clue: the error message is very cryptic and is meaningless (maybe not true to the boost guys). The only way I made it work is to add -I path_of_zlib/bzip2_header to cxxflags and add -Lpath_of_zlib/bzip2_lib to linkflags. It seems one reply in https://github.com/boostorg/iostreams/commit/08798f6fffd6b0bf1b08236dedf0b02f6d8aac8a says the same thing. But it looks to me the pull request does not examine the impact and does not update the document. I would not say that's a complete pull request.

anonymous — Mon, 16 Jan 2017 07:32:47 GMT

I am really surprised that no one even confirmed this is a bug while a new version has been released since then...

anonymous — Thu, 19 Jan 2017 13:58:34 GMT

i can confirm this problem on macOS, but did not find a solution yet :-(

anonymous — Wed, 01 Feb 2017 13:10:47 GMT

I tried using the cxxflags and linkflags without success: zlib is not detected and I vahe missing symbols if I try to use boost::iostreams gzip_compressor. Anyone found a workaround ?

Edward Diener — Wed, 01 Feb 2017 16:04:40 GMT

This is fixed in the latest 'develop' branch of Boost Build and should be in the next release of Boost.

status changed; resolution set

Steven Watanabe — Mon, 22 Jan 2018 23:58:38 GMT

status new → closed
resolution → fixed