Our great sponsors
-
fossa-cli
Fast, portable and reliable dependency analysis for any codebase. Supports license & vulnerability scanning for large monoliths. Language-agnostic; integrates with 20+ build systems.
-
binaryen
Discontinued DEPRECATED in favor of ghc wasm backend, see https://www.tweag.io/blog/2022-11-22-wasm-backend-merged-in-ghc
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
The project I'm trying to build is open source (https://github.com/fossas/fossa-cli). When I got this new system set up, I ran the instructions on our HACKING.md page and immediately tried to build. This failed because I didn't have `llvm` installed, so I `brew install llvm`'d, symlinked into `$PATH`, and tried again. This failed due to: ``` install_name_tool: error: unsupported load command (cmd=0x80000034) `install_name_tool' failed in phase `Install Name Tool'. (Exit code: 1)
We found a post where someone had a similar issue (here), but the fix in that issue doesn't help: using `ar` from `binutils` causes link errors like this instead:
As for "install name tool" part, I got the same error trying to build https://github.com/mkloczko/derive-storable on M1 Mac, and it turned out I had llvm 13 (which is default llvm in homebrew). In my case, uninstalling it and installing llvm@12 instead solved the issue immediately (had to do "cabal clean" though).
Related posts
- Content based change detection with Make
- Building problems for using `Asterius` to compile Haskell to Webassembly.
- hint: Runtime Haskell interpreter
- Pandoc in the browser w/ lua (possible contract gig?)
- It seems like every top tier team I work in insists on Yarn over NPM, almost unanimously it seems like all of these killer devs know Yarn is the industry standard on serious projects. Why do all documentation across the web default to npm installation instructions and assume you're using npm?