From: Julien Grall <julien.grall@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH v3] raisin: enable ovmf build for arm64
Date: Fri, 16 Oct 2015 19:39:34 +0100 [thread overview]
Message-ID: <56214466.6040003@citrix.com> (raw)
In-Reply-To: <1444995779-29218-1-git-send-email-stefano.stabellini@eu.citrix.com>
On 16/10/15 12:42, Stefano Stabellini wrote:
> function ovmf_check_package() {
> - local DEP_Debian_common="build-essential nasm uuid-dev python iasl"
> - local DEP_Debian_x86_32="$DEP_Debian_common"
> - local DEP_Debian_x86_64="$DEP_Debian_common"
> - local DEP_Debian_arm32="$DEP_Debian_common"
> + local DEP_Debian_common="build-essential uuid-dev python iasl"
> + local DEP_Debian_x86_32="$DEP_Debian_common nasm"
> + local DEP_Debian_x86_64="$DEP_Debian_x86_32"
> local DEP_Debian_arm64="$DEP_Debian_common"
>
> - local DEP_Fedora_common="make gcc gcc-c++ nasm libuuid-devel python acpica-tools"
> - local DEP_Fedora_x86_32="$DEP_Fedora_common"
> - local DEP_Fedora_x86_64="$DEP_Fedora_common"
> + local DEP_Fedora_common="make gcc gcc-c++ libuuid-devel python acpica-tools"
> + local DEP_Fedora_x86_32="$DEP_Fedora_common nasm"
> + local DEP_Fedora_x86_64="$DEP_Fedora_x86_32"
> + local DEP_Fedora_arm64="$DEP_Debian_common"
Shouldn't it be $DEP_Fedora_common here?
> +
> + local DEP_CentOS_common="$DEP_Fedora_common"
> + local DEP_CentOS_x86_32="$DEP_Fedora_x86_32"
> + local DEP_CentOS_x86_64="$DEP_Fedora_x86_64"
> + local DEP_CentOS_arm64="$DEP_Fedora_arm64"
It's bit strange to introduce DEP_CentOS_* in a patch which only enable
ARM64. Is it intentional?
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-10-16 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 11:42 [PATCH v3] raisin: enable ovmf build for arm64 Stefano Stabellini
2015-10-16 18:39 ` Julien Grall [this message]
2015-10-19 15:18 ` Stefano Stabellini
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=56214466.6040003@citrix.com \
--to=julien.grall@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.