Re: NASM-3.00 causes build failures, recommend downgrading

On 10/5/25 7:34 PM, Zeckma ([email protected] via blfs-dev Mailing 
List) wrote:
> Hello everyone.
>
> We have a problem with NASM-3.00. It is currently in the development
> books of BLFS. 3.00 made changes that affects packages like dav1d and
> libaom. I haven't tried packages besides those, but the scope may be
> bigger, I don't know quite yet.
>
> For dav1d, the assembly files have operands in an order that NASM-3.00
> forced to be the other way according to the specification. This causes
> dav1d to fail to build from source.
>
> In libaom's case, it fails to even configure via CMake as the NASM is
> unsupported. This is because the build system uses NASM's help output,
> in which it was changed. It expects all the supported options and build
> targets to be shown with the current options -hf. The problem is now
> the options it wants to see plus the build targets have been split up.
> Now, it would want -h0 plus -hf, which cannot be ran in the same
> command.
>
> Lack of energy and time, I see it as a good idea to simply downgrade
> NASM to 2.x.x until these issues in other packages have been fixed.
>
> Apologies to anyone who installed NASM-3.00 as a result of it being in
> the development books. I heavily recommend to downgrade to NASM-2.16.03
> to prevent build failures.

What would be the reason for downgrading? It's a DEVELOPMENT version of 
the book and this is where issues like this should be detected and fixed 
or reported upstream.

-- 
http://lists.linuxfromscratch.org/sympa/info/blfs-dev
Unsubscribe: See the above information page