Make modules work again part 2 (final): Link the module build back into the
authorMatthew Dillon <dillon@dragonflybsd.org>
Sat, 16 Aug 2003 02:52:00 +0000 (02:52 +0000)
committerMatthew Dillon <dillon@dragonflybsd.org>
Sat, 16 Aug 2003 02:52:00 +0000 (02:52 +0000)
commit53b3c2d0761ffd4ad9fd53abde8b11be50a53788
treefd59331791672302d6ff80ce0a3e316a852a4296
parent08525cf0b2e83f35f2ceb67a2bf6f9126cc29256
Make modules work again part 2 (final): Link the module build back into the
kernel build.  It should now be possible to build and install the modules
using the 'mobj', 'modules' and 'minstall' targets in /usr/src/sys/Makefile,
though the preferred way is to simply build a kernel using the config or
the buildkernel and installkernel mechanisms.

This commit also fixes a few minor #include path problems that came up during
testing.

Tested with: config/make/install, direct make/install, and with
buildkernel/installkernel.

The following modules are not yet being built by the new system (and were
built with the old system):  vesa.ko, fpu.ko, gnufpu.ko, ibcs2_coff.ko,
usb.ko, ng_mppc.ko, libiconv.ko.
sys/Makefile
sys/boot/i386/boot2/Makefile
sys/boot/pc32/boot2/Makefile
sys/conf/Makefile.i386
sys/dev/disk/aic7xxx/Makefile
sys/dev/disk/aic7xxx/aicasm/Makefile
sys/dev/netif/ar/if_ar.c
sys/dev/netif/sr/if_sr.c
sys/kern/Makefile
sys/netinet/ip_gre.c