relibc: init#475237
Draft
Eveeifyeve wants to merge 1 commit into
Draft
Conversation
Anderssorby
reviewed
Dec 30, 2025
Anderssorby
reviewed
Dec 30, 2025
Anderssorby
reviewed
Dec 30, 2025
Member
Author
|
Unfortunately there is no |
niklaskorz
reviewed
Jan 9, 2026
niklaskorz
reviewed
Jan 9, 2026
niklaskorz
reviewed
Jan 9, 2026
niklaskorz
reviewed
Jan 9, 2026
Eveeifyeve
force-pushed
the
relibc
branch
3 times, most recently
from
d483c9f to
ff1f352
Compare
nixpkgs-ci
Bot
added
the
2.status: merge conflict
This comment was marked as resolved.
This comment was marked as resolved.
nixpkgs-ci
Bot
removed
the
2.status: merge conflict
This comment was marked as duplicate.
This comment was marked as duplicate.
Co-authored-by: =?UTF-8?q?Anders=20Christiansen=20S=C3=B8rby?= <anders@sorby.xyz> Co-authored-by: Boosted-Bonobo <boostedbonobo1@outlook.com>
Member
Author
|
I have fixed redox os and I have pr up for submission which requires redox to update their pinned toolchain: https://gitlab.redox-os.org/redox-os/relibc/-/merge_requests/1204 However the pr can't be merged yet, because they need to update their own custom rust. Which I am not doing now, because I need sleep I have had ~15+ hours without sleep. |
Eveeifyeve
commented
Apr 17, 2026
Member
Author
There was a problem hiding this comment.
There is some current issues that need to be fixed by the Redox team before we can ship as a platform:
- Remove the dependence on a custom fork of rust. Which uses a custom fork of cargo (used in rust) and rust llvm (used in rust).
- Redox team has stated they do want to move to upstream with rust, but are not sure about where they are with that. Matrix message:
-
auronandace: We do want to move to upstream. Not sure where we are with that.
-
- Redox team has stated they do want to move to upstream with rust, but are not sure about where they are with that. Matrix message:
- Also llvm need to support redox.
- Dependence on nightly features. (Not required, but would reduce the breakages of relibc between rust versions)
Eveeifyeve
force-pushed
the
relibc
branch
4 times, most recently
from
fe80497 to
e21c929
Compare
Eveeifyeve
added
2.status: wait-for-upstream
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Redone relibc pr. A lot of issues that involved fetchFromGitLab, cargoLock defined instead we can use cargoHash(vendored), some werid changes to aliases to deprecated packages, staleness, merge conflicts and more.
Closes: #453786
Fixes: #93661
Waiting on #475235 to be merged first before we rebase and merge this one.
Things done
passthru.tests.nixpkgs-reviewon this PR. See nixpkgs-review usage../result/bin/.Add a 👍 reaction to pull requests you find important.