This repository has been archived by the owner on Jan 22, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Rust BPF: Using customized sysroot requires maintaining a fork #4389
Milestone
Comments
jackcmay
changed the title
Rust BPF: Using customized sysroot requires a maintaining a fork
Rust BPF: Using customized sysroot requires maintaining a fork
Jul 1, 2019
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
stale
bot
added
the
stale
[bot only] Added to stale content; results in auto-close after a week.
label
Apr 20, 2021
stale
bot
removed
the
stale
[bot only] Added to stale content; results in auto-close after a week.
label
Apr 20, 2021
@dmakarov We can close this now that you've combined the custom sysroot into the tree? |
Yes. |
Great work @dmakarov , we are no longer dependent on a bunch of forks for the custom sysroot |
behzadnouri
pushed a commit
to behzadnouri/solana
that referenced
this issue
Jan 12, 2025
* ci: run 4 partitions for tests * run 5 * revert retry update * reduce the timeout
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Problem
There are multiple customizations to the Rust sysroot (liballoc, libcore, compiler-builtins, etc...) that require we maintain our own fork/repo. Issues #3101, #3102, multi-thread related features are the most obvious but there are other changes related to interdependencies related to xargo that also require customizing the sysroot
Cargo.toml
files.Proposed Solution
The text was updated successfully, but these errors were encountered: