How do I link glibc into my Operating system? I tried a couple of times but I keep getting errors from the actual source from headers and .c files.
And the glibc headers had missing header files that exist in the glibc-build folder containing everything, how do I contain every folder that has glibc *.o files, *.c and *.h properly without any issues?
Porting Glibc
Re: Porting Glibc
glibc is known to be hard to port. It only runs on Linux (and maybe GNU Hurd). If you do not want to invest massive amounts of time into porting it, I'd suggest to look for other, more portable C libraries.
managarm: Microkernel-based OS capable of running a Wayland desktop (Discord: https://discord.gg/7WB6Ur3). My OS-dev projects: [mlibc: Portable C library for managarm, qword, Linux, Sigma, ...] [LAI: AML interpreter] [xbstrap: Build system for OS distributions].
Re: Porting Glibc
What good portable C libraries do you recommend? (And include how easy it is port them)
Re: Porting Glibc
https://wiki.osdev.org/C_LibraryJush wrote:What good portable C libraries do you recommend? (And include how easy it is port them)
(Although ignore the poetry under "MyOS libc"; what's "best" and "most in the osdev spirit" is entirely up to you.)
-
Combuster
- Member
- Posts: 9301
- Joined: Wed Oct 18, 2006 3:45 am
- Libera.chat IRC: [com]buster
- Location: On the balcony, where I can actually keep 1½m distance
- Contact:
Re: Porting Glibc
I've updated the wiki accordinglymallard wrote:Although ignore the poetry under "MyOS libc"; what's "best" and "most in the osdev spirit" is entirely up to you.
