-
Notifications
You must be signed in to change notification settings - Fork 12
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
FEAT: support for wasm32 target (error due to simsimd crate) #106
Comments
Hey Komal, thank you for reporting this. Also, I have never worked with WASM before. Could you provide more context about this matter? Like documentation to resources you're using? |
That makes sense. Also, I am using this as a crate to develop a canister in the ICP ecosystem. I am following their instructions like this - https://internetcomputer.org/docs/current/developer-docs/smart-contracts/advanced-features/simd Intro docs - https://internetcomputer.org/docs/current/developer-docs/backend/rust/ But when I deploy the canister, I get the above error of simsimd_cos_f32 . Looks like it is being dynamically linked during runtime. |
Thank you for providing the detail 😁 |
@edwinkys the crate is still not wasm32-unknown-unknown compatible after this change. there are some internal dependencies which are conflicting. Requesting to make it wasm compatible. Available to offer help and support in any way possible from my side including any testing. |
Error I get when building oasysdb = { version = "0.7.3", default-features = false }
|
Hey @komal-rs Based on the error message, I don't notice anything related to OasysDB. Instead, they seem to belong to a crate called Mio? Could you specify which part of OasysDB is causing this issue? |
Yes, seems like this is an issue with mio - seanmonstar/reqwest#1300 My understanding is oasys depends on tokio which depends on mio. Any workarounds you can think to solve it ? |
Its being tracked here - tokio-rs/tokio#4827 |
Hey! Apologize for the delay. Life has been very busy. I'm not quite sure if there is any work around for this version. The last thing we could do if your issue is not resolve is to fork v0.6 and remove the SIMD crate which was causing the error. |
Use case
Need target support for wasm32-unknown-unknown for developing on ICP ecosystem. Getting this error currently when building, something to do with the simsimd crate -
Here's the relevant error from above -
Module imports function 'simsimd_cos_f32' from 'env' that is not exported by the runtime..
Please support wasm32-unknown-unknown as a target.
The text was updated successfully, but these errors were encountered: