wasm-pack: wasm-pack can't install wasm32-unknown-unkonwn target on DragonFly BSD

πŸ› Bug description

Following the hello world tutorial example, I seem to hit 32bit requirements on a 64bit only operating system.

The following was observed, and annotated in another issue here:

I tried building off commit badbe1c, as well as off the 0.6.0 tag and the 0.7.0 tag, all failed. This was as well with the hello world example.

In order: 0.6.0, 0.7.0, master

zach@dev03 ~/wasm-pack-template> wasm-pack build

  [1/10] Checking `rustc` version...
  [2/10] Checking crate configuration...
| [3/10] Adding WASM target...
Error: Adding the wasm32-unknown-unknown target with rustup
Caused by: No such file or directory (os error 2)
zach@dev03 ~/wasm-pack-template> ../wasm-pack/target/release/wasm-pack build
[INFO]: Checking for the Wasm target...
Error: wasm32-unknown-unknown target not found!
zach@dev03 ~/wasm-pack-template> ../wasm-pack/target/release/wasm-pack build
[INFO]: Checking for the Wasm target...
Error: wasm32-unknown-unknown target not found!

πŸ€” Expected Behavior

I expected that the hello world example would work out of the box, but it’s possible that the documentation is not explicit that only 32bit compilation is supported and/or that 32bit libraries are required and/or that rustup support is required with 32bit binaries and libraries for this.

πŸ‘Ÿ Steps to reproduce

I did a git clone of the wasm-pack-template (my version of cargo does not support generate), so I then edited the Cargo.toml for an arbitrary author name and project name.

I installed the latest release of wasm-pack by cargo (0.6.0 as of this morning) and tried to do wasm-pack build, after not working and finding an issue exhibiting what I thought was the issue, checked out the source and did a git checkout of 0.7.0, with the a similar error. I then checked out master and tried on master with the same error as on 0.7.0.

🌍 Your environment

Include the relevant details of your environment. wasm-pack version: 0.6.0,0.7.0, master (badbe1c37a752963243da526b6fb01b66e7889bd) rustc version: 1.31.1

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 21 (11 by maintainers)

Most upvoted comments

Yeah, iβ€˜m p certain this is likely related to the new non rustup env support- it was a great first pass but i imagine weβ€˜ll need to do more work to make it more robust to the wide range of long tail unorthodox setups. the 32/64 bit part is likely less a concern and mor elikely tied to path issues, if i had to guess at first glance.