-
-
Notifications
You must be signed in to change notification settings - Fork 39
boost_zlib is missing from Windows build? #65
Comments
@conda-forge/boost-cpp If currently |
Is there any update on this? @wolfv and I are running into the same issue. |
See 75848b6#diff-d04c86b6bb20341f5f7c53165501a393 .. not sure why it doesn't work |
@Tobias-Fischer Do you have a PR where it is failing? According to the log, boost::iostreams zlib support was built on master. |
@xhochy we're still on boost 1.72, but this here is failing: Note we have some new pipelines to build out the ROS packages on Azure. |
Was this maybe a boost library that was only available in older boost versions? I don't really see it anymore in the current sources / command line options. |
I am also seeing this on a new recipe I am submitting for Windows. I do see some mentions to |
If this helps anybody, I'm pretty sure this is a bug in the Boost autolinking support on Windows (not a conda issue per se). When Boost sees that you want to use boost::iostreams, it adds boost_zlib to the library dependencies, because iostreams was built with zlib support. This sometimes works, in some configurations where boost bundles its own copy of zlib, but conda (sensibly) uses the system zlib, so there is no boost_zlib to link against and you get the failure above. The workaround I use is to add |
In that case should we close? It's not clear there's anything we should be doing with the package build (though please correct me if I've missed something) |
I think so. The package build looks fine to me right now - it does include zlib support (my own recipes depend on this and are currently working). zlib did go missing for a while (see #114) but should have been fixed by #115 (which includes an explicit test for the zlib support). |
I tried to bring up another project on
conda-forge
but I came into a linkage problem as below:And even if I tried to use
add_definitions(-DBOOST_ALL_NO_LIB=1)
to hack theCMakeLists.txt
, which still gave me the similar result.The text was updated successfully, but these errors were encountered: