From: "Lendacky, Thomas" <thomas.lendacky@amd.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Build failure
Date: Tue, 8 Mar 2022 08:08:02 -0600 [thread overview]
Message-ID: <804a68cb-4860-5964-93e8-2220c60340b8@amd.com> (raw)
Is there a new minimum version of NASM required for the build? The
following commit causes the build to fail on my Ubuntu 20.04 system:
d3febfd9ade3 ("MdePkg: Replace Opcode with the corresponding instructions.")
Specifically the opcode changes in LongJump.nasm:
/root/kernels/ovmf-build-X64/Build/OvmfX64/DEBUG_GCC5/X64/MdePkg/Library/BaseLib/BaseLib/OUTPUT/X64/LongJump.iii:44: error: parser: instruction expected
/root/kernels/ovmf-build-X64/Build/OvmfX64/DEBUG_GCC5/X64/MdePkg/Library/BaseLib/BaseLib/OUTPUT/X64/LongJump.iii:49: error: parser: instruction expected
make: *** [GNUmakefile:742: /root/kernels/ovmf-build-X64/Build/OvmfX64/DEBUG_GCC5/X64/MdePkg/Library/BaseLib/BaseLib/OUTPUT/X64/LongJump.obj] Error 1
The most recent NASM version available on Ubuntu 20.04 is:
# nasm -v
NASM version 2.14.02
Thanks,
Tom
next reply other threads:[~2022-03-08 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 14:08 Lendacky, Thomas [this message]
2022-03-08 15:47 ` [edk2-devel] Build failure Michael D Kinney
2022-03-08 16:35 ` Vincent Zimmer
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=804a68cb-4860-5964-93e8-2220c60340b8@amd.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