Hello,
Using --enable-python=internal fixes the issue.
I'm rebuilding the whole bibisect_linux64_24_8 repository from scratch
so the extension can be installed in that repo.
Regarding bibisect_linux64_24_2, since the extension can be installed
before the mentioned commit, I don't think it's needed to rebuilt the
repository but of course it can be done if needed.
Regards
On 18/1/24 9:50, Stephan Bergmann wrote:
Be aware that the Linux bibisect repo
<https://wiki.documentfoundation.org/QA/Bibisect/Linux#bibisect-linux-64-24.2>
apparently changed its configuration midway at
commit 8df817ae65e9ef94ae056abdf24d3c864e6077d0 (HEAD)
Author: Jenkins Build User <tdf@xxxxxxxxxx>
Date: Tue Oct 3 11:37:10 2023 +0200
source sha:1eef07805021b7ca26a1a8894809b6d995747ba1
source sha:1eef07805021b7ca26a1a8894809b6d995747ba1
It dropped the bundled python (with PyUNO support) from instdir (and
started to support skia).
I now got funny claims that bibisecting allegedly showed that my
<https://git.libreoffice.org/core/+/1eef07805021b7ca26a1a8894809b6d995747ba1%5E!/>
"Bump baseline to C++20" started to break Python-related stuff (see
the comments starting at
<https://gerrit.libreoffice.org/c/core/+/155121/10#message-f8c7de0591d9e8f6a8abb1029fec9ce32fab460f>
"Bump baseline to C++20").
--
Xisco Faulí
LibreOffice QA Team
IRC: x1sc0
