From: Ian Campbell <ian.campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, ard.biesheuvel@linaro.org
Subject: Re: [PATCH] raisin: enable ovmf build for arm64
Date: Tue, 13 Oct 2015 12:03:48 +0100 [thread overview]
Message-ID: <1444734228.23192.45.camel@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1510131154490.1179@kaball.uk.xensource.com>
On Tue, 2015-10-13 at 11:58 +0100, Stefano Stabellini wrote:
> On Tue, 13 Oct 2015, Ian Campbell wrote:
> > On Mon, 2015-10-12 at 18:18 +0100, Stefano Stabellini wrote:
> > > @@ -30,9 +38,18 @@ function ovmf_build() {
> > > git-checkout $OVMF_URL $OVMF_REVISION ovmf-dir
> > > cd ovmf-dir
> > >
> > > - make -C BaseTools/Source/C
> > > - OvmfPkg/build.sh -a X64 -b RELEASE -n 4
> > > - cp Build/OvmfX64/RELEASE_GCC*/FV/OVMF.fd ovmf.bin
> > > + make -C BaseTools
> > > +
> > > + if [[ $RAISIN_ARCH = "arm64" ]]
> >
> > Based on what I understand of the OVMF buildsystem I think you are
> > going to
> > eventually want a case $RAISIN_ARCH here, since it seems to vary a fair
> > bit.
> >
> > > + then
> > > + export GCC48_AARCH64_PREFIX=
> >
> > Won't this (unexpectedly) leak into other subsequent component builds?
> > Or
> > is each component built in a fresh sub-shell?
> >
> > What about host platforms which have a gcc other than 4.8? (e.g. Debian
> > Jessie uses 4.9 by default)
> >
> > Should you add a comment explaining why this apparent workaround is
> > needed?
>
> That is a good question. It all comes from
> https://wiki.linaro.org/LEG/UEFIforXEN, but I don't know why is
> required. Without GCC48_AARCH64_PREFIX= and -t GCC48, it won't build.
Is it just that GCC48_AARCH64_PREFIX defaults to some cross-compiler prefix
(e.g. aarch64-linux-gnu-) but a native build environment doesn't (always)
use that?
On Debian at least the prefixed name exists even for the native compiler,
but I'd not be surprised if that wasn't universal across all distros.
> Ard, do you know why? x86 doesn't need anything like that, as you can
> see below.
>
>
> > > + bash -c "source edksetup.sh && build -a AARCH64 -t GCC48 -p
> > > ArmVirtPkg/ArmVirtXen.dsc -b RELEASE"
> > > + mkdir -p "$INST_DIR"/$PREFIX/lib/xen/boot
> > > + cp Build/ArmVirtXen-AARCH64/RELEASE_GCC*/FV/XEN_EFI.fd
> > > "$INST_DIR"/$PREFIX/lib/xen/boot/XEN_EFI.fd
> > > + else
> > > + OvmfPkg/build.sh -a X64 -b RELEASE -n 4
> > > + cp Build/OvmfX64/RELEASE_GCC*/FV/OVMF.fd ovmf.bin
> > > + fi
> > >
> > > cd "$BASEDIR"
> > > }
> > >
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@lists.xen.org
> > > http://lists.xen.org/xen-devel
> >
next prev parent reply other threads:[~2015-10-13 11:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 17:18 [PATCH] raisin: enable ovmf build for arm64 Stefano Stabellini
2015-10-13 10:41 ` Ian Campbell
2015-10-13 10:58 ` Stefano Stabellini
2015-10-13 11:03 ` Ian Campbell [this message]
2015-10-13 11:24 ` Julien Grall
2015-10-13 12:49 ` Stefano Stabellini
2015-10-13 13:00 ` Ian Campbell
2015-10-13 13:16 ` Julien Grall
2015-10-13 13:18 ` Stefano Stabellini
2015-10-13 13:31 ` Julien Grall
2015-10-13 13:41 ` Stefano Stabellini
2015-10-13 13:43 ` Ard Biesheuvel
2015-10-13 13:48 ` Stefano Stabellini
2015-10-13 14:02 ` Ard Biesheuvel
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=1444734228.23192.45.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ard.biesheuvel@linaro.org \
--cc=stefano.stabellini@eu.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 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.