Hi Bret, On 02/12/21 21:49, Bret Barkelew wrote: > This is primarily used by CI builds, but may also be used by platforms. > > Update NASM to support newer structures and features, as agreed in recent > community meetings: > https://edk2.groups.io/g/devel/message/71289 > --- > BaseTools/Bin/nasm_ext_dep.yaml | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/BaseTools/Bin/nasm_ext_dep.yaml b/BaseTools/Bin/nasm_ext_dep.yaml > index 60b1f71b56aa..56703d4c18e7 100644 > --- a/BaseTools/Bin/nasm_ext_dep.yaml > +++ b/BaseTools/Bin/nasm_ext_dep.yaml > @@ -13,6 +13,6 @@ > "type": "nuget", > "name": "mu_nasm", > "source": "https://api.nuget.org/v3/index.json";, > - "version": "2.14.02", > + "version": "2.15.5", > "flags": ["set_path", "host_specific"] > } >
(1) I'm confused by the "patchlevel" number being "5" and not "05", in the "2.15.5" version. Per <https://edk2.groups.io/g/devel/message/71045>, my understanding has been that the latest release is "2.15.05". (2) The minimum required version, according to <https://edk2.groups.io/g/devel/message/71070>, is "2.15.01". In the RHEL build environments that matter to me, I can satisfy a NASM dependency up to 2.15.03, at this time, but not beyond. And this matters because... (3) ... arguably, the NASM requirement in "BaseTools/Conf/tools_def.template" should be updated too, in the same patch: # - NASM 2.10 or later for use with the GCC toolchain family # - NASM 2.12.01 or later for use with all other toolchain families Thanks Laszlo -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#71686): https://edk2.groups.io/g/devel/message/71686 Mute This Topic: https://groups.io/mt/80593990/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
