On 12.01.2019 12:30, Osman Zakir via Boost-users wrote:
I was also told that the problem could be either my network environment, something in my code, or both, and I was just giving info to help with figuring out which one it might be. And notice that I did also ask about a problem with building Boost, too.
I did not mention your zlib problem as there is another thread "Forcing boost to build zlib" active right know that I believe should answer your question. BTW, do you know what the term "top posting" means? Cheers, Leon
There are still 4 failed targets and 5 skipped targets when trying to build Boost. There were some "__imp_" unresolved symbols when building Boost, before, too. I wonder if they're there because of zlib.dll. If so, how do I tell b2 where that DLL is? I say this because when I built Node.js from source before, there were unresolved symbols for __imp_read, __imp_write and __imp_open, and specifying the path to the folder with zlib.dll in Visual Studio solved that problem. ------------------------------------------------------------------------
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org https://lists.boost.org/mailman/listinfo.cgi/boost-users