Hi Matthias,
intrig...@debian.org:
> As discovered on #942663, src:apparmor fails to build for python 3.8.
> Example failure log¹:
> […]
> ./libraries/libapparmor.python3.8/conftest.c:18: undefined reference to
> `Py_Initialize'
> collect2: error: ld returned 1 exit status
I've investigated a bit and I now believe that tis bug is the symptom
of #943657 (which included a fix for a problem that was not described
in details): I've crudely patched debian/{control,rules} locally to
force building against both python 3.7 & 3.8, and I can't reproduce
this bug — the bindings are successfully built for these 2 pythons.
And Christian Boltz confirmed¹ that your patch for #943657 fixed the
build of the libapparmor Python binding for 3.8 in his environment
as well.
I'm nevertheless keeping this bug open: Christian reported² that the
test suite fails with python 3.8, which will make src:apparmor FTBFS
once 3.8 is the default version (we run the upstream test suite only
for the default python). I did not try reproducing this yet.
Matthias, do you have an environment where python 3.8 is the default,
where you could reproduce this?
[1] https://gitlab.com/apparmor/apparmor/merge_requests/430
[2] https://gitlab.com/apparmor/apparmor/issues/62
https://bugs.python.org/issue38688
Cheers,
--
intrigeri
