-
Notifications
You must be signed in to change notification settings - Fork 694
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
Homebrew: emcc can't find wasm-ld #188
Comments
Have same issue on mac os, just made
is it possible to install emscripten with all stuff needed for wasm ? |
@Fraer it's possible the Separately from brew, the wasm backend should work in the official emsdk builds, see https://v8.dev/blog/emscripten-llvm-wasm#testing |
Seems like this is an issue with the homebrew package. Is this the right tracker for such bugs? Does anyone know who owns that package? |
I noticed this Homebrew discussion topic on this: https://discourse.brew.sh/t/switch-emscripten-to-llvm/5595 |
I'm tempted to close this since we can fix this in the emscripten project. Only the homebrew maintainer can fix this IIUC. |
I did some investigating here:
This is unfortunate since sometimes people use brew and run into issues, like here. In parallel to trying to contact the proper brew people, maybe we should update our docs on the install page to say that only the emsdk is supported officially? |
I agree with updating the docs, at least so say that the brew package only supports fastcomp . |
…supported, and mention how to install a specific version or a tip-of-tree build using the emsdk. Helps emscripten-core/emsdk#188
This helps with emscripten-core/emsdk#188 Also on that page, remove some obsolete mozilla infrastructure links, and add some docs for installing specific releases and tot builds, which I noticed was missing.
Docs have been updated. I think we can remove this from the blocker list given that, as suggested by @sbc100 I'll still try to contact the proper brew people. A week passed since that form post, I'll try filing an issue. |
I posted a comment on the latest brew PR that updates emscripten. |
…core#9481) This helps with emscripten-core/emsdk#188 Also on that page, remove some obsolete mozilla infrastructure links, and add some docs for installing specific releases and tot builds, which I noticed was missing.
* Workload changes and arcade update (emscripten-core#171) (emscripten-core#172) * Update arcade to 7.0.0-beta.22416.1 * Workload changes Co-authored-by: Larry Ewing <lewing@microsoft.com> Co-authored-by: Juan Hoyos <juan.hoyos@microsoft.com> * [release/7.0-rc1] Make two manifests one for net7 and one for net6 in 7.0.100 sdk band (emscripten-core#163) * Here goes nothing * Update WorkloadManifest.json.in * Update WorkloadManifest.json.in * Try to fix up the multi-targeted build. This will likely need an arcade change to enable manifests withtout packs and an additional change once arcade is updated. * Update eng/emsdk.proj Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com> * Rename .pkgproj files * Update PackageVersionNet6 to 6.0.9 * Fix the location of the .net7 pkgproj Co-authored-by: Marc Paine <marcpop@microsoft.com> Co-authored-by: Ankit Jain <radical@gmail.com> Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com> * [release/7.0-rc1] Shorten the name more (emscripten-core#174) * Shorten the name more * [release/7.0-rc1] Check nuget sizes and fix them (emscripten-core#175) * yml: Fail if nuget size exceeds 250MiB, on linux, and macos * Fix the case for no errors * Remove unused binaries Co-authored-by: Ankit Jain <radical@gmail.com> * Add PowerShell-based NuGet size check script and use it on Windows (emscripten-core#176) * Add PowerShell-based NuGet size check script and use it on Windows * Update azure-pipelines.yml * Roll back 6.0.x to 6.0.8 so that packages exist (emscripten-core#177) * Revert "Roll back 6.0.x to 6.0.8 so that packages exist (emscripten-core#177)" (emscripten-core#178) This reverts commit b7a5ae2. * make a 6.0.4 build (emscripten-core#180) * Revert "make a 6.0.4 build (emscripten-core#180)" (emscripten-core#181) This reverts commit eb3232e. * [release/7.0] Update arcade to 7.0.0-beta.22418.4 (emscripten-core#182) * WorkloadManifest.targets: fix condition (emscripten-core#183) Co-authored-by: Juan Hoyos <juan.hoyos@microsoft.com> Co-authored-by: Marc Paine <marcpop@microsoft.com> Co-authored-by: Ankit Jain <radical@gmail.com> Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com>
Just now I tried to run em++ after setting
EMCC_WASM_BACKEND
andEMCC_DEBUG
variables to 1 and I got this error:I'd ran these commands before that:
I'd really like some help here. Thanks in advance.
The text was updated successfully, but these errors were encountered: