From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Allow CPPFLAGS to be set on the make command line
Date: Tue, 07 Aug 2018 21:25:00 -0000 [thread overview]
Message-ID: <4ba8fcdd331d0d9016b3c4d6a2df5733@polymtl.ca> (raw)
In-Reply-To: <20180807180934.13645-1-tom@tromey.com>
On 2018-08-07 14:09, Tom Tromey wrote:
> While looking into PR build/8751 (which seems to be fixed), I noticed
> that it's not possible to change CPPFLAGS for gdb on the "make"
> command line. It's reasonable to want to do this sometimes, and I
> think this patch should suffice.
>
> gdb/ChangeLog
> 2018-08-07 Tom Tromey <tom@tromey.com>
>
> * Makefile.in (CPPFLAGS): New variable.
> (INTERNAL_CPPFLAGS): Use it.
> ---
> gdb/ChangeLog | 5 +++++
> gdb/Makefile.in | 3 ++-
> 2 files changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/gdb/Makefile.in b/gdb/Makefile.in
> index 8c744d70c0..7ff817d790 100644
> --- a/gdb/Makefile.in
> +++ b/gdb/Makefile.in
> @@ -557,6 +557,7 @@ PROFILE_CFLAGS = @PROFILE_CFLAGS@
> # when running make. I.E.: "make CFLAGS=-Wmissing-prototypes".
> CFLAGS = @CFLAGS@
> CXXFLAGS = @CXXFLAGS@
> +CPPFLAGS = @CPPFLAGS@
>
> # Set by configure, for e.g. expat. Python installations are such
> that
> # C headers are included using their basename (for example, we
> #include
> @@ -564,7 +565,7 @@ CXXFLAGS = @CXXFLAGS@
> # are sometimes a little generic, we think that the risk of collision
> # with other header files is high. If that happens, we try to
> mitigate
> # a bit the consequences by putting the Python includes last in the
> list.
> -INTERNAL_CPPFLAGS = @CPPFLAGS@ @GUILE_CPPFLAGS@ @PYTHON_CPPFLAGS@
> +INTERNAL_CPPFLAGS = $(CPPFLAGS) @GUILE_CPPFLAGS@ @PYTHON_CPPFLAGS@
>
> # INTERNAL_CFLAGS is the aggregate of all other *CFLAGS macros.
> INTERNAL_CFLAGS_BASE = \
+1.
Simon
prev parent reply other threads:[~2018-08-07 21:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 18:10 Tom Tromey
2018-08-07 21:25 ` Simon Marchi [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=4ba8fcdd331d0d9016b3c4d6a2df5733@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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