public inbox for
 help / color / mirror / Atom feed
From: Tsukasa OI <>
To: Nick Clifton <>
Subject: Re: [PATCH 1/1] configure: Pass CPPFLAGS_FOR_BUILD to subdirs
Date: Wed, 21 Sep 2022 14:56:40 +0900	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2022/09/20 21:53, Nick Clifton wrote:
> Hi Tsukasa,
>> ChangeLog:
>>     * Pass CPPFLAGS_FOR_BUILD to subdirectories.
>>     * configure: Regenerate.
> Patch approved - please apply.
> Note - you may wish to submit a copy of this patch to the gcc-patches
> mailing list as well, since gcc and binutils/gdb try to share the top
> level configure files.
> Cheers
>   Nick

Hi Nick,

I found that GCC already has a superset of this patch.
Commit 84401ce5fb4e ("[PATCH 1/5] Ensure build CPP/CPPFLAGS
is used for build targets") is the one.

I will commit my patchset as is (because this is sufficient to resolve
Binutils side issue) but also will seek an opportunity to sync with this
when I revisit configure scripts again (currently, I'm working on RISC-V
(various parts) and disassembler improvements on Arm and AArch64).


      reply	other threads:[~2022-09-21  5:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-15  5:59 [PATCH 0/1] configure: Pass CPPFLAGS_FOR_BUILD to subdirectories Tsukasa OI
2022-09-15  5:59 ` [PATCH 1/1] configure: Pass CPPFLAGS_FOR_BUILD to subdirs Tsukasa OI
2022-09-20 12:53   ` Nick Clifton
2022-09-21  5:56     ` Tsukasa OI [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).