From: Ammar Faizi <ammarfaizi2@xxxxxxxxxxx> 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... Signed-off-by: Alviro Iskandar Setiawan <alviro.iskandar@xxxxxxxxxxx> Signed-off-by: Ammar Faizi <ammarfaizi2@xxxxxxxxxxx> --- 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 -- Ammar Faizi
