Hi Regina, On 2025-05-17 16:30, Regina Henschel wrote:
I have attached the output of configure and of build.
the output of the different jobs is interspersed (`make -O` could help to prevent that), but from what I can see, the failure is related to Harfbuzz and Meson. (The accessibility warnings are just warnings and unrelated to the build failure.)
From the build log:
python3: can't open file '/cygdrive/c/buildLo2/core/workdir/UnpackedTarball/harfbuzz/C:/BuildLOAdds/meson/meson-1.7.2/meson.py': [Errno 2] No such file or directory ... make[1]: *** [C:/BuildLO2/core/external/harfbuzz/ExternalProject_harfbuzz.mk:51: C:/buildLo2/core/workdir/ExternalProject/harfbuzz/build] Error 1 make[1]: *** Waiting for unfinished jobs....
The configure log includes this:
MESON=C:/BuildLOAdds/meson/meson-1.7.2/meson.py
and apparently there is some problem with the path used during the build
as `/cygdrive/c/buildLo2/core/workdir/UnpackedTarball/harfbuzz/` can be
seen as being prepended to that path for some reason.
There was some discussion on IRC recently and others might be able to say more, but if I remember correctly, one working configuration since
commit 9430b6549a6bf4b6717530c578796e93c5a43f9a
Date: Wed May 7 19:46:13 2025 +0200
use meson as an external when building with fully-internal python
should be to add `--enable-python=fully-internal` to autogen.input and
stop explicitly setting `MESON=...` in which case the LO build will take
care of downloading meson and using that one instead of a manually
downloaded one.
Does that help? Michael
OpenPGP_signature.asc
Description: OpenPGP digital signature
