Red Bear OS 07659b7f5f Remove round-7 stubs: todo!(), unimplemented!(), silent no-ops
Six items fixed from the round-7 relibc stub scan:

1. set_scheduler todo!() (mod.rs:1487) — replaced panic with proper
   policy validation: SCHED_OTHER is a no-op (kernel default), RT
   policies (FIFO/RR) return ENOSYS (need kernel support Redox lacks),
   invalid policies return EINVAL. Made posix_spawnattr_t.policy
   pub(crate) so the platform layer can read it.

2. F_SETLKW silent no-op (mod.rs:474) — merged into the F_SETLK |
   F_OFD_SETLK match arm. Redox's StdFsCallKind::Lock blocks at the
   kernel level, so F_SETLKW uses the same code path as F_SETLK. The
   is_ofd flag correctly evaluates to false for F_SETLKW.

3. relative_to_absolute_foffset silent (0,0) (mod.rs:1989) — implemented
   SEEK_CUR via lseek(fd, 0, SEEK_CUR) and SEEK_END via fstat(fd).
   Both apply the same negative-len normalization as SEEK_SET. Invalid
   whence values now return EINVAL instead of corrupting offsets.

4. setitimer ENOSYS (signal.rs:96) — replaced todo_skip! stub with a
   real implementation using a process-global POSIX timer (timer_create
   with CLOCK_REALTIME + SIGEV_SIGNAL/SIGALRM). Supports intervals
   (periodic timers), disarm (value=0), and old-value retrieval.
   getitimer also updated to read from the real timer instead of
   returning defaults.

5. ptrace unimplemented!() (ptrace.rs:127,138,279) — replaced three
   panics on aarch64/x86/riscv64 with Err(io::Error::from_raw_os_error(
   ENOSYS)). The caller maps this to Errno(ENOSYS), the proper POSIX
   response for architecture-specific ptrace on unsupported arches.

6. todo_skip! macro verified (macros.rs:47) — confirmed it is
   non-panicking (logs via log::info! and evaluates to ()). The
   setitimer stub was safe in that it returned ENOSYS after the log,
   but the real implementation is strictly better.
2026-07-27 07:12:27 +09:00
2026-07-14 21:56:57 +10:00
2026-07-15 18:24:56 +10:00
2026-07-10 19:06:40 +01:00
2020-08-07 14:16:45 +00:00
2026-02-13 22:00:20 +11:00
2026-07-08 04:21:33 +07:00
2026-04-28 16:49:28 +02:00
2026-07-08 04:21:33 +07:00
2026-07-17 17:26:26 +10:00
2019-02-20 19:27:18 +01:00
2026-07-15 22:40:29 +10:00
2024-07-18 23:59:48 +02:00
2018-03-07 17:29:33 -07:00
2026-05-18 08:29:50 -04:00
2026-05-25 17:03:17 -06:00
2025-10-03 21:51:10 -06:00
2025-10-06 12:44:20 +07:00

Redox C Library (relibc)

relibc is a portable C standard library written in Rust and is under heavy development, this library contains the following items:

  • C, Linux, BSD functions and extensions
  • POSIX compatibility layer
  • Interfaces for system components

The motivation for this project is twofold: Reduce issues that the Redox developers were having with newlib, and create a more stable and safe alternative to C standard libraries written in C. It is mainly designed to be used under Redox, as an alternative to newlib, but it also supports Linux via the sc crate.

Currently Redox and Linux are supported.

redox-rt

redox-rt is a runtime library that provides much of the code that enables POSIX on Redox, like fork, exec, signal handling, etc. Relibc uses it as backend in src/platform/redox, and it's intended to eventually be usable independently, without relibc.

Repository Layout

  • include - Header files (mostly macros and variadic functions cbindgen can't generate)
  • src - Source files
  • src/c - C code
  • src/crt0 - Runtime code
  • src/crti - Runtime code
  • src/crtn - Runtime code
  • src/header - Header files implementation
  • src/header/* - Each folder has a cbindgen.toml file, it generates a C-to-Rust interface and header files
  • src/ld_so - Dynamic loader code
  • src/platform - Platform-specific and common code
  • src/platform/redox - Redox-specific code
  • src/platform/linux - Linux-specific code
  • src/pthread - pthread implementation
  • src/sync - Synchronization primitives
  • tests - C tests (each MR needs to give success in all of them)

Download the sources

To download the relibc sources run the following command:

git clone --recursive https://gitlab.redox-os.org/redox-os/relibc

Build Instructions

To build relibc out of the Redox build system, do the following steps:

Dependencies

  • Install cbindgen
cargo install cbindgen

Install the expect tool

  • Debian, Ubuntu and PopOS:
sudo apt install expect
  • Fedora:
sudo dnf install expect
  • Arch Linux:
sudo pacman -S expect

Build Relibc

To build the relibc library objects, run the following command:

make all
  • Clean old library objects and tests
make clean

Build relibc inside the Redox build system

Inside of your Redox build system, run:

make prefix

If you need to rebuild relibc for testing a Cookbook recipe, run:

touch relibc
make prefix r.recipe-name

Touching (changing the "last modified time" of) the relibc folder is needed to trigger recompilation for make prefix. Replace recipe-name with your desired recipe name.

Note: Do not edit relibc inside prefix folder! Do your work on relibc folder directly inside your Redox build system instead.

Tests

Relibc has a test suite that also runs every time a new commit get pushed. You can see .gitlab-ci.yml to see how it's being executed. That being said, ./check.sh is the recommended way to run tests. Here's few examples:

  • ./check.sh - Run build, without running the test
  • ./check.sh --test - Run all tests in x86_64 Redox using Redoxer
  • ./check.sh --test --host - Run all tests in host (Linux)
  • ./check.sh --test --arch=aarch64 - Run all tests in specified arch
    • Arch can be x86_64, aarch64, i586, or riscv64gc
  • ./check.sh --test=stdio/printf - Run a single test
    • Can be combined with --host or --arch
    • Will run statically linked test in Linux, dynamically linked in Redox

Couple of notes:

  • Relibc and its tests will rebuild if files are changed, however switching between arch or host requires you to run make clean
  • Redoxer is needed to run tests for Redox without --host. You can install it using cargo install redoxer
  • Tests can hang, the test runner can anticipate this, assuming the kernel doesn't hang too.

Issues

I'm building for my own platform which I run, and am getting x86_64-linux-gnu-ar: command not found (or similar)

The Makefile expects GNU compiler tools prefixed with the platform specifier, as would be present when you installed a cross compiler. Since you are building for your own platform, some Linux distributions (like Manjaro) don't install/symlink the prefixed executables.

An easy fix would be to replace the corresponding lines in config.mk, e.g.

ifeq ($(TARGET),x86_64-unknown-linux-gnu)
-	export CC=x86_64-linux-gnu-gcc
-	export LD=x86_64-linux-gnu-ld
-	export AR=x86_64-linux-gnu-ar
-	export NM=x86_64-linux-gnu-nm
+       export CC=gcc
+       export LD=ld
+       export AR=ar
+       export NM=nm
	export OBJCOPY=objcopy
	export CPPFLAGS=
	LD_SO_PATH=lib/ld64.so.1
endif

Contributing

Before starting to contribute, read this document.

Supported OSes

  • Redox OS
  • Linux

Supported architectures

  • i586 (Intel/AMD)
  • x86_64 (Intel/AMD)
  • aarch64 (ARM64)
  • riscv64gc (RISC-V)

Funding - Unix-style Signals and Process Management

This project is funded through NGI Zero Core, a fund established by NLnet with financial support from the European Commission's Next Generation Internet program. Learn more at the NLnet project page.

NLnet foundation logo NGI Zero Logo

S
Description
RedBear Operating System, based on RedoxOS. Licenced under MIT license.
https://redbearos.org
Readme MIT 18 GiB
Languages
C 37.5%
C++ 37.2%
JavaScript 6.7%
QML 3.4%
HTML 3.2%
Other 11.4%