From: Nick Clifton <nickc@redhat.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>,
Jim Wilson <wilson@tuliptree.org>
Cc: binutils@sourceware.org
Subject: Re: [PATCH 1/1] configure: Pass CPPFLAGS_FOR_BUILD to subdirs
Date: Tue, 20 Sep 2022 13:53:25 +0100 [thread overview]
Message-ID: <459fb3e2-e4fe-54eb-22b0-19f1a90ae6d1@redhat.com> (raw)
In-Reply-To: <ba9607eb1b1ef3f5adb5f396ae72956c663475e0.1663221557.git.research_trasio@irq.a4lg.com>
Hi Tsukasa,
> ChangeLog:
>
> * configure.ac: 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
next prev parent reply other threads:[~2022-09-20 12:53 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 [this message]
2022-09-21 5:56 ` Tsukasa OI
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=459fb3e2-e4fe-54eb-22b0-19f1a90ae6d1@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=research_trasio@irq.a4lg.com \
--cc=wilson@tuliptree.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).