Re: Python2 -> Python3 fallout

On 2020/03/30 20:31, Rafael Sadowski wrote:
> On Mon Mar 30, 2020 at 07:34:10PM +0200, Christian Weisgerber wrote:
> > People have been switching ports from Python2 to Python3. In some
> > cases, this appears to bubble up to dependent ports and break them:
> >
> > games/freeorion undefined symbol: PyString_FromStringAndSize
> > games/gemrb undefined symbol: Py_InitModule4_64
>
> !cmake

those two are cmake too.

freeorion:
===> Configuring for freeorion-0.4.8p1
-- Build type CMAKE_BUILD_TYPE set to Release
[..]
-- Found PythonInterp: /usr/local/bin/python2.7 (found suitable version "2.7.17", minimum required is "2.7")
-- Found PythonLibs: /usr/local/lib/libpython3.7m.so.0.0 (found suitable version "2.7.17", minimum required is "2.7")

gemrb:
===> Configuring for gemrb-0.8.6
-- The C compiler identification is Clang 8.0.1
[..]
-- Found PythonLibs: /usr/local/lib/libpython3.7m.so.0.0 (found suitable version "2.7.17", minimum required is "2.3")
-- Looking for Python libraries and headers: found

As a first step I think check whether backing out the cmake py-sphinx commit
fixes things and if it does, commit the backout. Then work on a different
way forward for sphinx.