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
tiann
merged 25 commits into
tiann:main
from
CanerKaraca23:mainMar 20, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cross build --target aarch64-linux-android --release --manifest-path ./userspace/ksud/Cargo.toml
Warning: using older rustc `1.67.0 (fc594f156 2023-01-24)` for the target. Current active rustc on the host is `rustc 1.75.0 (82e1608df 2023-12-21)`.
> Update with `rustup update --force-non-host stable-x86_64-unknown-linux-gnu`
error: package `clap v4.5.3` cannot be built because it requires rustc 1.74 or newer, while the currently active rustc version is 1.67.0
Either upgrade to rustc 1.74 or newer, or use
cargo update -p [email protected] --precise ver
where `ver` is the latest version of `clap` supporting rustc 1.67.0
error: Recipe `build_ksud` failed on line 5 with exit code 101
cross build --target aarch64-linux-android --release --manifest-path ./userspace/ksud/Cargo.toml
Warning: using older rustc `1.67.0 (fc594f156 2023-01-24)` for the target. Current active rustc on the host is `rustc 1.75.0 (82e1608df 2023-12-21)`.
> Update with `rustup update --force-non-host stable-x86_64-unknown-linux-gnu`
error: package `clap v4.5.3` cannot be built because it requires rustc 1.74 or newer, while the currently active rustc version is 1.67.0
Either upgrade to rustc 1.74 or newer, or use
cargo update -p [email protected] --precise ver
where `ver` is the latest version of `clap` supporting rustc 1.67.0
error: Recipe `build_ksud` failed on line 5 with exit code 101
Should we update Linux versions of Build Kernel - ChromeOS ARCVM and Build Kernel - WSA workflows from 20.04 to 22.04? Will it break anything? Didn't wanted to do without asking you.
Should we update Linux versions of Build Kernel - ChromeOS ARCVM and Build Kernel - WSA workflows from 20.04 to 22.04? Will it break anything? Didn't wanted to do without asking you.
Should we update Linux versions of Build Kernel - ChromeOS ARCVM and Build Kernel - WSA workflows from 20.04 to 22.04? Will it break anything? Didn't wanted to do without asking you.
I think it won't break
Ah, merged, should i create a new pr for it or you will update it?
Should we update Linux versions of Build Kernel - ChromeOS ARCVM and Build Kernel - WSA workflows from 20.04 to 22.04? Will it break anything? Didn't wanted to do without asking you.
I think it won't break
Ah, merged, should i create a new pr for it or you will update it?
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Build may fail because of some major dependency updates. Needs changes, changes/fixes welcomed.
Main goal is keeping all things up-to-date.