From: Christophe Lyon <christophe.lyon@linaro.org>
To: Alexandre Oliva <oliva@gnu.org>
Cc: gcc-patches@gcc.gnu.org, josmyers@redhat.com
Subject: Re: [PATCH] gcc/Makefile.in: Fix install-info target if BUILD_INFO is empty
Date: Mon, 12 Feb 2024 11:13:49 +0100 [thread overview]
Message-ID: <CAPS5khYSb0JN3ZTCnhinC0isAn9Zsez=JGY6X2+utz7cvqWKeA@mail.gmail.com> (raw)
In-Reply-To: <orbk8n4k8q.fsf@lxoliva.fsfla.org>
On Sun, 11 Feb 2024 at 06:56, Alexandre Oliva <oliva@gnu.org> wrote:
>
> Hello, Christophe,
>
> On Feb 10, 2024, Christophe Lyon <christophe.lyon@linaro.org> wrote:
>
> > gcc/
> > * Makefile.in: Add no-info dependency.
> > * configure.ac: Set BUILD_INFO=no-info if makeinfo is not
> > available.
> > * configure: Regenerate.
>
> Thank you, this is ok.
>
> Now, this doesn't fix a regression, does it?
Of course not :-)
>
> I would support putting this in for GCC 14, but I would be overstepping
> my authority if I approved even such a small and well-contained
> improvement patch in the current stage, so I'm approving it for stage1,
> but maybe some global maintainer or release manager will chime in in
> support for earlier merging? (hint, hint ;-)
Thanks!
>
> --
> Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
> Free Software Activist GNU Toolchain Engineer
> Disinformation flourishes because many people care deeply about injustice but
> very few check the facts. Think Assange & Stallman. The empires strike back
next prev parent reply other threads:[~2024-02-12 10:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 17:15 [PATCH] gcc/configure: Re-introduce INSTALL_INFO Christophe Lyon
2024-02-02 10:10 ` rep.dot.nop
2024-02-02 10:40 ` Christophe Lyon
2024-02-05 11:26 ` [PATCH] gcc/Makefile.in: Fix install-info target if BUILD_INFO is empty Christophe Lyon
2024-02-06 5:37 ` Alexandre Oliva
2024-02-10 22:06 ` Christophe Lyon
2024-02-11 5:56 ` Alexandre Oliva
2024-02-12 10:13 ` Christophe Lyon [this message]
2024-02-12 10:27 ` Jakub Jelinek
2024-02-12 15:48 ` Christophe Lyon
2024-02-05 11:30 ` [PATCH] gcc/configure: Re-introduce INSTALL_INFO Christophe Lyon
2024-02-05 12:25 ` rep.dot.nop
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='CAPS5khYSb0JN3ZTCnhinC0isAn9Zsez=JGY6X2+utz7cvqWKeA@mail.gmail.com' \
--to=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=josmyers@redhat.com \
--cc=oliva@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).