[PATCH 00/20] RFC: Add the CPU run-time library for C

Siddhesh Poyarekar siddhesh@gotplt.org
Wed Jun 13 14:20:00 GMT 2018


On 06/13/2018 06:55 PM, Florian Weimer wrote:
> It would be another thing to build a static PIC string library from 
> sources and link that both into libc.so and this new support library. 
> Then the build process would at least be aligned.  But I don't think our 
> current build system is up for that.

Why so?  Are there dependencies that avoid splitting out a 
libstring_pic.a that builds only the string routines and then links that 
into everything that needs it, i.e. libc.so, libc.a, libc-rt.so, etc.?

Ideally I'd like to see something like this happen but it is a crazy 
long term project:

1. Put sysdeps for specific routines into their respective directories. 
That is, elf/sysdeps, math/sysdeps, string/sysdeps, etc.

2. Support building all of these as separate lib*_pic.a that then gets 
integrated at the top

3. Add a new target in string/Makefile that builds a libstring-rt.so 
from its libstring_pic.a

4. Pull string out into a separate project and make it a submodule of 
the glibc repo.

This could even get used to replace libio in future, where 
libio-3.0_pic.a gets linked in by default and libio-2.x_pic.a is built 
into a libio_compat.so that can then be preloaded for programs that need it.

Siddhesh



More information about the Libc-alpha mailing list