From: Laszlo Ersek <lersek@redhat.com>
To: Jordan Justen <jordan.l.justen@intel.com>, edk2-devel@lists.01.org
Subject: Re: [PATCH 2/2] EmulatorPkg/build.sh: Merge GCC toolchain detection from OVMF
Date: Fri, 2 Jun 2017 23:50:23 +0200 [thread overview]
Message-ID: <e6e054df-b720-c188-d798-d96f0a56eb0a@redhat.com> (raw)
In-Reply-To: <20170601235640.25540-2-jordan.l.justen@intel.com>
On 06/02/17 01:56, Jordan Justen wrote:
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Jordan Justen <jordan.l.justen@intel.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> ---
> EmulatorPkg/build.sh | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff --git a/EmulatorPkg/build.sh b/EmulatorPkg/build.sh
> index 7f74391120..a196c3e9f3 100755
> --- a/EmulatorPkg/build.sh
> +++ b/EmulatorPkg/build.sh
> @@ -93,6 +93,13 @@ case `uname` in
>
> 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
This should say EmulatorPkg, not OvmfPkg.
With that fixed:
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Thanks
Laszlo
> + exit 1
> + ;;
> + 4.4.*)
> + TARGET_TOOLS=GCC44
> + ;;
> 4.5.*)
> TARGET_TOOLS=GCC45
> ;;
> @@ -105,11 +112,11 @@ case `uname` in
> 4.8.*)
> TARGET_TOOLS=GCC48
> ;;
> - 4.9.*|4.1[0-9].*|5.*.*)
> + 4.9.*|6.[0-2].*)
> TARGET_TOOLS=GCC49
> ;;
> *)
> - TARGET_TOOLS=GCC44
> + TARGET_TOOLS=GCC5
> ;;
> esac
> ;;
>
next prev parent reply other threads:[~2017-06-02 21:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 23:56 [PATCH 1/2] EmulatorPkg/Unix/Host: Add GCC5 CC/DLINK commands (for GCC >= 5) Jordan Justen
2017-06-01 23:56 ` [PATCH 2/2] EmulatorPkg/build.sh: Merge GCC toolchain detection from OVMF Jordan Justen
2017-06-02 21:50 ` Laszlo Ersek [this message]
2017-06-02 9:03 ` [PATCH 1/2] EmulatorPkg/Unix/Host: Add GCC5 CC/DLINK commands (for GCC >= 5) Ard Biesheuvel
2017-06-02 21:48 ` Laszlo Ersek
2017-06-05 18:33 ` Jordan Justen
2017-06-06 11:10 ` Ard Biesheuvel
2017-06-06 17:18 ` 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=e6e054df-b720-c188-d798-d96f0a56eb0a@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