Code signature invalid with macOS wasm-opt binary
Closed this issue · 1 comments
nth10sd commented
dyld[26929]: Library not loaded: @rpath/libbinaryen.dylib
Referenced from: <42040B09-76A3-3DB4-8F71-C8EF82F00CA7> <path to>/binaryen-version_117/bin/wasm-opt
Reason: tried: '<path to>/binaryen-version_117/bin/../lib/libbinaryen.dylib' (code signature invalid in <B80FB249-B408-39F4-B9C8-BDD1CA140B7E> '<path to>/binaryen-version_117/lib/libbinaryen.dylib' (errno=85) sliceOffset=0x00000000, codeBlobOffset=0x0125B5D0, codeBlobSize=0x00024C00), '<path to>/binaryen-version_117/bin/../lib/libbinaryen.dylib' (code signature invalid in <B80FB249-B408-39F4-B9C8-BDD1CA140B7E> '<path to>/binaryen-version_117/lib/libbinaryen.dylib' (errno=85) sliceOffset=0x00000000, codeBlobOffset=0x0125B5D0, codeBlobSize=0x00024C00), '/usr/local/lib/libbinaryen.dylib' (no such file), '/usr/lib/libbinaryen.dylib' (no such file, not in dyld cache)
(note that paths were changed slightly)
I'm not sure if this is my issue, or with the releases. Version 117 on macOS 14.5 seems to occasionally show this code signature invalid
issue when I run wasm-opt
from the tarball downloaded off GitHub. This happens when I run wasm-opt
via a subprocess.run
call in a Python script.
nth10sd commented
I fixed it, I was probably spawning too many instances of wasm-opt
at the same time...