[Bug build/29308] [gdb/build] python 3.10 problems

["vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=29308

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Simon Marchi from comment #1)
> Why do we ship our own python-config.py? 

Here ( https://sourceware.org/pipermail/gdb-patches/2010-May/074836.html ) is
mentioned:
...
python-config is a python script so it won't work when build != host.
...

> We could maybe rely on the
> python-config scripts shipped with Python installations. 

I'll give that a try.

> I guess that
> python-config scripts were maybe not always there in the past?
> 

AFAICT, the python-config shell script was introduced starting 3.4.

>From looking at the cpython.git sources, the python-config python script
appeared in 2.7, but looking at the original commit of
gdb/python/python-config.py is mentions a copy from 2.6.5, so perhaps I'm
missing something.

> We would append `-config` to the python executable.  Since you passed
> --with-python=python3, it means python3 is in your PATH, so python3-config
> should also exist in your PATH.
> 

FWIW, I need to install python3-devel to get python3-config, in addition to the
python3 package, but that's not a problem of course.  I need to install lots of
-devel packages to be able to build gdb.

> My guess is that since python-config scripts are now shell scripts, they can
> be executed on the build machine even cross-compiling.  So maybe it would
> simplify the case described here:
> 
> https://sourceware.org/gdb/wiki/CrossCompilingWithPythonSupport
> 
> Not sure.

AFAICT, that was exactly the purpose of moving to a shell script.

-- 
You are receiving this mail because:
You are on the CC list for the bug.