Date: Tue, 3 Apr 2018 20:32:10 +0000 From: Brooks Davis <brooks@one-eyed-alien.net> To: freebsd-toolchain@freebsd.org Cc: Ali Mashtizadeh <ali@mashtizadeh.com> Subject: splitting libc -> libc + libsys and static linking Message-ID: <20180403203210.GA23045@spindle.one-eyed-alien.net>
next in thread | raw e-mail | index | archive | help
--cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline We (mostly Ali) are working on a patch to to split the actual syscalls (__sys_<foo>) out of libc and into a libsys. For dynamic linking, this is fairly straightforward (link libc against libsys, maybe as a filter). For static linking, I'm looking for feedback on the right approach. Do we link libsys.a into libc.a? Do we try to teach all the compilers to add -lsys? I'm pretty sure we don't modify all the ports that statically link programs. Is there some easy approach I'm missing? -- Brooks --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJaw+TJAAoJEKzQXbSebgfAuhMIAI8tXIYqhheldGh7ol33Zaar dJUyK49eWVTrfJsaQxsFA3252tug+1uv91eXVgSayIZmYPxBFI0qFst+WGAOKB/7 B+pLdx6X6C+AfXAFS5FtTGtNmEoDHauxEXfZMuTtnj69a1jua+w5lgw2DSYCfEt1 5hc35NGSqpbqx0SmYflU/pmxh0+73qFnnIqT1EzyiFMsQmMnfvzraVLfTfWUzItH DLDwDDHbCdN0Dd4YGySeZc3ZAFKVvkWX6kLfqSt63f8lwNry/HKVTOor0RfDTKbv XBPueuGTCQ6uYUXnA4812Rtn1vYM1ppOLm7/KGf2T+huAV4HA8Fu0j4ZKBwoigQ= =WQxq -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180403203210.GA23045>