From: Fangrui Song <i@maskray.me>
To: Alan Modra <amodra@gmail.com>
Cc: binutils@sourceware.org, Hans-Peter Nilsson <hp@axis.com>
Subject: Re: Should we require GNU make in binutils?
Date: Thu, 24 Aug 2023 22:12:06 -0700 [thread overview]
Message-ID: <DS7PR12MB5765CFE8051E7285001CA6A4CBE3A@DS7PR12MB5765.namprd12.prod.outlook.com> (raw)
In-Reply-To: <ZOgesf+pTitJDdSN@squeak.grove.modra.org>
On Thu, Aug 24, 2023 at 8:23 PM Alan Modra via Binutils
<binutils@sourceware.org> wrote:
>
> I see the toplevel Makefile.in makes use of $(filter-out ..) and other
> GNU Make extensions, and requires GNU Make 3.80 or later when building
> gcc. gdb also uses GNU make extensions. It seems silly to me that
> binutils is still trying to avoid GNU make extensions.
>
> We could start with the following (originally from Hans-Peter) which
> avoids a whole lot of entering/leaving messages when building with
> --enable-targets=all. What do people think?
This is a good idea!
next prev parent reply other threads:[~2023-08-25 5:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 3:23 Alan Modra
2023-08-25 5:12 ` Fangrui Song [this message]
2023-08-25 8:15 ` Jan Beulich
2023-08-25 9:26 ` Alan Modra
2023-08-25 8:37 ` Jose E. Marchesi
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=DS7PR12MB5765CFE8051E7285001CA6A4CBE3A@DS7PR12MB5765.namprd12.prod.outlook.com \
--to=i@maskray.me \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=hp@axis.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).