On Tue, Apr 03, 2018 at 08:32:10PM +0000, Brooks Davis wrote: > 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?
Hey Brooks, I'm curious about the reasoning behind this change. Could you explain in more detail why you'd like to create a libsys? Thanks, -- Shawn Webb Cofounder and Security Engineer HardenedBSD Tor-ified Signal: +1 443-546-8752 Tor+XMPP+OTR: latt...@is.a.hacker.sx GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE
signature.asc
Description: PGP signature
