public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tsukasa OI <a4lg@sourceware.org>
To: bfd-cvs@sourceware.org, gdb-cvs@sourceware.org
Subject: [binutils-gdb] configure: Pass CPPFLAGS_FOR_BUILD to subdirs
Date: Wed, 21 Sep 2022 06:16:28 +0000 (GMT)	[thread overview]
Message-ID: <20220921061628.641DA38582BC@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e472ec9fad6d7b0da914da606430e249d1bd99e4

commit e472ec9fad6d7b0da914da606430e249d1bd99e4
Author: Tsukasa OI <research_trasio@irq.a4lg.com>
Date:   Wed Sep 14 12:28:02 2022 +0000

    configure: Pass CPPFLAGS_FOR_BUILD to subdirs
    
    Because CPPFLAGS_FOR_BUILD is used in some subdirectories (through
    bfd/warning.m4), not AC_SUBSTing the variable causes minor issues.
    
    Fortunately, it didn't cause severe errors but error messages related to
    @CPPFLAGS_FOR_BUILD@ (not AC_SUBSTed CPPFLAGS_FOR_BUILD variable passed
    to subdirectories through Makefile) remain in config.log.
    
    To avoid invalid invocation of preprocessor for build environment, we
    need to set proper CPPFLAGS_FOR_BUILD (may be empty) and pass it to
    subdirectories that need it.  This is what this commit does.
    
    ChangeLog:
    
            * configure.ac: Pass CPPFLAGS_FOR_BUILD to subdirectories.
            * configure: Regenerate.

Diff:
---
 configure    | 3 +++
 configure.ac | 2 ++
 2 files changed, 5 insertions(+)

diff --git a/configure b/configure
index 16139e3bfa3..d75f47a1e95 100755
--- a/configure
+++ b/configure
@@ -651,6 +651,7 @@ GFORTRAN_FOR_BUILD
 DLLTOOL_FOR_BUILD
 CXX_FOR_BUILD
 CXXFLAGS_FOR_BUILD
+CPPFLAGS_FOR_BUILD
 CFLAGS_FOR_BUILD
 CC_FOR_BUILD
 AS_FOR_BUILD
@@ -8024,6 +8025,7 @@ esac
 # our build compiler if desired.
 if test x"${build}" = x"${host}" ; then
   CFLAGS_FOR_BUILD=${CFLAGS_FOR_BUILD-${CFLAGS}}
+  CPPFLAGS_FOR_BUILD=${CPPFLAGS_FOR_BUILD-${CPPFLAGS}}
   CXXFLAGS_FOR_BUILD=${CXXFLAGS_FOR_BUILD-${CXXFLAGS}}
   LDFLAGS_FOR_BUILD=${LDFLAGS_FOR_BUILD-${LDFLAGS}}
 fi
@@ -8102,6 +8104,7 @@ done
 
 
 
+
 # Generate default definitions for YACC, M4, LEX and other programs that run
 # on the build machine.  These are used if the Makefile can't locate these
 # programs in objdir.
diff --git a/configure.ac b/configure.ac
index a5555a9c91b..ae18d436aca 100644
--- a/configure.ac
+++ b/configure.ac
@@ -3326,6 +3326,7 @@ esac
 # our build compiler if desired.
 if test x"${build}" = x"${host}" ; then
   CFLAGS_FOR_BUILD=${CFLAGS_FOR_BUILD-${CFLAGS}}
+  CPPFLAGS_FOR_BUILD=${CPPFLAGS_FOR_BUILD-${CPPFLAGS}}
   CXXFLAGS_FOR_BUILD=${CXXFLAGS_FOR_BUILD-${CXXFLAGS}}
   LDFLAGS_FOR_BUILD=${LDFLAGS_FOR_BUILD-${LDFLAGS}}
 fi
@@ -3392,6 +3393,7 @@ AC_SUBST(AR_FOR_BUILD)
 AC_SUBST(AS_FOR_BUILD)
 AC_SUBST(CC_FOR_BUILD)
 AC_SUBST(CFLAGS_FOR_BUILD)
+AC_SUBST(CPPFLAGS_FOR_BUILD)
 AC_SUBST(CXXFLAGS_FOR_BUILD)
 AC_SUBST(CXX_FOR_BUILD)
 AC_SUBST(DLLTOOL_FOR_BUILD)

                 reply	other threads:[~2022-09-21  6:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220921061628.641DA38582BC@sourceware.org \
    --to=a4lg@sourceware.org \
    --cc=bfd-cvs@sourceware.org \
    --cc=gdb-cvs@sourceware.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).