From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
 id BBD0F3858D39; Fri,  1 Jul 2022 09:27:03 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BBD0F3858D39
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/29308] [gdb/build] python 3.10 problems
Date: Fri, 01 Jul 2022 09:27:03 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: build
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-29308-4717-nZ3wRwH5TO@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-29308-4717@http.sourceware.org/bugzilla/>
References: <bug-29308-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gdb-prs@sourceware.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gdb-prs mailing list <gdb-prs.sourceware.org>
List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=unsubscribe>
List-Archive: <https://sourceware.org/pipermail/gdb-prs/>
List-Help: <mailto:gdb-prs-request@sourceware.org?subject=help>
List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-prs>,
 <mailto:gdb-prs-request@sourceware.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jul 2022 09:27:03 -0000

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

--- 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?=20

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 !=3D host.
...

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

I'll give that a try.

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

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=3Dpython3, it means python3 is in your PATH, so python3-con=
fig
> should also exist in your PATH.
>=20

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 lot=
s 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:
>=20
> https://sourceware.org/gdb/wiki/CrossCompilingWithPythonSupport
>=20
> Not sure.

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

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