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

Conflicting imports of wasi cause wasm-component-ld error. #2047

Open
cdmurph32 opened this issue Feb 10, 2025 · 2 comments
Open

Conflicting imports of wasi cause wasm-component-ld error. #2047

cdmurph32 opened this issue Feb 10, 2025 · 2 comments

Comments

@cdmurph32
Copy link

Conflicting version of wasi will cause builds to crash. As more common crates are importing wasi this problem will grow if not addressed. In my particular case newer version of tempfile and uuid depended on a newer version of getrandom which depended on v0.13.3+wasi-0.2.2. This conflicted with my crate's direct dependency and the dependency of wstd on v0.14.1+wasi-0.2.3.

working_tree.txt

not_working_tree.txt

conflicting_wasi_error.txt

@alexcrichton
Copy link
Member

It's hard to say without a reproduction, but my gut is that this is likely a duplicate of #1897 and is also similar to bytecodealliance/wasm-component-ld#52

@cdmurph32
Copy link
Author

cdmurph32 commented Feb 11, 2025

Reproduction steps:

  1. Checkout https://github.com/contentauth/c2pa-rs/tree/wasm32-wasi_0.41.0
  2. Change version of tempfile to v3.16.0
  3. Run cargo +nightly build --target wasm32-wasip2 -p c2pa

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

2 participants