Hi Andreas, noticed that remark just now:
On Sat, Jun 21, 2025 at 11:51 AM Andreas Mantke <ma...@gmx.de> wrote: > > My autogen.input looks like this: > --without-system-nss > --disable-skia > CC=gcc-12 > CXX=g++-12 > --enable-python=fully-internal gcc-12 to build internal python certainly should work, gcc-12 is used on baseline builders and those in parts also built with fully-internal python on linux, but regardless: > Here the messages in the shell (last part): > […] > A build with the system Python is not possible. There is an incompatibility > with meson. I use OpenSuSE 15.6. There should be no fundamental incompatibility, more a matter of not telling the build which meson to use and how to call it. If you add MESON=/how/meson/should/be/called to your autogen.input it will use that as-is and not try to run it with the python used during the LibreOffice build, and harfbuzz is fine with old versions of meson still, so if you run into an incompatibility with meson even after adding "MESION=meson" (if meson is in your path and you want to use that) or "MESON=/some/custom/path", I'd love to see the logs for that. > Anyone else running into this issue? Nope.. (and using a python venv to build surely shouldn't be necessary, using system-python on linux for the build-side should be perfectly fine and not conflict with meson using a different python, given that the build is configured in a non-conflicting way) ciao Christian
