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
dyld: Symbol not found: _clock_gettime #1278
Comments
I googled this for you and this was the first result: https://stackoverflow.com/questions/66741383/dyld-symbol-not-found-clock-gettime-after-installing-golang. It sounds like you are using an unsupported version of macOS. You will either have to upgrade your operating system or install the WebAssembly version to use esbuild: https://esbuild.github.io/getting-started/#wasm. |
Closing since esbuild is not supported on this platform. Workarounds are described above. |
That happened to me as well. I'm on macOS v10.11.6. Unfortunately my current hardware cannot support a more modern version.
I've tried the alternative WASM version. But no luck so far.
Are there more steps I should follow in order to make this work? Thanks in advance. |
The platforms that esbuild currently supports are the same platforms that Go currently supports since esbuild is written in Go. The latest version of Go (1.17) only supports macOS 10.13 or higher (released in 2017). The WASM version should work since WASM is platform-independent and presumably node's WASM support for macOS 10.11 works. That's the approach I'd recommend. What does "no luck so far" mean? Do you get an error? If you really want to use the native version of esbuild, you could try building from source using Go version 1.14 (the last version to support macOS 10.11). |
I'm trying to develop and compile an Angular12 project, but keep getting the same error, even after installing the I don't have the So I don't really know how to bypass this installation error. Thanks for your response. |
For anybody having the same issue, see sveltejs/kit#3028 (comment) for an alternative solution. |
As @fergardi links to, I just managed to survive the planned obsolescence thanks to: Issue: SOLUTION:
|
thanks, This method solved my problem |
I had the same issue still running on Mac OS X El Capitan 10.11.6 when I wanted to test Vite that uses esbuild. fix-esbuild.sh: #!/bin/sh
npm i
npm i -D esbuild-wasm
rm -rf node_modules/esbuild
ln -s $(pwd)/node_modules/esbuild-wasm ./node_modules/esbuild package.json: {
"name": "vite-project",
"private": true,
"version": "0.0.0",
"type": "module",
"scripts": {
"dev": "vite",
"build": "tsc && vite build",
"lint": "eslint . --ext ts,tsx --report-unused-disable-directives --max-warnings 0",
"preview": "vite preview"
},
"dependencies": {
"react": "^18.2.0",
"react-dom": "^18.2.0"
},
"devDependencies": {
"@types/react": "^18.2.15",
"@types/react-dom": "^18.2.7",
"@typescript-eslint/eslint-plugin": "^6.0.0",
"@typescript-eslint/parser": "^6.0.0",
"@vitejs/plugin-react": "^4.0.3",
"esbuild-wasm": "^0.19.2",
"eslint": "^8.45.0",
"eslint-plugin-react-hooks": "^4.6.0",
"eslint-plugin-react-refresh": "^0.4.3",
"typescript": "^5.0.2",
"vite": "^4.4.5"
}
} |
操作系统(os): mac
node: v14.16.1
npm: 6.14.12
npm install 的时候报错
The text was updated successfully, but these errors were encountered: