Skip to content
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

Open
DragonOsman opened this issue Nov 23, 2018 · 9 comments
Open

Homebrew: emcc can't find wasm-ld #188

DragonOsman opened this issue Nov 23, 2018 · 9 comments
Assignees

Comments

@DragonOsman
Copy link

Just now I tried to run em++ after setting EMCC_WASM_BACKEND and EMCC_DEBUG variables to 1 and I got this error:

shared:ERROR: WASM_BACKEND selected but could not find lld (wasm-ld): C:/Users/Osman/emsdk/clang/e1.38.20_64bit\wasm-ld.exe

I'd ran these commands before that:

emsdk install latest --vs2017 --build=Release
emsdk activate latest --vs2017 --build=Release
emsdk_env

I'd really like some help here. Thanks in advance.

@Fraer
Copy link

Fraer commented Aug 5, 2019

Have same issue on mac os, just made brew install emscripten and each time i run emcc i have the message:

shared:ERROR: emcc: WASM_BACKEND selected but could not find lld (wasm-ld): /usr/bin/wasm-ld

is it possible to install emscripten with all stuff needed for wasm ?

@kripken
Copy link
Member

kripken commented Aug 5, 2019

@Fraer it's possible the brew setup only supports fastcomp for now. We should file a bug for that - if you can please do so and link to it here. (I don't have a MacOS machine so I can't provide any info they might ask me if I file a bug there.)

Separately from brew, the wasm backend should work in the official emsdk builds, see https://v8.dev/blog/emscripten-llvm-wasm#testing

@kripken kripken changed the title emcc can't find wasm-ld Homebrew: emcc can't find wasm-ld Aug 6, 2019
@sbc100
Copy link
Collaborator

sbc100 commented Aug 20, 2019

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?

@kripken
Copy link
Member

kripken commented Aug 28, 2019

I noticed this Homebrew discussion topic on this: https://discourse.brew.sh/t/switch-emscripten-to-llvm/5595

@sbc100
Copy link
Collaborator

sbc100 commented Aug 28, 2019

I'm tempted to close this since we can fix this in the emscripten project. Only the homebrew maintainer can fix this IIUC.

@kripken
Copy link
Member

kripken commented Sep 21, 2019

I did some investigating here:

  • The main brew repo discourages people from filing issues for things that aren't clearly bugs with STRs, so I didn't file an issue there.
  • I went through commits trying to find who maintains the emscripten release, but it was hard to tell - there are commits to update to new builds, but they are by people that do a lot of other stuff. I'm not sure if those are just automatic or semi-automatic updates, or actual devs that are familiar with it.
  • I pinged the forum post about this that I linked earlier. No response yet.

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?

@sbc100
Copy link
Collaborator

sbc100 commented Sep 21, 2019

I agree with updating the docs, at least so say that the brew package only supports fastcomp .

kripken added a commit to emscripten-core/emscripten that referenced this issue Sep 22, 2019
…supported, and mention how to install a specific version or a tip-of-tree build using the emsdk. Helps emscripten-core/emsdk#188
@kripken kripken self-assigned this Sep 23, 2019
kripken added a commit to emscripten-core/emscripten that referenced this issue Sep 23, 2019
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.
@kripken
Copy link
Member

kripken commented Sep 25, 2019

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.

@kripken
Copy link
Member

kripken commented Sep 25, 2019

I posted a comment on the latest brew PR that updates emscripten.

belraquib pushed a commit to belraquib/emscripten that referenced this issue Dec 23, 2020
…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.
vargaz pushed a commit to vargaz/emsdk that referenced this issue Nov 22, 2023
* 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 <[email protected]>

Co-authored-by: Juan Hoyos <[email protected]>

* [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 <[email protected]>

* Rename .pkgproj files

* Update PackageVersionNet6 to 6.0.9

* Fix the location of the .net7 pkgproj

Co-authored-by: Marc Paine <[email protected]>
Co-authored-by: Ankit Jain <[email protected]>
Co-authored-by: Alexander Köplinger <[email protected]>

* [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 <[email protected]>

* 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 <[email protected]>
Co-authored-by: Marc Paine <[email protected]>
Co-authored-by: Ankit Jain <[email protected]>
Co-authored-by: Alexander Köplinger <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants