public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: "Gao, Liming" <liming.gao@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	 "leif.lindholm@linaro.org" <leif.lindholm@linaro.org>,
	"Zhu, Yonghong" <yonghong.zhu@intel.com>
Subject: Re: [PATCH] BaseTools/tools_def: suppress GCC predefined macros in DTB compilation
Date: Tue, 31 Oct 2017 08:27:07 +0000	[thread overview]
Message-ID: <CAKv+Gu_h9zyw+3XB0xSxfOGsGgLCPZoGO78hy3=D43OfeNejBA@mail.gmail.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E175A32@SHSMSX104.ccr.corp.intel.com>

On 31 October 2017 at 05:41, Gao, Liming <liming.gao@intel.com> wrote:
> Ard:
>   I have no other comments.
>
> Reviewed-by: Liming Gao <liming.gao@intel.com>
>

Thanks. I already pushed this as 8512fc5731df



>>-----Original Message-----
>>From: Ard Biesheuvel [mailto:ard.biesheuvel@linaro.org]
>>Sent: Thursday, October 26, 2017 6:12 PM
>>To: edk2-devel@lists.01.org
>>Cc: leif.lindholm@linaro.org; Gao, Liming <liming.gao@intel.com>; Zhu,
>>Yonghong <yonghong.zhu@intel.com>; Ard Biesheuvel
>><ard.biesheuvel@linaro.org>
>>Subject: [PATCH] BaseTools/tools_def: suppress GCC predefined macros in
>>DTB compilation
>>
>>The standard GCC preprocessor we use to preprocess device tree sources
>>files has a whole bunch of macros predefined, among which
>>
>>This causes a property like 'linux,code' to be converted into '1,code'
>>which is obviously wrong. So let's get rid of all the predefined macros
>>by passing -undef to the preprocessor command line.
>>
>>Contributed-under: TianoCore Contribution Agreement 1.1
>>Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>>---
>> BaseTools/Conf/tools_def.template | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>>diff --git a/BaseTools/Conf/tools_def.template
>>b/BaseTools/Conf/tools_def.template
>>index df7c109438fd..98df0ffc9294 100755
>>--- a/BaseTools/Conf/tools_def.template
>>+++ b/BaseTools/Conf/tools_def.template
>>@@ -4369,7 +4369,7 @@ DEFINE GCC_VFRPP_FLAGS             = -x c -E -P -
>>DVFRCOMPILE --include $(DEST_DI
>> DEFINE GCC_ASLPP_FLAGS             = -x c -E -include AutoGen.h
>> DEFINE GCC_ASLCC_FLAGS             = -x c
>> DEFINE GCC_WINDRES_FLAGS           = -J rc -O coff
>>-DEFINE GCC_DTCPP_FLAGS             = -E -x assembler-with-cpp -imacros
>>$(DEST_DIR_DEBUG)/AutoGen.h -nostdinc
>>+DEFINE GCC_DTCPP_FLAGS             = -E -x assembler-with-cpp -imacros
>>$(DEST_DIR_DEBUG)/AutoGen.h -nostdinc -undef
>> DEFINE GCC_IA32_RC_FLAGS           = -I binary -O elf32-i386          -B i386    --
>>rename-section .data=.hii
>> DEFINE GCC_X64_RC_FLAGS            = -I binary -O elf64-x86-64        -B i386    --
>>rename-section .data=.hii
>> DEFINE GCC_IPF_RC_FLAGS            = -I binary -O elf64-ia64-little   -B ia64    --
>>rename-section .data=.hii
>>--
>>2.11.0
>


      reply	other threads:[~2017-10-31  8:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26 10:12 [PATCH] BaseTools/tools_def: suppress GCC predefined macros in DTB compilation Ard Biesheuvel
2017-10-26 11:09 ` Laszlo Ersek
2017-10-26 11:11   ` Ard Biesheuvel
2017-10-26 11:33     ` Leif Lindholm
2017-10-26 11:34       ` Ard Biesheuvel
2017-10-26 15:08         ` Laszlo Ersek
2017-10-31  5:41 ` Gao, Liming
2017-10-31  8:27   ` Ard Biesheuvel [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-list 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='CAKv+Gu_h9zyw+3XB0xSxfOGsGgLCPZoGO78hy3=D43OfeNejBA@mail.gmail.com' \
    --to=devel@edk2.groups.io \
    /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