From: Laszlo Ersek <lersek@redhat.com>
To: Konrad Rzeszutek Wilk <konrad@kernel.org>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
xen-devel@lists.xenproject.org,
edk2-devel-01 <edk2-devel@ml01.01.org>,
"Jordan Justen (Intel address)" <jordan.l.justen@intel.com>,
Olaf Hering <olaf@aepfle.de>
Subject: Re: [PATCH RESEND] OvmfPkg/build.sh: Use GCC49 toolchain with GCC 6.*
Date: Mon, 21 Nov 2016 21:07:25 +0100 [thread overview]
Message-ID: <9faa1698-7471-3f47-e552-8da23c0f0195@redhat.com> (raw)
In-Reply-To: <CAKv+Gu8+p-fKbaDMJPs4KqQkZTErJT3bXVo3dZ9RDsPhGwEvsQ@mail.gmail.com>
On 11/21/16 17:20, Ard Biesheuvel wrote:
> On 21 November 2016 at 15:56, Konrad Rzeszutek Wilk <konrad@kernel.org> wrote:
>> Without this I cannot build it under Fedora Core 25.
>>
>> Contributed-under: TianoCore Contribution Agreement 1.0
>> Signed-off-by: Konrad Rzeszutek Wilk <konrad@kernel.org>
>> ---
>> OvmfPkg/build.sh | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/OvmfPkg/build.sh b/OvmfPkg/build.sh
>> index eb5eb73..759ade3 100755
>> --- a/OvmfPkg/build.sh
>> +++ b/OvmfPkg/build.sh
>> @@ -95,7 +95,7 @@ case `uname` in
>> 4.8.*)
>> TARGET_TOOLS=GCC48
>> ;;
>> - 4.9.*|4.1[0-9].*|5.*.*)
>> + 4.9.*|4.1[0-9].*|5.*.*|6.*.*)
>> TARGET_TOOLS=GCC49
>> ;;
>> *)
>
> I think it may be time to start using GCC5 for 5.x and later
I agree.
We have an open BZ for this:
https://bugzilla.tianocore.org/show_bug.cgi?id=62
Olaf Hering submitted a patch around June, but the formalities on those
patches weren't right, and Olaf decided not to submit further versions
of the patch.
Here's the idea:
- change the catch-all (*) to GCC5, from GCC44
- remove the (5.*.*) pattern from GCC49
- add a branch (with multiple patterns if necessary) for gcc-4.3 and
earlier to exit with an error message / failure (those compiler
versions are unsupported)
Konrad, can you please submit a v2 with this? If so, please add the tag
Bugzilla: https://bugzilla.tianocore.org/show_bug.cgi?id=62
as well, just before the "Contributed-under:" tag.
(Side note: we haven't been ignoring BZ#62. It's just that after
reviewing Olaf's original patch, implementing the change -- which is
very simple and cannot really be done in different ways -- in his stead
would have practically consisted of replacing Olaf's signoff with
someone elses, and we couldn't do that.)
Thank you,
Laszlo
next prev parent reply other threads:[~2016-11-21 20:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 15:56 [PATCH RESEND] Fix TianoCore building under Fedora Core 25 Konrad Rzeszutek Wilk
2016-11-21 15:56 ` [PATCH RESEND] OvmfPkg/build.sh: Use GCC49 toolchain with GCC 6.* Konrad Rzeszutek Wilk
2016-11-21 16:20 ` Ard Biesheuvel
2016-11-21 20:07 ` Laszlo Ersek [this message]
2016-11-23 2:36 ` [PATCH v2] Compile TianoCore under Fedora Core 25 Konrad Rzeszutek Wilk
2016-11-23 2:36 ` [PATCH v2] OvmfPkg/build.sh: Make GCC5 the default toolchain, catch GCC43 and earlier Konrad Rzeszutek Wilk
2016-11-23 3:37 ` Jordan Justen
2016-11-23 14:55 ` Laszlo Ersek
2016-11-23 14:59 ` Laszlo Ersek
[not found] ` <20161123150126.GA21907@char.us.oracle.com>
2016-11-23 21:08 ` [Xen-devel] " Laszlo Ersek
2016-11-24 1:15 ` PATCH v3] Compile TianoCore under Fedora Core 25 Konrad Rzeszutek Wilk
2016-11-24 1:15 ` [PATCH v3] OvmfPkg/build.sh: Make GCC5 the default toolchain, catch GCC43 and earlier Konrad Rzeszutek Wilk
2016-11-24 8:51 ` 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=9faa1698-7471-3f47-e552-8da23c0f0195@redhat.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