Today I was unable to build after rebasing. Bug 1509453 prevented this as there is something missing from the config. I'm going to file a patch to disable at least to help others with this issue. Perhaps it's an issue with sccache?
Thanks for the report, I am running a build on Linux to check your error. What are you planning to disable?
Can confirm that I am seeing this issue as well (no sccache).
Installing nasm fixed this for me. Seems there's a check missing.
Er yeah, nasm remained optional until this patch. We should either bail out in configure now, or disable av1 if nasm isn't present.
The Mozilla way is to have configuration independent of the system. That implies the bail out option, requiring the configurer to choose whether to explicitly disable or provide nasm.
I agree. Also, we need to check for nasm >2.13, which is also missing (before it would work with 2.10 or even older). I'll make a patch that checks this and bails out unless you have explicitly disabled all features that require it (currently AV1)
Maybe is a good idea to add nasm configuration in `./mach bootstrap`.
It's already there (let me know if it doesn't work)
Sorry my bad, I should have checked before speak.
My distribution only provides nasm version 2.11.08.
Also require nasm unless av1 is disabled.
This happens for me too, with gcc 8. Adding anything to ./mach bootstrap will not fully solve the problem as that one only works on a few blessed distros. Installing nasm 2.14 (I had none) solves the problem, thanks. Yes, configure should warn if nasm is not installed.
I was able to see this problem and workaround by applying the patch from @jkt to disable ASM. I tried to upgrade my nasm to 2.14 and workaround the problem that way. Unfortunately I could not. That's probably because mach was using the original (older) version of nasm and not taking into account my new $PATH that included the bin directory for the newer nasm. Does anyone know if mach caches the absolute path to nasm? If so, could you tell me how to change that? Sorry for being a newbie!
Yes, it does take the absolute path. You need to rerun ./mach configure to get the new path after your $PATH changes.
Hi Will! It's totally fine to being a newbie! Thanks you for your comment. Has the comment above solved your issue?
(In reply to Alex Chronopoulos [:achronop] from comment #17) > Hi Will! > It's totally fine to being a newbie! Thanks you for your comment. Has the > comment above solved your issue? Thanks for being so kind. After rerunning './mach configure' I was able to build without having to use the patch from jkt. So, it seems like the answer to the problem really is just a modern version of nasm! Thanks again Alex and Thomas! Will
Attachment #9033014 - Attachment description: Bug 1515641 - Check for nasm >= 2.13 in configure. → Bug 1515641 - Check for nasm >= 2.13 for dav1d.
Pushed by email@example.com: https://hg.mozilla.org/integration/autoland/rev/5a8a06e5187c Turn --enable-av1 around. r=nalexander https://hg.mozilla.org/integration/autoland/rev/99cc2de46625 Check for nasm >= 2.13 for dav1d. r=TD-Linux,nalexander
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/9820df609ddf Turn --enable-av1 around. r=nalexander https://hg.mozilla.org/integration/autoland/rev/7b565c75d34b Check for nasm >= 2.13 for dav1d. r=TD-Linux,nalexander
You need to log in before you can comment on or make changes to this bug.