=> Background:
=>
=>   building an independent/standalone toolchain able to produce binaries
=>   runnable on NetBSD
=>   (note, this is not the same as compiling or cross-compiling "NetBSD")
=>
=> The component:
=>
=>   libc
=>
=> A small practical question:
=>
=>   Where does machine/asm.h come from, given the NetBSD source sets as
=>   the starting point?
=>
=> Presumably it is possible to find out the answer by analysing the
=> "build.sh" tool but the named tool is possibly not the (only) definition
=> of the structure/interrelations of the concerned data?

   The small question I can handle: see src/sys/arch/*/include/asm.h .

                                 Gary Duzan



Reply via email to