From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "Gao, Liming" <liming.gao@intel.com>,
edk2-devel-01 <edk2-devel@lists.01.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Cole Robinson <crobinso@redhat.com>
Subject: Re: [PATCH 0/3] BaseTools: let the C-language build utils compile with gcc-8
Date: Wed, 7 Mar 2018 09:12:19 +0000 [thread overview]
Message-ID: <CAKv+Gu_EvN7fdv4zkVKwef4Wrgqsgdp=z6vso_bH6O4xCQh3BA@mail.gmail.com> (raw)
In-Reply-To: <e63da203-3f79-4e2f-8e2b-cb37a0d9f718@redhat.com>
On 7 March 2018 at 09:11, Laszlo Ersek <lersek@redhat.com> wrote:
> On 03/07/18 07:43, Gao, Liming wrote:
>> Laszlo:
>> We just find this change causes XCODE5 build failure, because XCODE compiler doesn't know these two options. So, could you provide the patch to remove the change in BUILD_CFLAGS for MAC?
>
> Yep, I was a bit concerned about that.
>
> Ultimately I assumed that
> - clang would either recognize these warnings options (because it does
> recognize most -W options of gcc),
> - or, similarly to gcc, clang would simply ignore -Wno-* flags that it
> does not recognize.
>
> Neither appears to be the case, then. I'll send a patch soon.
>
What is the reason we don't pass -Wno-unknown-warning-option to XCODE ?
next prev parent reply other threads:[~2018-03-07 9:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 18:09 [PATCH 0/3] BaseTools: let the C-language build utils compile with gcc-8 Laszlo Ersek
2018-03-02 18:09 ` [PATCH 1/3] BaseTools/header.makefile: add "-Wno-stringop-truncation" Laszlo Ersek
2018-03-02 18:09 ` [PATCH 2/3] BaseTools/header.makefile: add "-Wno-restrict" Laszlo Ersek
2018-03-02 18:09 ` [PATCH 3/3] BaseTools/GenVtf: silence false "stringop-overflow" warning with memcpy() Laszlo Ersek
2018-03-05 14:13 ` [PATCH 0/3] BaseTools: let the C-language build utils compile with gcc-8 Gao, Liming
2018-03-05 21:41 ` Laszlo Ersek
2018-03-07 6:43 ` Gao, Liming
2018-03-07 9:11 ` Laszlo Ersek
2018-03-07 9:12 ` Ard Biesheuvel [this message]
2018-03-07 20:26 ` Laszlo Ersek
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_EvN7fdv4zkVKwef4Wrgqsgdp=z6vso_bH6O4xCQh3BA@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