You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, many functions or structures in executor are used in the fiber.rs but are ignored with #[cfg(all(target_os = "linux", not(target_env = "musl")))]
cause build fail.
Is this the expected behavior? and is there any standard approach for handling this?
Currently, I can only always disable async in runwasi. (they will build with musl and not musl both)
The text was updated successfully, but these errors were encountered:
The default feature will enable async.
However, many functions or structures in executor are used in the fiber.rs but are ignored with
#[cfg(all(target_os = "linux", not(target_env = "musl")))]
cause build fail.
Is this the expected behavior? and is there any standard approach for handling this?
Currently, I can only always disable async in runwasi. (they will build with musl and not musl both)
The text was updated successfully, but these errors were encountered: