From: Nick Clifton <nickc@redhat.com>
To: Jan Beulich <jbeulich@suse.com>,
Andrew Goth <Andrew.Goth@caemilusa.com>,
"H.J. Lu" <hjl.tools@gmail.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: @CPP_FOR_BUILD@ problem since binutils-2.38
Date: Mon, 10 Oct 2022 11:06:29 +0100 [thread overview]
Message-ID: <0aad9687-e70d-9e79-e2d3-cbbba04b10f6@redhat.com> (raw)
In-Reply-To: <c8710738-94c8-ec95-357a-7a63cf50f50a@suse.com>
Hi Jan,
> Hmm, this looks to be due to 08ca783430ac syncing only Makefile.*
> with gcc's, but not configure.ac. The CPPFLAGS_FOR_BUILD issue was
> meanwhile addressed in isolation by commit e472ec9fad6d. Nick -
> what is the general policy / approach of syncing top level files?
From the MAINTAINERS file at the top level:
Makefile.*; configure; configure.ac; src-release
Any global maintainer can approve changes to these
files, but they should be aware that they need to
be kept in sync with their counterparts in the GCC
repository. Also please notify the following of
any committed patches:
binutils@sourceware.org
gdb-patches@sourceware.org
So changes to configure.ac should also be submitted to the gcc project.
Cheers
Nick
prev parent reply other threads:[~2022-10-10 10:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 4:10 Andrew Goth
2022-10-07 8:42 ` Jan Beulich
2022-10-10 0:43 ` Alan Modra
2022-10-10 6:50 ` Tsukasa OI
2022-10-11 13:03 ` Alan Modra
2022-10-11 18:21 ` Tom Tromey
2022-10-11 23:40 ` Alan Modra
2022-10-13 4:32 ` Tom Tromey
2022-10-10 10:06 ` Nick Clifton [this message]
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=0aad9687-e70d-9e79-e2d3-cbbba04b10f6@redhat.com \
--to=nickc@redhat.com \
--cc=Andrew.Goth@caemilusa.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=jbeulich@suse.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).