From: Gaius Mulley <gaiusmod2@gmail.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v4 1/19] modula2 front end: changes outside gcc/m2, libgm2 and gcc/testsuite.
Date: Mon, 12 Dec 2022 09:05:47 +0000 [thread overview]
Message-ID: <87a63t9el0.fsf@debian> (raw)
In-Reply-To: <CAFiYyc04B1yXKHu5VM579635thSQNALW6bgqzwySAA2jW3eapA@mail.gmail.com> (Richard Biener's message of "Sun, 11 Dec 2022 11:42:56 +0100")
Richard Biener <richard.guenther@gmail.com> writes:
> On Sat, Dec 10, 2022 at 1:49 AM Gaius Mulley via Gcc-patches
> <gcc-patches@gcc.gnu.org> wrote:
>>
>>
>> While writing the ChangeLog entries git gcc-verify spotted an oversight
>> with v3 of this patch set. I had forgotten to post gm2.texi and also a
>> tiny patchlet in gcc/configure.ac (to detect Python). HAVE_PYTHON is
>> used within gcc/m2/Make-lang.in to avoid generating the library section
>> included by gm2.texi should Python not be available.
>
> The configure check doesn't verify the python version.
indeed - I'll fix this
> Does --enable-generated-files-in-srcdir (used when building release
> tarballs) generate the required section so it's packed up in the
> release tarball and avoid requiring python3 when building from the
> release tarball?
currently working on it - no it fails - should be done rsn.
> Note these kind of dependences should be mentioned in
> install.texi - for python also listing required modules would be nice.
I'll add these.
> Thanks,
> Richard.
>
>> ok to commit? I've included gm2-lang.cc and lang.opt for reference.
>
> The python script would have been more informative, the generated
> .texi fragment and the Make-lang.in part as well
ah yes this is true, sorry.
regards,
Gaius
next prev parent reply other threads:[~2022-12-12 9:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-10 0:48 Gaius Mulley
2022-12-11 10:42 ` Richard Biener
2022-12-12 9:05 ` Gaius Mulley [this message]
2022-12-14 7:48 ` [PATCH v5 1/19] modula2 front end: Fixes, improvements detecting python3 and documentation generation (shorter) Gaius Mulley
2022-12-14 8:17 ` Richard Biener
2022-12-14 8:35 ` Gaius Mulley
2022-12-15 12:03 ` Jakub Jelinek
2022-12-15 12:51 ` Gaius Mulley
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=87a63t9el0.fsf@debian \
--to=gaiusmod2@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
/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).