This is odd. You are correct about PKGBUILD. Here is the contents of my /mingw32/lib/cmake folder:
boost_atomic-1.70.0/ boost_chrono-1.70.0/ boost_container-1.70.0/ boost_context-1.70.0/ boost_contract-1.70.0/ boost_coroutine-1.70.0/ boost_date_time-1.70.0/ boost_exception-1.70.0/ boost_fiber_numa-1.70.0/ boost_fiber-1.70.0/ boost_filesystem-1.70.0/ boost_graph_parallel-1.70.0/ boost_graph-1.70.0/ boost_headers-1.70.0/ boost_iostreams-1.70.0/ boost_locale-1.70.0/ boost_log_setup-1.70.0/ boost_log-1.70.0/ boost_math_c99-1.70.0/ boost_math_c99f-1.70.0/ boost_math_c99l-1.70.0/ boost_math_tr1-1.70.0/ boost_math_tr1f-1.70.0/ boost_math_tr1l-1.70.0/ boost_math-1.70.0/ boost_numpy-1.70.0/ boost_prg_exec_monitor-1.70.0/ boost_program_options-1.70.0/ boost_python-1.70.0/ boost_random-1.70.0/ boost_regex-1.70.0/ boost_serialization-1.70.0/ boost_stacktrace_addr2line-1.70.0/ boost_stacktrace_backtrace-1.70.0/ boost_stacktrace_basic-1.70.0/ boost_stacktrace_noop-1.70.0/ boost_stacktrace_windbg_cached-1.70.0/ boost_stacktrace_windbg-1.70.0/ boost_system-1.70.0/ boost_test_exec_monitor-1.70.0/ boost_thread-1.70.0/ boost_timer-1.70.0/ boost_type_erasure-1.70.0/ boost_unit_test_framework-1.70.0/ boost_wave-1.70.0/ boost_wserialization-1.70.0/ Boost-1.70.0/ BoostDetectToolset-1.70.0.cmake c-ares/ clang/ DBus1/ fftw3/ glew/ glm/ harfbuzz/ jsoncpp/ libxml2/ llvm/ minizip-exports.cmake minizip-exports-release.cmake openjpeg-2.3/ SDL2/ xapian/ z3/ Maybe ./b2 now just calls cmake to do the build. I have never built boost on msys2 using cmake or b2 so this wasn't me. When I downgrade boost, the boost_* folders get removed so something is different. On 5/1/2019 11:55 AM, Nick Østergaard wrote: > I don't think so, at least when I look at the PKGBUILD it is still > using bootstrap.sh and b2 to build. See: > https://github.com/msys2/MINGW-packages/blob/fd550b8d48e6bc831b1e36202eaf495cba5062f8/mingw-w64-boost/PKGBUILD > > I don't see anything immediately alarming. Maybe the builds scripts in > boost changed such that they need patching to work properly with > msys2? > > Also it seems that other people are struggling: > https://github.com/msys2/MINGW-packages/issues/5233 > > Nick > > On Wed, 1 May 2019 at 15:41, Wayne Stambaugh <stambau...@gmail.com> wrote: >> >> On 5/1/2019 8:53 AM, John Beard wrote: >>> On 01/05/2019 13:36, Wayne Stambaugh wrote: >>>> On 5/1/2019 8:27 AM, John Beard wrote: >>>>> On 01/05/2019 12:53, Jeff Young wrote: >>>>>> Someone on the forums had to turn off the qa tests on Linux to get it >>>>>> to build: >>>> It fails during linking not compiling. I also tried clang but I get the >>>> same error. Here is the gcc command that is failing: >>> >>> Jeff's forum issue is a compiler failure in qa_kicad2step, not linking >>> in qa_sexpr. I don't think it's related to this. >>> >>>> cd /E/build/mingw64/kicad/product-debug/qa/libs/sexpr && >>>> /E/msys64/mingw64/bin/g++.exe -Wall -Wsuggest-override -Werror=vla >>>> -fpermissive -g3 -ggdb3 -DDEBUG -Wno-deprecated-declarations >>>> -Wl,--whole-archive CMakeFiles/qa_sexpr.dir/objects.a >>>> -Wl,--no-whole-archive -o qa_sexpr.exe >>>> -Wl,--major-image-version,0,--minor-image-version,0 >>>> ../../../libs/sexpr/libsexpr.a >>>> ../../unit_test_utils/libunit_test_utils.a -LE:/msys64/mingw64/lib -pipe >>>> -Wl,--subsystem,windows -mwindows -lwx_mswu_gl-3.0 -lwx_mswu_aui-3.0 >>>> -lwx_mswu_adv-3.0 -lwx_mswu_html-3.0 -lwx_mswu_core-3.0 >>>> -lwx_baseu_net-3.0 -lwx_baseu-3.0 -lwx_baseu_xml-3.0 -lwx_mswu_stc-3.0 >>>> -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 >>>> -luuid -lcomdlg32 -ladvapi32 >>> >>> Do *any* unit tests build? I don't see "-lboost_unit_test_framework >>> -lboost_filesystem -lboost_system" in there, and it should be. Does >>> CMake have the right paths? For me, it is like this: >>> >>> >>> Boost_UNIT_TEST_FRAMEWORK_LIBRARY_DEBUG:FILEPATH=/usr/lib/libboost_unit_test_framework.so >> >> boost_unit_test_framework_DIR:PATH=E:/msys64/mingw32/lib/cmake/boost_unit_test_framework-1.70.0 >> >> Looks like msys2 folks decided to use boost's cmake support to build >> boost starting with 1.70 instead of the old boost build system. I >> thought this was still experimental but I could be wrong. None the >> less, boost 1.70 is broken on msys2 so I guess I will have to downgrade >> and pin boost yet again :( For everyone out there using msys2, do not >> upgrade to boost 1.70. If you did, downgrade boost to 1.69 and edit >> your pacman.conf file to prevent boost from upgrading. >> >>> >>> >>> Sadly Arch hasn't got Boost 1.70 yet, so it's a bit tricky to test. >>> >>> Cheers, >>> >>> John >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
