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
Would it be possible to create a new 0.1 patch release with the CARGO_ENCODED_RUSTFLAGS behavior? Many crates can fail to build on cross-targets with the --locked cargo flag on newer rust versions because of the RUSTFLAGS change, noticed in the Void Linux CI: void-linux/void-packages#34889
The text was updated successfully, but these errors were encountered:
I did publish 0.1.8 that re-exports from 1.1.0 (or later), as they are actually API compatible. This way the 0.1.x series can pick up newer fixes, but you still have to update the lock file. There's nothing I can do for prior locked versions.
Would it be possible to create a new 0.1 patch release with the CARGO_ENCODED_RUSTFLAGS behavior? Many crates can fail to build on cross-targets with the
--locked
cargo flag on newer rust versions because of the RUSTFLAGS change, noticed in the Void Linux CI: void-linux/void-packages#34889The text was updated successfully, but these errors were encountered: