New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build error with clang on Mac OS X 10.15.7 (wasm-engine.cc:157:19: error: no viable overloaded '=') #52847
Comments
macOS 10.15 is no longer supported to build node. We require at least macOS 11. |
To me it seems like the build error might not be specific to OS X 10.15. |
It's specific to the clang version that ships with Xcode on 10.15 |
Assuming I fixed that locally and put it under a platform-specific |
I am experiencing something similar on Mac OS 11.7.10 I'm building v22.1 via Homebrew (I'm aware that Homebrew no longer officially supports this OS version) Clang: 13.0.0 build 1300
|
Does this need to be reported upstream to the maintainers of v8 or to what extent is the version bundled with nodejs up-to-date with that? |
Official macOS releases are built with Xcode 13.2.1 too and we don't get this error 🤔 |
Had similar issue to @ireddick -- install node v22.1 from source via homebrew on macOS 11 failed, re: wasm-engine Clang="Apple clang version 13.0.0 (clang-1300.0.29.30)" Error: node "make install" step failing on wasm-engine.o:
Workaround (sufficient for my needs): revert to older node version in homebrew: node@20 (ref), build/install completed without error |
I'm getting a similar error when using brew to upgrade node:
Clang="Apple clang version 13.0.0 (clang-1300.0.29.30)" |
Version
v22.1
Platform
Darwin Tobiass-MBP-2.fritz.box 19.6.0 Darwin Kernel Version 19.6.0: Tue Jun 21 21:18:39 PDT 2022; root:xnu-6153.141.66~1/RELEASE_X86_64 x86_64
Subsystem
No response
What steps will reproduce the bug?
Try to install node on Mac OS X
How often does it reproduce? Is there a required condition?
every time
What is the expected behavior? Why is that the expected behavior?
Build does not fail.
What do you see instead?
Additional information
No response
The text was updated successfully, but these errors were encountered: