public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/107233] New: gm2 build hardcodes python3
Date: Wed, 12 Oct 2022 12:08:20 +0000 [thread overview]
Message-ID: <bug-107233-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107233
Bug ID: 107233
Summary: gm2 build hardcodes python3
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: modula2
Assignee: gaius at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
Target Milestone: ---
Target: *-*-solaris2.11
When trying to build the current devel/modula-2 branch on Solaris 11.3/SPARC
(only tried on 11.4 before), it fails trying to execute python3
unconditionally:
python3 /vol/gcc/src/hg/master/modula-2/gcc/m2/tools-src/def2texi.py -b./
-f/vol/gcc/src/hg/master/modula-2/gcc/m2/gm2-libs/Builtins.def >
/var/gcc/modula-2/11.4-gcc-modula-2/gcc/m2/Builtins.texi
/bin/ksh: python3: not found
make[3]: *** [/vol/gcc/src/hg/master/modula-2/gcc/m2/Make-lang.in:167:
Builtins.texi-check] Error 127
This happens because Solaris 11.3, unlike 11.4, has no python3 command. It
only
provides python2.7 and python3.4.
I believe this could easily be fixed by using Automake's AM_PATH_PYTHON([3.0])
(or whatever minimal python 3.x version is required), substituting the
resulting
$PYTHON into Make-lang.in and the scripts that currently hardcode python3
instead.
next reply other threads:[~2022-10-12 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 12:08 ro at gcc dot gnu.org [this message]
2022-10-12 12:08 ` [Bug modula2/107233] " ro at gcc dot gnu.org
2022-11-03 15:02 ` gaius at gcc dot gnu.org
2022-11-08 13:07 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-11-22 16:35 ` gaius at gcc dot gnu.org
2022-11-23 13:43 ` ro at CeBiTec dot Uni-Bielefeld.DE
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-107233-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).