Redox support in `liblibc` and `libstd`
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Redox support in liblibc and libstd
I would like to draft two RFC's to propose the addition of Redox support to liblibc and libstd.
liblibc
Redox currently has issues building using cargo if there is a dependency on the libc crate. This is due to the required patches for adding Redox to liblibc not being available through cargo, and currently liblibc is built as a cargo override using this fork
libstd
Currently, Redox uses a custom libstd, which implements the majority of the public API, but only on Redox. A patch has been in development for the "standard" libstd on this fork
Help Needed
I have maintained these two forks and would like to know the steps required to clean them up and merge them into the Rust mainline, significantly improving ease of development on Redox and potentially allowing for rustc and cargo to be ported to Redox.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked liblibc fork and the redox branch of the rust repository, then read the Rust RFC process to determine what the two proposed RFCs must cover. Done means producing RFC drafts that describe the path for merging Redox support into liblibc and libstd.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100