From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 50A063854569; Wed, 23 Nov 2022 13:43:32 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 50A063854569 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1669211012; bh=Sg+h3h0JGB/c5tW1sU4wgrWAe71blROQlQtDPkx9sF8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=a2NgSDPkhmo039toFIbmlfDxNJLdDyTsb2sNzVNavE9Nv4YoI8qlbnNSi9E7xLFrJ 5Lc6ZIzYLkRJDDVw80vF94piW8xNrCWPUX46htHSTo39S6kq/FuWY0+hy0AzUaGxfF 1u/vLjQmec+UmF2PpxYMRFSKK2iJlAfRCuAsfMDw= From: "ro at CeBiTec dot Uni-Bielefeld.DE" To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/107233] gm2 build hardcodes python3 Date: Wed, 23 Nov 2022 13:43:31 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: modula2 X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: gaius at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107233 --- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE --- > --- Comment #3 from Gaius Mulley --- > ok, thanks for the suggestion. I've changed gcc/configure.ac to use > AM_PATH_PYTHON and AM_CONDITIONAL: > > # Python3? > AM_PATH_PYTHON(,, [:]) > AM_CONDITIONAL([HAVE_PYTHON], [test "$PYTHON" !=3D :]) But wouldn't this pick up a version of python < 3.0 if nothing else is present? If the python code inside gcc/m2 does require 3.x, shouldn't this be AM_PATH_PYTHON([3.0],, [:]) (or whatever is the minimum) instead?=