From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: anthony.perard@citrix.com, xen-devel@lists.xensource.com,
wei.liu2@citrix.com
Subject: [lersek@redhat.com: Re: [PATCH v3] OvmfPkg/build.sh: Make GCC5 the default toolchain, catch GCC43 and earlier]
Date: Fri, 25 Nov 2016 08:24:00 -0500 [thread overview]
Message-ID: <20161125132400.GD24445@char.us.oracle.com> (raw)
Hey Wei, Anthony,
Are you guys OK pushing this commit: 2667ad40919a in the
git://xenbits.xen.org/ovmf.git
tree? Without this I cannot build Xen 4.8 with TianoCore
(--enable-ovmf).
Thanks.
----- Forwarded message from Laszlo Ersek <lersek@redhat.com> -----
Date: Thu, 24 Nov 2016 09:51:29 +0100
From: Laszlo Ersek <lersek@redhat.com>
To: Konrad Rzeszutek Wilk <konrad@kernel.org>, edk2-devel@ml01.01.org
Cc: xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] [PATCH v3] OvmfPkg/build.sh: Make GCC5 the default toolchain, catch GCC43 and earlier
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.0
On 11/24/16 02:15, Konrad Rzeszutek Wilk wrote:
> v2:
> * Changes suggested by Laszlo:
> - change the catch-all (*) to GCC5, from GCC44
> - remove the (5.*.*) pattern from GCC49
> - generate error for GCC < 4.4
>
> In v3, also generate error for really GCC < 4.4, like GCC 1.
>
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
> Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
> Bugzilla: https://bugzilla.tianocore.org/show_bug.cgi?id=62
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Konrad Rzeszutek Wilk <konrad@kernel.org>
> ---
> v1: Initial
> v2: Redo it per Laszlo suggestions
> v3: Fix up commit message per Jordan
> Also generate error for prehistoric versions of GCC, like 1.
> ---
> OvmfPkg/build.sh | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/OvmfPkg/build.sh b/OvmfPkg/build.sh
> index eb5eb73..95fe8fb 100755
> --- a/OvmfPkg/build.sh
> +++ b/OvmfPkg/build.sh
> @@ -83,6 +83,13 @@ case `uname` in
> Linux*)
> gcc_version=$(gcc -v 2>&1 | tail -1 | awk '{print $3}')
> case $gcc_version in
> + [1-3].*|4.[0-3].*)
> + echo OvmfPkg requires GCC4.4 or later
> + exit 1
> + ;;
> + 4.4.*)
> + TARGET_TOOLS=GCC44
> + ;;
> 4.5.*)
> TARGET_TOOLS=GCC45
> ;;
> @@ -95,11 +102,11 @@ case `uname` in
> 4.8.*)
> TARGET_TOOLS=GCC48
> ;;
> - 4.9.*|4.1[0-9].*|5.*.*)
> + 4.9.*)
> TARGET_TOOLS=GCC49
> ;;
> *)
> - TARGET_TOOLS=GCC44
> + TARGET_TOOLS=GCC5
> ;;
> esac
> esac
>
Tested-by: Laszlo Ersek <lersek@redhat.com>
(With gcc-4.8.)
Pushed as commit 2667ad40919a.
Thank you!
Laszlo
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
----- End forwarded message -----
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next reply other threads:[~2016-11-25 13:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 13:24 Konrad Rzeszutek Wilk [this message]
2016-11-25 13:51 ` [lersek@redhat.com: Re: [PATCH v3] OvmfPkg/build.sh: Make GCC5 the default toolchain, catch GCC43 and earlier] Wei Liu
2016-11-25 17:04 ` Konrad Rzeszutek Wilk
2016-11-29 4:34 ` Wei Liu
2016-11-28 12:38 ` Anthony PERARD
2016-11-28 15:03 ` Konrad Rzeszutek Wilk
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=20161125132400.GD24445@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=anthony.perard@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).