Page MenuHomeFreeBSD

makesyscalls: don't make syscall.mk by default
ClosedPublic

Authored by brooks on Nov 17 2023, 7:52 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Oct 16, 1:46 AM
Unknown Object (File)
Sun, Oct 12, 3:27 AM
Unknown Object (File)
Sun, Oct 12, 3:27 AM
Unknown Object (File)
Sun, Oct 12, 3:26 AM
Unknown Object (File)
Sat, Oct 11, 5:32 PM
Unknown Object (File)
Thu, Oct 2, 9:29 PM
Unknown Object (File)
Thu, Oct 2, 9:29 PM
Unknown Object (File)
Sun, Sep 28, 1:23 AM
Subscribers

Details

Summary

We only want to produce syscall.mk for the main syscall table so default
to not producing it (send it to /dev/null) and add a syscalls.conf to
sys/kern to trigger the creation of sys/sys/syscall.mk. This eliminates
the need for entries in other syscalls.conf files and is a cleaner
pattern going forward.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

It might not be a bad idea to later special-case /dev/null in a couple places so that we don't even bother writing temp files in the first place (i.e. shim it out in write_line and a couple other places to nops).

This revision is now accepted and ready to land.Nov 17 2023, 8:26 PM

Likely not worth special case...
I have a refactoring that makes this run in libc in a make friendly way...

FWIW, I hit this because I'm looking at generating parts of lib/libc/sys/Symbol.map on the way to a long overdue reimplementation of D14609. Fortunately it's quite a minor change that just touches all the places sysmk support does (unless I decide to generate more of the file which would require annotations).