135 
 136 uts/sun4c/Makefile.sun4c
 137 uts/sun4/Makefile.sun4
 138         These Makefile contains the definitions specific (defaults) to
 139         the obvious "implementation architecture". These rules can be
 140         overridden in specific leaf node Makefiles if necessary.
 141 
 142 uts/sun4c/unix/Makefile
 143         Main driving Makefile for building /unix.
 144 
 145 uts/sun4c/MODULE/Makefile (for MODULE in arp, aoutexec, ...)
 146         Main driving Makefile for building MODULE.kmod.
 147 
 148 uts/sun4c/unix.static/Makefile
 149         Main driving Makefile for building a static unix (for development
 150         work only). This Makefile is known to NSE, but its targets are
 151         not. This makefile may be copied to additional parallel directories
 152         to build multiple configurations. This configuration is roughly
 153         equivalent to the GENERIC kernel of SunOS 4.x.
 154 
 155 uts/*/Makefile.?.shared
 156         These denote Makefile contents which are shared between open and
 157         closed builds.
 158 
 159 The Makefiles are verbosely commented. It is desired that they should
 160 stay this way.
 161 
 162 
 163 USE
 164 ---
 165 
 166 Issuing the command 'make' in the uts directory will cause all supported,
 167 modularized kernels and modules to be built.
 168 
 169 Issuing the command 'make' in a uts/ARCHITECTURE directory (i.e.: uts/sparc)
 170 will cause all supported, "implementation architecture" independent modules
 171 for ARCHITECTURE to be built.
 172 
 173 Issuing the command 'make' in a uts/MACHINE directory (i.e.: uts/sun4c)
 174 will cause that kernel and all supported, "implementation architecture"
 175 dependent modules for MACHINE to be built.
 176 
 177 Issuing the command 'make' in the uts/MACHINE/unix directory will cause the
 178 kernel for MACHINE to be built (and unix.o).

 135 
 136 uts/sun4c/Makefile.sun4c
 137 uts/sun4/Makefile.sun4
 138         These Makefile contains the definitions specific (defaults) to
 139         the obvious "implementation architecture". These rules can be
 140         overridden in specific leaf node Makefiles if necessary.
 141 
 142 uts/sun4c/unix/Makefile
 143         Main driving Makefile for building /unix.
 144 
 145 uts/sun4c/MODULE/Makefile (for MODULE in arp, aoutexec, ...)
 146         Main driving Makefile for building MODULE.kmod.
 147 
 148 uts/sun4c/unix.static/Makefile
 149         Main driving Makefile for building a static unix (for development
 150         work only). This Makefile is known to NSE, but its targets are
 151         not. This makefile may be copied to additional parallel directories
 152         to build multiple configurations. This configuration is roughly
 153         equivalent to the GENERIC kernel of SunOS 4.x.
 154 




 155 The Makefiles are verbosely commented. It is desired that they should
 156 stay this way.
 157 
 158 
 159 USE
 160 ---
 161 
 162 Issuing the command 'make' in the uts directory will cause all supported,
 163 modularized kernels and modules to be built.
 164 
 165 Issuing the command 'make' in a uts/ARCHITECTURE directory (i.e.: uts/sparc)
 166 will cause all supported, "implementation architecture" independent modules
 167 for ARCHITECTURE to be built.
 168 
 169 Issuing the command 'make' in a uts/MACHINE directory (i.e.: uts/sun4c)
 170 will cause that kernel and all supported, "implementation architecture"
 171 dependent modules for MACHINE to be built.
 172 
 173 Issuing the command 'make' in the uts/MACHINE/unix directory will cause the
 174 kernel for MACHINE to be built (and unix.o).