[klibc] Re: Merge strategy for klibc
H. Peter Anvin
hpa at zytor.com
Mon Mar 20 13:24:32 PST 2006
Jan-Benedict Glaw wrote:
> I haven't yet looked at your code, but what actually needs to be done?
> Defining syscall macros?
> I'd probably give it a try for VAX.
Each architecture needs an assembly stub generator for most syscalls, a
crt0.S, plus adjustments for which syscalls are "special" (as in special
ed) on that architecture. There are also a couple of header files which
need per-architecture configuration information. All in all it is
usually a few hours worth of work, no more.
More information about the klibc