RFC Always enable CONFIG_NOLIBC if supported and deprecate --nolibc option
Status from this message: Applied, thanks!
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 1 replyApplied
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | github: Remove nolibc build on the GitHub CI bot.github/ | +0 | 0 replies | |
| 2/2 | configure: Always enable `CONFIG_NOLIBC` if the arch is supportedconfigure | +35 | 0 replies |
Reviews trailers per patch
None of the 2 patches has a Reviewed-by or Acked-by.
| Patch | Ammar Faizi |
|---|---|
| 1/2 | |
| 2/2 | Co-authored-by |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [RFC PATCH liburing v1 0/2] Always enable CONFIG_NOLIBC if supported and deprecate --nolibc option
From: Ammar Faizi <[email protected]>
Hi Jens,
This is an RFC patchset. It's already build-tested.
Currently, the default liburing compilation uses libc as its dependency. liburing doesn't depend on libc when it's compiled on x86-64, x86 (32-bit), and aarch64. There is no benefit to having libc.so linked to liburing.so on those architectures.
Always enable CONFIG_NOLBIC if the arch is supported. If the architecture is not supported, fallback to libc.
There are 2 patches in this series:
- A preparation patch, remove --nolibc from the GitHub CI.
- Always enable CONFIG_NOLIBC if supported and deprecate --nolibc.
After this series, --nolibc option is deprecated and has no effect. I plan to remove this option in a future liburing release.
Comments welcome...
---
Alviro Iskandar Setiawan (1):
configure: Always enable CONFIG_NOLIBC if the arch is supported
Ammar Faizi (1):
github: Remove nolibc build on the GitHub CI bot
.github/workflows/build.yml | 10 ---------- configure | 40 ++++++++++++++++++++++++++++++++----- 2 files changed, 35 insertions(+), 15 deletions(-)
base-commit: c76d392035fd271980faa297334268f2cd77d774
Signature · 1 line
Ammar Faizi