Don't call 'nasm /?' at cmake call time.
The bug is originally reported as:
- https://bugs.gentoo.org/670944
- https://bugzilla.nasm.us/show_bug.cgi?id=3392529
- https://github.com/libjpeg-turbo/libjpeg-turbo/issues/332
The problem:
cmake calls nasm
with unsupported /?
option. On some versions of nasm this leads to '/?' file to be created. In a sandboxed environment this triggers out-of-sandbox access violation and build failure.
It looks like the problem stems from https://github.com/libjpeg-turbo/libjpeg-turbo/blob/4f943644e5bf7544f126ce1d23e430e649a82c41/simd/CMakeLists.txt#L41 where enable_language(ASM_NASM)
is called.
nasm
maintainer suggests not to pass unsupported arguments to nasm.
libjpeg-turbo
maintainer suggests it's a cmake
deficiency.
Thanks!