From: Anthony PERARD <anthony.perard@citrix.com>
To: <xen-devel@lists.xenproject.org>
Cc: Roger Pau Monne <roger.pau@citrix.com>, Ian Jackson <iwj@xenproject.org>
Subject: Re: [OSSTEST PATCH] ts-xen-build-prep: Grab newer NASM version, to build OVMF
Date: Fri, 13 May 2022 14:43:38 +0100 [thread overview]
Message-ID: <Yn5git1z9Xfz5HwM@perard.uk.xensource.com> (raw)
In-Reply-To: <20220513133534.88564-1-anthony.perard@citrix.com>
On Fri, May 13, 2022 at 02:35:34PM +0100, Anthony PERARD wrote:
> Recent versions of OVMF now need a version of NASM that is newer
> than the one available on Debian oldstable/buster. They want to use
> NASM 2.15.05 [1], which is available in Debian stable/bullseye. The
> need to use a newer version started with d3febfd9ade3 ("MdePkg:
> Replace Opcode with the corresponding instructions.").
>
> There is no backport package available but the nasm package from
> Debian Bullseye can easily be installed on Buster as it has few
> dependencies and are already satisfied.
>
> [1] https://github.com/tianocore/edk2/commit/6a890db161cd6d378bec3499a1e774db3f5a27a7
> ("BaseTools: Upgrade the version of NASM tool")
>
> Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
A flight with my change:
http://logs.test-lab.xenproject.org/osstest/logs/170388/
(ignore the failing "libvirt-build" jobs which shouldn't be part
of the flight ;-) )
--
Anthony PERARD
next prev parent reply other threads:[~2022-05-13 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 13:35 [OSSTEST PATCH] ts-xen-build-prep: Grab newer NASM version, to build OVMF Anthony PERARD
2022-05-13 13:43 ` Anthony PERARD [this message]
2022-05-13 14:39 ` Roger Pau Monné
2022-05-13 21:16 ` Ian Jackson
2022-05-13 21:15 ` Ian Jackson
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=Yn5git1z9Xfz5HwM@perard.uk.xensource.com \
--to=anthony.perard@citrix.com \
--cc=iwj@xenproject.org \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.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.