<0​xfffc:monero.social> MSYS2 CI issue is upstream: boostorg/boost #1079

0xfffc: did you see the same behavior with boost 1.88?

<0​xfffc:monero.social> selsta: Yes. I double confirmed again right now. Another data point: look at the ICU libraries found by boost ( when building boost via pacman ), you will see it founds only `.dll.a` files.

<0​xfffc:monero.social> > FIND_PACKAGE_MESSAGE_DETAILS_ICU:INTERNAL=[C:/msys64/mingw64/include][C:/msys64/mingw64/lib/libicudt.dll.a;C:/msys64/mingw64/lib/libicuin.dll.a;C:/msys64/mingw64/lib/libicuuc.dll.a;C:/msys64/mingw64/lib/libicudt.dll.a;C:/msys64/mingw64/lib/libicuin.dll.a;C:/msys64/mingw64/lib/libicuuc.dll.a][found components: data i18n uc ][v77.1()]

<0​xfffc:monero.social> from CMakeCache.txt in boost build directory.

what I meant is if it finds the same libs with 1.88 I'm not sure if this is the issue we are having as the issue for us got introduced once mingw updated boost to 1.89

<0​xfffc:monero.social> selsta: You are correct. But this is the root issue. When pacman updated boost to 1.89, it broke something.

<0​xfffc:monero.social> But the root of the issue is this one. This is the build command: paste.debian.net/1394883

<0​xfffc:monero.social> when you add `.dll` to the end of icu files, it finds them and works correctly.

<0​xfffc:monero.social> `-licuio.dll -licuin.dll -licuuc.dll -licudt.dll -licutu.dll` works without issue and compiles.

<0​xfffc:monero.social> the fact that boost is in the middle of transition from b2 to CMake, and the pacman used cmake prematurely for building for msys2/mingw is make it convoluted.

<0​xfffc:monero.social> In case anyone interested: a nice and easy PR would change ICU_LIBRARIES to find_package(ICU ...) and ICU::i18n style CMake ( Iconv::Iconv too ). But that is not going to solve this issue. Since the root of the issue is the way boost handles compilation.

i didn't realize they switched to cmake

<0​xfffc:monero.social> Not official / final yet. github.com/boostorg/cmake they have been actively working on this since 2020 IIRC. The msys2/mingw should've not used it. since it is pretty early stage. github.com/msys2/MINGW-packages/blo…9ed7c1/mingw-w64-boost/PKGBUILD#L80

maybe in addition a msys2 issue should be opened? they can quickly put out a new version

though since our issue is quite specific not sure if they would care

<0​xfffc:monero.social> not a bad idea. worth the try.