mirror/freebsd
1
0
Fork 0
mirror of https://git.FreeBSD.org/src.git synced 2024-12-20 11:11:24 +00:00
Code Issues Releases Activity
6cb2040baf
freebsd/sys/conf/kmod.mk

404 lines
9.7 KiB
Makefile
Raw Normal View History

A make system file for building LKMs, derived from bsd.prog.mk.
1994-09-14 21:59:28 +00:00
# From: @(#)bsd.prog.mk 5.26 (Berkeley) 6/25/91
$Id$ -> $FreeBSD$
1999-08-28 00:22:10 +00:00
# $FreeBSD$
Add some comments for variables and targets.
1996-05-25 23:09:49 +00:00
#
Style fixes, including: - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
2004-10-12 15:04:10 +00:00
# The include file <bsd.kmod.mk> handles building and installing loadable
# kernel modules.
Add some comments for variables and targets.
1996-05-25 23:09:49 +00:00
#
#
# +++ variables +++
#
# CLEANFILES Additional files to remove for the clean and cleandir targets.
#
Style fixes, including: - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
2004-10-12 15:04:10 +00:00
# EXPORT_SYMS A list of symbols that should be exported from the module,
# or the name of a file containing a list of symbols, or YES
# to export all symbols. If not defined, no symbols are
# exported.
#
# KMOD The name of the kernel module to build.
Add some comments for variables and targets.
1996-05-25 23:09:49 +00:00
#
The kernel is now known as `kernel.ko' and it and its matching modules live in ``/boot/kernel/''.
2000-09-05 22:37:46 +00:00
# KMODDIR Base path for kernel modules (see kld(4)). [/boot/kernel]
Add some comments for variables and targets.
1996-05-25 23:09:49 +00:00
#
Style fixes, including: - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
2004-10-12 15:04:10 +00:00
# KMODOWN Module file owner. [${BINOWN}]
Add some comments for variables and targets.
1996-05-25 23:09:49 +00:00
#
Style fixes, including: - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
2004-10-12 15:04:10 +00:00
# KMODGRP Module file group. [${BINGRP}]
Add some comments for variables and targets.
1996-05-25 23:09:49 +00:00
#
Style fixes, including: - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
2004-10-12 15:04:10 +00:00
# KMODMODE Module file mode. [${BINMODE}]
Add some comments for variables and targets.
1996-05-25 23:09:49 +00:00
#
1) s/mod(un)?load/kld$1load/ 2) s/MODLOAD/KMODLOAD/ to be consistent with the rest of the variables (KMOD, KMODOWN, KMODGRP, etc) and definition of MODLOAD/UNLOAD in the Makefile of the ATAPI module 3) textual fixups
1999-09-06 20:11:59 +00:00
# KMODLOAD Command to load a kernel module [/sbin/kldload]
add variables MODLOAD and MODUNLOAD for modlad/modunload commands
1996-10-06 22:10:35 +00:00
#
1) s/mod(un)?load/kld$1load/ 2) s/MODLOAD/KMODLOAD/ to be consistent with the rest of the variables (KMOD, KMODOWN, KMODGRP, etc) and definition of MODLOAD/UNLOAD in the Makefile of the ATAPI module 3) textual fixups
1999-09-06 20:11:59 +00:00
# KMODUNLOAD Command to unload a kernel module [/sbin/kldunload]
add variables MODLOAD and MODUNLOAD for modlad/modunload commands
1996-10-06 22:10:35 +00:00
#
Allow the calling Makefile to specify a list of device interfaces instead of relying on the default list provided here.
2000-04-05 10:13:05 +00:00
# MFILES Optionally a list of interfaces used by the module.
# This file contains a default list of interfaces.
Add some comments for variables and targets.
1996-05-25 23:09:49 +00:00
#
Style fixes, including: - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
2004-10-12 15:04:10 +00:00
# PROG The name of the kernel module to build.
# If not supplied, ${KMOD}.ko is used.
#
# SRCS List of source files.
#
# DESTDIR The tree where the module gets installed. [not set]
Eliminate the use of commons in the kernel and modules, simplifying the module linking process and eliminating the risks associated with doubly-defined variables. Cases where commons were legitimately used (detection of compiled-in subsystems) have been converted to use sysinits, and any new code should use this or an equivalent practice as a matter of course. Modules can override this behaviour by substituting -fno-common out of ${CFLAGS} in cases where commons are necessary (eg. third-party object modules). Commons will be resolved and allocated space when the kld is linked as part of the module build process, so they will not pose a risk to the kernel or other modules. Provide a mechanism for controlling the export of symbols from the module namespace. The EXPORT_SYMS variable may be set in the Makefile to NO (export no symbols), a list of symbols to export, or the name of a file containing a newline-seperated list of symbols to be exported. Non-exported symbols are converted to local symbols. If EXPORT_SYMS is not set, all global symbols are currently exported. This behaviour is expected to change (to exporting no symbols) once modules have been converted. Reviewed by: peter (in principle) Obtained from: green (kmod_syms.awk)
2002-01-10 03:52:01 +00:00
#
Add some comments for variables and targets.
1996-05-25 23:09:49 +00:00
# +++ targets +++
#
# install:
Drop <bsd.man.mk> support from <bsd.kmod.mk>. Not objected to by: -current
2002-01-11 15:49:02 +00:00
# install the kernel module; if the Makefile
Add some comments for variables and targets.
1996-05-25 23:09:49 +00:00
# does not itself define the target install, the targets
# beforeinstall and afterinstall may also be used to cause
# actions immediately before and after the install target
# is executed.
#
kobjify. this gives us several benefits, including: * easier extensibility- new optional methods can be added to ac97/mixer/channel classes without having to fixup every driver. * forward compatibility for drivers, provided no new mandatory methods are added.
2000-12-18 01:36:41 +00:00
# load:
Style fixes, including: - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
2004-10-12 15:04:10 +00:00
# Load a module.
Add some comments for variables and targets.
1996-05-25 23:09:49 +00:00
#
# unload:
Style fixes, including: - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
2004-10-12 15:04:10 +00:00
# Unload a module.
Add some comments for variables and targets.
1996-05-25 23:09:49 +00:00
#
A make system file for building LKMs, derived from bsd.prog.mk.
1994-09-14 21:59:28 +00:00
Use vnode_if.awk rather than vnode_if.pl
2002-03-01 01:21:29 +00:00
AWK?= awk
1) s/mod(un)?load/kld$1load/ 2) s/MODLOAD/KMODLOAD/ to be consistent with the rest of the variables (KMOD, KMODOWN, KMODGRP, etc) and definition of MODLOAD/UNLOAD in the Makefile of the ATAPI module 3) textual fixups
1999-09-06 20:11:59 +00:00
KMODLOAD?= /sbin/kldload
KMODUNLOAD?= /sbin/kldunload
When building a debugging kernel with modules, build modules with debugging support as well. Debugging module support is handled identically to kernel debugging support, right down to poor choice of make variable names.
2001-08-02 09:22:18 +00:00
OBJCOPY?= objcopy
add variables MODLOAD and MODUNLOAD for modlad/modunload commands
1996-10-06 22:10:35 +00:00
Catch any stray KMODDEPS entries to make sure they do not keep turning up.
2002-05-01 01:32:28 +00:00
.if defined(KMODDEPS)
Style fixes, including: - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
2004-10-12 15:04:10 +00:00
.error "Do not use KMODDEPS on 5.0+; use MODULE_VERSION/MODULE_DEPEND"
Catch any stray KMODDEPS entries to make sure they do not keep turning up.
2002-05-01 01:32:28 +00:00
.endif
Use standard bsd.init.mk prologue.
2002-04-22 15:47:11 +00:00
.include <bsd.init.mk>
A make system file for building LKMs, derived from bsd.prog.mk.
1994-09-14 21:59:28 +00:00
.SUFFIXES: .out .o .c .cc .cxx .C .y .l .s .S
This are the build infrastructure changes to allow to use the Intel C/C++ compiler (lang/icc) to build the kernel. The icc CPUTYPE CFLAGS use icc v7 syntax, icc v8 moans about them, but doesn't abort. They also produce CPU specific code (new instructions of the CPU, not only CPU specific scheduling), so if you get coredumps with signal 4 (SIGILL, illegal instruction) you've used the wrong CPUTYPE. Incarnations of this patch survive gcc compiles and my make universe. I use it on my desktop. To use it update share/mk, add /usr/local/intel/compiler70/ia32/bin (icc v7, works) or /usr/local/intel_cc_80/bin (icc v8, doesn't work) to your PATH, make sure you have a new kernel compile directory (e.g. MYKERNEL_icc) and run CFLAGS="-O2 -ip" CC=icc make depend CFLAGS="-O2 -ip" CC=icc make in it. Don't compile with -ipo, the build infrastructure uses ld directly to link the kernel and the modules, but -ipo needs the link step to be performed with Intel's linker. Problems with icc v8: - panic: npx0 cannot be emulated on an SMP system - UP: first start of /bin/sh results in a FP exception Parts of this commit contains suggestions or submissions from Marius Strobl <marius@alchemy.franken.de>. Reviewed by: silence on -arch Submitted by: netchild
2004-03-12 21:36:12 +00:00
.if ${CC} == "icc"
Fix some style bugs in previous commit. Fix 'broken' ifdefs. icc does not support profiling yet so remove unfinished code which was supposed to help. Submitted by: netchild (original version) Reviewed by: ru
2004-03-14 01:29:05 +00:00
CFLAGS:= ${CFLAGS:C/(-x[^M^K^W]+)[MKW]+|-x[MKW]+/\1/}
Generally force -Werror for modules when not compiling with icc. This has burned me for the last time.
2005-01-26 15:49:23 +00:00
.else
WERROR?= -Werror
Add required ing
2005-01-26 23:27:12 +00:00
CFLAGS:= ${CFLAGS:C/-O2/-O2 -fno-strict-aliasing/}
This are the build infrastructure changes to allow to use the Intel C/C++ compiler (lang/icc) to build the kernel. The icc CPUTYPE CFLAGS use icc v7 syntax, icc v8 moans about them, but doesn't abort. They also produce CPU specific code (new instructions of the CPU, not only CPU specific scheduling), so if you get coredumps with signal 4 (SIGILL, illegal instruction) you've used the wrong CPUTYPE. Incarnations of this patch survive gcc compiles and my make universe. I use it on my desktop. To use it update share/mk, add /usr/local/intel/compiler70/ia32/bin (icc v7, works) or /usr/local/intel_cc_80/bin (icc v8, doesn't work) to your PATH, make sure you have a new kernel compile directory (e.g. MYKERNEL_icc) and run CFLAGS="-O2 -ip" CC=icc make depend CFLAGS="-O2 -ip" CC=icc make in it. Don't compile with -ipo, the build infrastructure uses ld directly to link the kernel and the modules, but -ipo needs the link step to be performed with Intel's linker. Problems with icc v8: - panic: npx0 cannot be emulated on an SMP system - UP: first start of /bin/sh results in a FP exception Parts of this commit contains suggestions or submissions from Marius Strobl <marius@alchemy.franken.de>. Reviewed by: silence on -arch Submitted by: netchild
2004-03-12 21:36:12 +00:00
.endif
Generally force -Werror for modules when not compiling with icc. This has burned me for the last time.
2005-01-26 15:49:23 +00:00
CFLAGS+= ${WERROR}
Removed COPTS support from kmod.mk and kern.pre.mk. COPTS support in bsd.prog.mk is preserved but discouraged.
2004-08-13 14:30:26 +00:00
CFLAGS+= -D_KERNEL
Define KLD_MODULE if building a KLD module. Forgot to mention that the previous commit was Submitted by: Doug Rabson <dfr@freebsd.org>
1998-10-02 05:08:09 +00:00
CFLAGS+= -DKLD_MODULE
Generate symlinks to the "sys" and <machine> directories and put them in the include path. This fixes recent breakage of the syscons LKMs and general brokenness of the include paths (headers under /usr/include were used in many cases).
1998-01-26 20:36:38 +00:00
Restrict the include search path using -nostdinc -I- in $(CFLAGS} as in kernel Makefiles. Nothing in /usr/include is used (provided relative paths for sys/* and <machine> can be found), so there is no need for the -I/usr/include kludge as in kernel Makefiles.
1998-02-01 17:19:54 +00:00
# Don't use any standard or source-relative include directories.
# Since -nostdinc will annull any previous -I paths, we repeat all
# such paths after -nostdinc. It doesn't seem to be possible to
# add to the front of `make' variable.
_ICFLAGS:= ${CFLAGS:M-I*}
This are the build infrastructure changes to allow to use the Intel C/C++ compiler (lang/icc) to build the kernel. The icc CPUTYPE CFLAGS use icc v7 syntax, icc v8 moans about them, but doesn't abort. They also produce CPU specific code (new instructions of the CPU, not only CPU specific scheduling), so if you get coredumps with signal 4 (SIGILL, illegal instruction) you've used the wrong CPUTYPE. Incarnations of this patch survive gcc compiles and my make universe. I use it on my desktop. To use it update share/mk, add /usr/local/intel/compiler70/ia32/bin (icc v7, works) or /usr/local/intel_cc_80/bin (icc v8, doesn't work) to your PATH, make sure you have a new kernel compile directory (e.g. MYKERNEL_icc) and run CFLAGS="-O2 -ip" CC=icc make depend CFLAGS="-O2 -ip" CC=icc make in it. Don't compile with -ipo, the build infrastructure uses ld directly to link the kernel and the modules, but -ipo needs the link step to be performed with Intel's linker. Problems with icc v8: - panic: npx0 cannot be emulated on an SMP system - UP: first start of /bin/sh results in a FP exception Parts of this commit contains suggestions or submissions from Marius Strobl <marius@alchemy.franken.de>. Reviewed by: silence on -arch Submitted by: netchild
2004-03-12 21:36:12 +00:00
.if ${CC} == "icc"
NOSTDINC= -X
.else
NOSTDINC= -nostdinc
.endif
CFLAGS+= ${NOSTDINC} -I- ${INCLMAGIC} ${_ICFLAGS}
Include opt_global.h in the modules build, when building from a normal kernel build. This makes it possible for me not to get pissed off that random.ko crashes the system trying to rdtsc() when the i386/cpu.h support code decides it's okay to call that op when neither I386_CPU or I486_CPU is defined. I guess it also makes WITNESS/INVARIANTS defines get picked up by the modules.
2003-11-14 16:04:11 +00:00
.if defined(KERNBUILDDIR)
Style fixes, including: - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
2004-10-12 15:04:10 +00:00
CFLAGS+= -include ${KERNBUILDDIR}/opt_global.h
Include opt_global.h in the modules build, when building from a normal kernel build. This makes it possible for me not to get pissed off that random.ko crashes the system trying to rdtsc() when the i386/cpu.h support code decides it's okay to call that op when neither I386_CPU or I486_CPU is defined. I guess it also makes WITNESS/INVARIANTS defines get picked up by the modules.
2003-11-14 16:04:11 +00:00
.endif
Restrict the include search path using -nostdinc -I- in $(CFLAGS} as in kernel Makefiles. Nothing in /usr/include is used (provided relative paths for sys/* and <machine> can be found), so there is no need for the -I/usr/include kludge as in kernel Makefiles.
1998-02-01 17:19:54 +00:00
Style fixes, including: - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
2004-10-12 15:04:10 +00:00
# Add -I paths for system headers. Individual module makefiles don't
Restrict the include search path using -nostdinc -I- in $(CFLAGS} as in kernel Makefiles. Nothing in /usr/include is used (provided relative paths for sys/* and <machine> can be found), so there is no need for the -I/usr/include kludge as in kernel Makefiles.
1998-02-01 17:19:54 +00:00
# need any -I paths for this. Similar defaults for .PATH can't be
# set because there are no standard paths for non-headers.
Now that the pci include file location migration has been completed, remove the -I$S/dev and -I@/dev which were there only for pci. # If I've broken something, please let me know.
2003-08-22 15:41:44 +00:00
CFLAGS+= -I. -I@
Generate symlinks to the "sys" and <machine> directories and put them in the include path. This fixes recent breakage of the syscons LKMs and general brokenness of the include paths (headers under /usr/include were used in many cases).
1998-01-26 20:36:38 +00:00
Link ALTQ to the build and break with ABI for struct ifnet. Please recompile your (network) modules as well as any userland that might make sense of sizeof(struct ifnet). This does not change the queueing yet. These changes will follow in a seperate commit. Same with the driver changes, which need case by case evaluation. __FreeBSD_version bump will follow. Tested-by: (i386)LINT
2004-06-13 17:29:10 +00:00
# Add -I path for altq headers as they are included via net/if_var.h
# for example.
CFLAGS+= -I@/contrib/altq
Add "-I@/../include" and/or "-I${DESTDIR}/usr/include" to CFLAGS, essentially as in kernel makefiles, so that module sources can include <stddef.h> and other standard headers. Only add the second path when the first path can't be found, instead of when DESTDIR is defined. Adding it used to be just an obfuscation. Use "${.OBJDIR}" instyead of "." in -I paths. Using "${.OBJDIR}" just gave more verbose command lines and depend files.
2000-01-08 18:48:57 +00:00
# Add a -I path to standard headers like <stddef.h>. Use a relative
# path to src/include if possible. If the @ symlink hasn't been built
# yet, then we can't tell if the relative path exists. Add both the
# potential relative path and an absolute path in that case.
.if exists(@)
.if exists(@/../include)
CFLAGS+= -I@/../include
.else
Add "-I${DESTDIR}/usr/include" to CFLAGS if DESTDIR is defined, just like bsd.lib.mk and bsd.prog.mk. It doesn't add it to CXXINCLUDES, I don't think anybody has written a kernel module with C++. (Not that I think DavidG will allow it anyway. :) Reviewed by: bde
1997-06-18 03:10:31 +00:00
CFLAGS+= -I${DESTDIR}/usr/include
.endif
Add "-I@/../include" and/or "-I${DESTDIR}/usr/include" to CFLAGS, essentially as in kernel makefiles, so that module sources can include <stddef.h> and other standard headers. Only add the second path when the first path can't be found, instead of when DESTDIR is defined. Adding it used to be just an obfuscation. Use "${.OBJDIR}" instyead of "." in -I paths. Using "${.OBJDIR}" just gave more verbose command lines and depend files.
2000-01-08 18:48:57 +00:00
.else # !@
CFLAGS+= -I@/../include -I${DESTDIR}/usr/include
.endif # @
Pick up CWARNFLAGS from /etc/make.conf if defined.
1996-04-03 12:08:52 +00:00
This are the build infrastructure changes to allow to use the Intel C/C++ compiler (lang/icc) to build the kernel. The icc CPUTYPE CFLAGS use icc v7 syntax, icc v8 moans about them, but doesn't abort. They also produce CPU specific code (new instructions of the CPU, not only CPU specific scheduling), so if you get coredumps with signal 4 (SIGILL, illegal instruction) you've used the wrong CPUTYPE. Incarnations of this patch survive gcc compiles and my make universe. I use it on my desktop. To use it update share/mk, add /usr/local/intel/compiler70/ia32/bin (icc v7, works) or /usr/local/intel_cc_80/bin (icc v8, doesn't work) to your PATH, make sure you have a new kernel compile directory (e.g. MYKERNEL_icc) and run CFLAGS="-O2 -ip" CC=icc make depend CFLAGS="-O2 -ip" CC=icc make in it. Don't compile with -ipo, the build infrastructure uses ld directly to link the kernel and the modules, but -ipo needs the link step to be performed with Intel's linker. Problems with icc v8: - panic: npx0 cannot be emulated on an SMP system - UP: first start of /bin/sh results in a FP exception Parts of this commit contains suggestions or submissions from Marius Strobl <marius@alchemy.franken.de>. Reviewed by: silence on -arch Submitted by: netchild
2004-03-12 21:36:12 +00:00
.if ${CC} != "icc"
Change the inline limit switch to something that exists in gcc-3.2. Unfortunately, it has different units.
2003-07-26 02:27:50 +00:00
CFLAGS+= -finline-limit=${INLINE_LIMIT}
This are the build infrastructure changes to allow to use the Intel C/C++ compiler (lang/icc) to build the kernel. The icc CPUTYPE CFLAGS use icc v7 syntax, icc v8 moans about them, but doesn't abort. They also produce CPU specific code (new instructions of the CPU, not only CPU specific scheduling), so if you get coredumps with signal 4 (SIGILL, illegal instruction) you've used the wrong CPUTYPE. Incarnations of this patch survive gcc compiles and my make universe. I use it on my desktop. To use it update share/mk, add /usr/local/intel/compiler70/ia32/bin (icc v7, works) or /usr/local/intel_cc_80/bin (icc v8, doesn't work) to your PATH, make sure you have a new kernel compile directory (e.g. MYKERNEL_icc) and run CFLAGS="-O2 -ip" CC=icc make depend CFLAGS="-O2 -ip" CC=icc make in it. Don't compile with -ipo, the build infrastructure uses ld directly to link the kernel and the modules, but -ipo needs the link step to be performed with Intel's linker. Problems with icc v8: - panic: npx0 cannot be emulated on an SMP system - UP: first start of /bin/sh results in a FP exception Parts of this commit contains suggestions or submissions from Marius Strobl <marius@alchemy.franken.de>. Reviewed by: silence on -arch Submitted by: netchild
2004-03-12 21:36:12 +00:00
.endif
Provide a knob for raising the inline instruction estimate threshold and set an initial value. This is aimed at getting us closer to being able to turn -Werror back on and we can adjust the settings later on. Yes, we could turn off -Wno-inline instead, but that would hide the effect of gcc's bogo-estimator ignoring inline (either rightly or wrongly).
2003-07-23 20:03:42 +00:00
Eliminate the use of commons in the kernel and modules, simplifying the module linking process and eliminating the risks associated with doubly-defined variables. Cases where commons were legitimately used (detection of compiled-in subsystems) have been converted to use sysinits, and any new code should use this or an equivalent practice as a matter of course. Modules can override this behaviour by substituting -fno-common out of ${CFLAGS} in cases where commons are necessary (eg. third-party object modules). Commons will be resolved and allocated space when the kld is linked as part of the module build process, so they will not pose a risk to the kernel or other modules. Provide a mechanism for controlling the export of symbols from the module namespace. The EXPORT_SYMS variable may be set in the Makefile to NO (export no symbols), a list of symbols to export, or the name of a file containing a newline-seperated list of symbols to be exported. Non-exported symbols are converted to local symbols. If EXPORT_SYMS is not set, all global symbols are currently exported. This behaviour is expected to change (to exporting no symbols) once modules have been converted. Reviewed by: peter (in principle) Obtained from: green (kmod_syms.awk)
2002-01-10 03:52:01 +00:00
# Disallow common variables, and if we end up with commons from
# somewhere unexpected, allocate storage for them in the module itself.
This are the build infrastructure changes to allow to use the Intel C/C++ compiler (lang/icc) to build the kernel. The icc CPUTYPE CFLAGS use icc v7 syntax, icc v8 moans about them, but doesn't abort. They also produce CPU specific code (new instructions of the CPU, not only CPU specific scheduling), so if you get coredumps with signal 4 (SIGILL, illegal instruction) you've used the wrong CPUTYPE. Incarnations of this patch survive gcc compiles and my make universe. I use it on my desktop. To use it update share/mk, add /usr/local/intel/compiler70/ia32/bin (icc v7, works) or /usr/local/intel_cc_80/bin (icc v8, doesn't work) to your PATH, make sure you have a new kernel compile directory (e.g. MYKERNEL_icc) and run CFLAGS="-O2 -ip" CC=icc make depend CFLAGS="-O2 -ip" CC=icc make in it. Don't compile with -ipo, the build infrastructure uses ld directly to link the kernel and the modules, but -ipo needs the link step to be performed with Intel's linker. Problems with icc v8: - panic: npx0 cannot be emulated on an SMP system - UP: first start of /bin/sh results in a FP exception Parts of this commit contains suggestions or submissions from Marius Strobl <marius@alchemy.franken.de>. Reviewed by: silence on -arch Submitted by: netchild
2004-03-12 21:36:12 +00:00
.if ${CC} != "icc"
Eliminate the use of commons in the kernel and modules, simplifying the module linking process and eliminating the risks associated with doubly-defined variables. Cases where commons were legitimately used (detection of compiled-in subsystems) have been converted to use sysinits, and any new code should use this or an equivalent practice as a matter of course. Modules can override this behaviour by substituting -fno-common out of ${CFLAGS} in cases where commons are necessary (eg. third-party object modules). Commons will be resolved and allocated space when the kld is linked as part of the module build process, so they will not pose a risk to the kernel or other modules. Provide a mechanism for controlling the export of symbols from the module namespace. The EXPORT_SYMS variable may be set in the Makefile to NO (export no symbols), a list of symbols to export, or the name of a file containing a newline-seperated list of symbols to be exported. Non-exported symbols are converted to local symbols. If EXPORT_SYMS is not set, all global symbols are currently exported. This behaviour is expected to change (to exporting no symbols) once modules have been converted. Reviewed by: peter (in principle) Obtained from: green (kmod_syms.awk)
2002-01-10 03:52:01 +00:00
CFLAGS+= -fno-common
This are the build infrastructure changes to allow to use the Intel C/C++ compiler (lang/icc) to build the kernel. The icc CPUTYPE CFLAGS use icc v7 syntax, icc v8 moans about them, but doesn't abort. They also produce CPU specific code (new instructions of the CPU, not only CPU specific scheduling), so if you get coredumps with signal 4 (SIGILL, illegal instruction) you've used the wrong CPUTYPE. Incarnations of this patch survive gcc compiles and my make universe. I use it on my desktop. To use it update share/mk, add /usr/local/intel/compiler70/ia32/bin (icc v7, works) or /usr/local/intel_cc_80/bin (icc v8, doesn't work) to your PATH, make sure you have a new kernel compile directory (e.g. MYKERNEL_icc) and run CFLAGS="-O2 -ip" CC=icc make depend CFLAGS="-O2 -ip" CC=icc make in it. Don't compile with -ipo, the build infrastructure uses ld directly to link the kernel and the modules, but -ipo needs the link step to be performed with Intel's linker. Problems with icc v8: - panic: npx0 cannot be emulated on an SMP system - UP: first start of /bin/sh results in a FP exception Parts of this commit contains suggestions or submissions from Marius Strobl <marius@alchemy.franken.de>. Reviewed by: silence on -arch Submitted by: netchild
2004-03-12 21:36:12 +00:00
.endif
Eliminate the use of commons in the kernel and modules, simplifying the module linking process and eliminating the risks associated with doubly-defined variables. Cases where commons were legitimately used (detection of compiled-in subsystems) have been converted to use sysinits, and any new code should use this or an equivalent practice as a matter of course. Modules can override this behaviour by substituting -fno-common out of ${CFLAGS} in cases where commons are necessary (eg. third-party object modules). Commons will be resolved and allocated space when the kld is linked as part of the module build process, so they will not pose a risk to the kernel or other modules. Provide a mechanism for controlling the export of symbols from the module namespace. The EXPORT_SYMS variable may be set in the Makefile to NO (export no symbols), a list of symbols to export, or the name of a file containing a newline-seperated list of symbols to be exported. Non-exported symbols are converted to local symbols. If EXPORT_SYMS is not set, all global symbols are currently exported. This behaviour is expected to change (to exporting no symbols) once modules have been converted. Reviewed by: peter (in principle) Obtained from: green (kmod_syms.awk)
2002-01-10 03:52:01 +00:00
LDFLAGS+= -d -warn-common
Add ${DEBUG_FLAGS} to CFLAGS in bsd.kmod.mk, not in scattered module makefiles. Bad examples in fxp/Makefile keep getting copied to new makefiles.
2000-01-28 11:26:46 +00:00
CFLAGS+= ${DEBUG_FLAGS}
Unconditionally add `-fno-omit-frame-pointer' to CFLAGS when building modules on the amd64 platform. Without this, ddb stack traces cannot follow module function calls, which makes debugging very difficult.
2004-08-29 02:00:50 +00:00
.if ${MACHINE_ARCH} == amd64
CFLAGS+= -fno-omit-frame-pointer
.endif
Add ${DEBUG_FLAGS} to CFLAGS in bsd.kmod.mk, not in scattered module makefiles. Bad examples in fxp/Makefile keep getting copied to new makefiles.
2000-01-28 11:26:46 +00:00
Modules on PPC need to be compiled with -mlongcall to get around the +/-64k blr offset limitation. With gcc bug #12769 fixed, it's time to put enable this.
2005-01-06 06:26:11 +00:00
.if ${MACHINE_ARCH} == "powerpc"
Don't lose the frame pointer for PPC modules: backtrace doesn't work.
2005-02-02 23:44:24 +00:00
CFLAGS+= -mlongcall -fno-omit-frame-pointer
Modules on PPC need to be compiled with -mlongcall to get around the +/-64k blr offset limitation. With gcc bug #12769 fixed, it's time to put enable this.
2005-01-06 06:26:11 +00:00
.endif
Style fixes, including: - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
2004-10-12 15:04:10 +00:00
OBJS+= ${SRCS:N*.h:R:S/$/.o/g}
A make system file for building LKMs, derived from bsd.prog.mk.
1994-09-14 21:59:28 +00:00
.if !defined(PROG)
Changes to support building of KLD modules. This includes the possibly to be removed KMODDEPS define.
1998-10-02 04:51:10 +00:00
PROG= ${KMOD}.ko
.endif
A make system file for building LKMs, derived from bsd.prog.mk.
1994-09-14 21:59:28 +00:00
Reduce the number of knobs controlling the build of debug modules to one, DEBUG_FLAGS, which is also compatible with <bsd.prog.mk>. Previously one had to set both DEBUG and DEBUG_FLAGS to build the .ko.debug with debugging symbols which was boring when doing this manually.
2004-02-13 10:40:54 +00:00
.if !defined(DEBUG_FLAGS)
When building a debugging kernel with modules, build modules with debugging support as well. Debugging module support is handled identically to kernel debugging support, right down to poor choice of make variable names.
2001-08-02 09:22:18 +00:00
FULLPROG= ${PROG}
.else
FULLPROG= ${PROG}.debug
${PROG}: ${FULLPROG}
${OBJCOPY} --strip-debug ${FULLPROG} ${PROG}
.endif
Enable first part of kld's on amd64. This is known to not work right yet, but building kld's is OK now and they can be loaded by kldload(2). (but the machine will likely crash soon afterwards, a "minor" problem :-) Brought to you by: my injured knee (from moving)
2004-05-16 20:11:38 +00:00
.if ${MACHINE_ARCH} != amd64
When building a debugging kernel with modules, build modules with debugging support as well. Debugging module support is handled identically to kernel debugging support, right down to poor choice of make variable names.
2001-08-02 09:22:18 +00:00
${FULLPROG}: ${KMOD}.kld
Remove KMODDEPS support. All our existing dependencies are specified via the MODULE_VERSION() and MODULE_DEPEND() macros that both the loader and kld system know how to deal with. The old DT_NEEDED tag is still supported by the loader (and will remain supported for a while) - but the kernel side presently doesn't know how to deal with DT_NEEDED.
2000-05-01 18:06:49 +00:00
${LD} -Bshareable ${LDFLAGS} -o ${.TARGET} ${KMOD}.kld
Reduce the number of knobs controlling the build of debug modules to one, DEBUG_FLAGS, which is also compatible with <bsd.prog.mk>. Previously one had to set both DEBUG and DEBUG_FLAGS to build the .ko.debug with debugging symbols which was boring when doing this manually.
2004-02-13 10:40:54 +00:00
.if !defined(DEBUG_FLAGS)
${OBJCOPY} --strip-debug ${.TARGET}
We didn't strip debugging symbols from .ko if DEBUG was undefined.
2004-02-13 09:39:45 +00:00
.endif
Enable first part of kld's on amd64. This is known to not work right yet, but building kld's is OK now and they can be loaded by kldload(2). (but the machine will likely crash soon afterwards, a "minor" problem :-) Brought to you by: my injured knee (from moving)
2004-05-16 20:11:38 +00:00
.endif
A make system file for building LKMs, derived from bsd.prog.mk.
1994-09-14 21:59:28 +00:00
Reverse the sense of EXPORT_SYMS. If EXPORT_SYMS is not defined, no symbols are exported from the module. This is the typical configuration for most device drivers and standalone modules; only infrastructure modules or those with special requirements typically need to export symbols. Don't print the objcopy commands as they are run when converting symbols; they're bulky and annoying in many cases.
2002-01-11 01:11:44 +00:00
EXPORT_SYMS?= NO
.if ${EXPORT_SYMS} != YES
Style fixes, including: - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
2004-10-12 15:04:10 +00:00
CLEANFILES+= export_syms
Eliminate the use of commons in the kernel and modules, simplifying the module linking process and eliminating the risks associated with doubly-defined variables. Cases where commons were legitimately used (detection of compiled-in subsystems) have been converted to use sysinits, and any new code should use this or an equivalent practice as a matter of course. Modules can override this behaviour by substituting -fno-common out of ${CFLAGS} in cases where commons are necessary (eg. third-party object modules). Commons will be resolved and allocated space when the kld is linked as part of the module build process, so they will not pose a risk to the kernel or other modules. Provide a mechanism for controlling the export of symbols from the module namespace. The EXPORT_SYMS variable may be set in the Makefile to NO (export no symbols), a list of symbols to export, or the name of a file containing a newline-seperated list of symbols to be exported. Non-exported symbols are converted to local symbols. If EXPORT_SYMS is not set, all global symbols are currently exported. This behaviour is expected to change (to exporting no symbols) once modules have been converted. Reviewed by: peter (in principle) Obtained from: green (kmod_syms.awk)
2002-01-10 03:52:01 +00:00
.endif
Enable first part of kld's on amd64. This is known to not work right yet, but building kld's is OK now and they can be loaded by kldload(2). (but the machine will likely crash soon afterwards, a "minor" problem :-) Brought to you by: my injured knee (from moving)
2004-05-16 20:11:38 +00:00
.if ${MACHINE_ARCH} != amd64
Remove KMODDEPS support. All our existing dependencies are specified via the MODULE_VERSION() and MODULE_DEPEND() macros that both the loader and kld system know how to deal with. The old DT_NEEDED tag is still supported by the loader (and will remain supported for a while) - but the kernel side presently doesn't know how to deal with DT_NEEDED.
2000-05-01 18:06:49 +00:00
${KMOD}.kld: ${OBJS}
Enable first part of kld's on amd64. This is known to not work right yet, but building kld's is OK now and they can be loaded by kldload(2). (but the machine will likely crash soon afterwards, a "minor" problem :-) Brought to you by: my injured knee (from moving)
2004-05-16 20:11:38 +00:00
.else
${FULLPROG}: ${OBJS}
.endif
Eliminate the use of commons in the kernel and modules, simplifying the module linking process and eliminating the risks associated with doubly-defined variables. Cases where commons were legitimately used (detection of compiled-in subsystems) have been converted to use sysinits, and any new code should use this or an equivalent practice as a matter of course. Modules can override this behaviour by substituting -fno-common out of ${CFLAGS} in cases where commons are necessary (eg. third-party object modules). Commons will be resolved and allocated space when the kld is linked as part of the module build process, so they will not pose a risk to the kernel or other modules. Provide a mechanism for controlling the export of symbols from the module namespace. The EXPORT_SYMS variable may be set in the Makefile to NO (export no symbols), a list of symbols to export, or the name of a file containing a newline-seperated list of symbols to be exported. Non-exported symbols are converted to local symbols. If EXPORT_SYMS is not set, all global symbols are currently exported. This behaviour is expected to change (to exporting no symbols) once modules have been converted. Reviewed by: peter (in principle) Obtained from: green (kmod_syms.awk)
2002-01-10 03:52:01 +00:00
${LD} ${LDFLAGS} -r -d -o ${.TARGET} ${OBJS}
.if defined(EXPORT_SYMS)
Reverse the sense of EXPORT_SYMS. If EXPORT_SYMS is not defined, no symbols are exported from the module. This is the typical configuration for most device drivers and standalone modules; only infrastructure modules or those with special requirements typically need to export symbols. Don't print the objcopy commands as they are run when converting symbols; they're bulky and annoying in many cases.
2002-01-11 01:11:44 +00:00
.if ${EXPORT_SYMS} != YES
Eliminate the use of commons in the kernel and modules, simplifying the module linking process and eliminating the risks associated with doubly-defined variables. Cases where commons were legitimately used (detection of compiled-in subsystems) have been converted to use sysinits, and any new code should use this or an equivalent practice as a matter of course. Modules can override this behaviour by substituting -fno-common out of ${CFLAGS} in cases where commons are necessary (eg. third-party object modules). Commons will be resolved and allocated space when the kld is linked as part of the module build process, so they will not pose a risk to the kernel or other modules. Provide a mechanism for controlling the export of symbols from the module namespace. The EXPORT_SYMS variable may be set in the Makefile to NO (export no symbols), a list of symbols to export, or the name of a file containing a newline-seperated list of symbols to be exported. Non-exported symbols are converted to local symbols. If EXPORT_SYMS is not set, all global symbols are currently exported. This behaviour is expected to change (to exporting no symbols) once modules have been converted. Reviewed by: peter (in principle) Obtained from: green (kmod_syms.awk)
2002-01-10 03:52:01 +00:00
.if ${EXPORT_SYMS} == NO
Style fixes, including: - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
2004-10-12 15:04:10 +00:00
touch export_syms
Eliminate the use of commons in the kernel and modules, simplifying the module linking process and eliminating the risks associated with doubly-defined variables. Cases where commons were legitimately used (detection of compiled-in subsystems) have been converted to use sysinits, and any new code should use this or an equivalent practice as a matter of course. Modules can override this behaviour by substituting -fno-common out of ${CFLAGS} in cases where commons are necessary (eg. third-party object modules). Commons will be resolved and allocated space when the kld is linked as part of the module build process, so they will not pose a risk to the kernel or other modules. Provide a mechanism for controlling the export of symbols from the module namespace. The EXPORT_SYMS variable may be set in the Makefile to NO (export no symbols), a list of symbols to export, or the name of a file containing a newline-seperated list of symbols to be exported. Non-exported symbols are converted to local symbols. If EXPORT_SYMS is not set, all global symbols are currently exported. This behaviour is expected to change (to exporting no symbols) once modules have been converted. Reviewed by: peter (in principle) Obtained from: green (kmod_syms.awk)
2002-01-10 03:52:01 +00:00
.elif !exists(${.CURDIR}/${EXPORT_SYMS})
Style fixes, including: - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
2004-10-12 15:04:10 +00:00
echo ${EXPORT_SYMS} > export_syms
Eliminate the use of commons in the kernel and modules, simplifying the module linking process and eliminating the risks associated with doubly-defined variables. Cases where commons were legitimately used (detection of compiled-in subsystems) have been converted to use sysinits, and any new code should use this or an equivalent practice as a matter of course. Modules can override this behaviour by substituting -fno-common out of ${CFLAGS} in cases where commons are necessary (eg. third-party object modules). Commons will be resolved and allocated space when the kld is linked as part of the module build process, so they will not pose a risk to the kernel or other modules. Provide a mechanism for controlling the export of symbols from the module namespace. The EXPORT_SYMS variable may be set in the Makefile to NO (export no symbols), a list of symbols to export, or the name of a file containing a newline-seperated list of symbols to be exported. Non-exported symbols are converted to local symbols. If EXPORT_SYMS is not set, all global symbols are currently exported. This behaviour is expected to change (to exporting no symbols) once modules have been converted. Reviewed by: peter (in principle) Obtained from: green (kmod_syms.awk)
2002-01-10 03:52:01 +00:00
.else
Style fixes, including: - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
2004-10-12 15:04:10 +00:00
grep -v '^#' < ${EXPORT_SYMS} > export_syms
Eliminate the use of commons in the kernel and modules, simplifying the module linking process and eliminating the risks associated with doubly-defined variables. Cases where commons were legitimately used (detection of compiled-in subsystems) have been converted to use sysinits, and any new code should use this or an equivalent practice as a matter of course. Modules can override this behaviour by substituting -fno-common out of ${CFLAGS} in cases where commons are necessary (eg. third-party object modules). Commons will be resolved and allocated space when the kld is linked as part of the module build process, so they will not pose a risk to the kernel or other modules. Provide a mechanism for controlling the export of symbols from the module namespace. The EXPORT_SYMS variable may be set in the Makefile to NO (export no symbols), a list of symbols to export, or the name of a file containing a newline-seperated list of symbols to be exported. Non-exported symbols are converted to local symbols. If EXPORT_SYMS is not set, all global symbols are currently exported. This behaviour is expected to change (to exporting no symbols) once modules have been converted. Reviewed by: peter (in principle) Obtained from: green (kmod_syms.awk)
2002-01-10 03:52:01 +00:00
.endif
awk -f ${SYSDIR}/conf/kmod_syms.awk ${.TARGET} \
Style fixes, including: - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
2004-10-12 15:04:10 +00:00
export_syms | xargs -J% ${OBJCOPY} % ${.TARGET}
Reverse the sense of EXPORT_SYMS. If EXPORT_SYMS is not defined, no symbols are exported from the module. This is the typical configuration for most device drivers and standalone modules; only infrastructure modules or those with special requirements typically need to export symbols. Don't print the objcopy commands as they are run when converting symbols; they're bulky and annoying in many cases.
2002-01-11 01:11:44 +00:00
.endif
Eliminate the use of commons in the kernel and modules, simplifying the module linking process and eliminating the risks associated with doubly-defined variables. Cases where commons were legitimately used (detection of compiled-in subsystems) have been converted to use sysinits, and any new code should use this or an equivalent practice as a matter of course. Modules can override this behaviour by substituting -fno-common out of ${CFLAGS} in cases where commons are necessary (eg. third-party object modules). Commons will be resolved and allocated space when the kld is linked as part of the module build process, so they will not pose a risk to the kernel or other modules. Provide a mechanism for controlling the export of symbols from the module namespace. The EXPORT_SYMS variable may be set in the Makefile to NO (export no symbols), a list of symbols to export, or the name of a file containing a newline-seperated list of symbols to be exported. Non-exported symbols are converted to local symbols. If EXPORT_SYMS is not set, all global symbols are currently exported. This behaviour is expected to change (to exporting no symbols) once modules have been converted. Reviewed by: peter (in principle) Obtained from: green (kmod_syms.awk)
2002-01-10 03:52:01 +00:00
.endif
Enable first part of kld's on amd64. This is known to not work right yet, but building kld's is OK now and they can be loaded by kldload(2). (but the machine will likely crash soon afterwards, a "minor" problem :-) Brought to you by: my injured knee (from moving)
2004-05-16 20:11:38 +00:00
.if !defined(DEBUG_FLAGS) && ${MACHINE_ARCH} == amd64
${OBJCOPY} --strip-debug ${.TARGET}
.endif
Eliminate the use of commons in the kernel and modules, simplifying the module linking process and eliminating the risks associated with doubly-defined variables. Cases where commons were legitimately used (detection of compiled-in subsystems) have been converted to use sysinits, and any new code should use this or an equivalent practice as a matter of course. Modules can override this behaviour by substituting -fno-common out of ${CFLAGS} in cases where commons are necessary (eg. third-party object modules). Commons will be resolved and allocated space when the kld is linked as part of the module build process, so they will not pose a risk to the kernel or other modules. Provide a mechanism for controlling the export of symbols from the module namespace. The EXPORT_SYMS variable may be set in the Makefile to NO (export no symbols), a list of symbols to export, or the name of a file containing a newline-seperated list of symbols to be exported. Non-exported symbols are converted to local symbols. If EXPORT_SYMS is not set, all global symbols are currently exported. This behaviour is expected to change (to exporting no symbols) once modules have been converted. Reviewed by: peter (in principle) Obtained from: green (kmod_syms.awk)
2002-01-10 03:52:01 +00:00
Generate symlinks to the "sys" and <machine> directories and put them in the include path. This fixes recent breakage of the syscons LKMs and general brokenness of the include paths (headers under /usr/include were used in many cases).
1998-01-26 20:36:38 +00:00
_ILINKS=@ machine
A make system file for building LKMs, derived from bsd.prog.mk.
1994-09-14 21:59:28 +00:00
Merge bsd.obj.mk's version of the _SUBDIR target with bsd.subdir.mk. Ensure all standard targets honor SUBDIR. Now `make obj' descends into SUBDIRs even if NOOBJ is set (some descendants may still need an object directory, but we do not have such precedents). Now `make install' in non-bsd.subdir.mk makefiles runs `afterinstall' target _after_ `install' in SUBDIRs, like we do in bsd.subdir.mk. Nothing depended on the wrong order anyway. Fixed `distribute' targets (except for the bsd.subdir.mk version) so that they do not depend on _SUBDIR; `distribute' calls `install' which already depends on _SUBDIR. De-standardize `maninstall', otherwise manpages would be installed twice. (To be revised later.)
2002-04-23 09:03:56 +00:00
all: objwarn ${PROG}
Generate symlinks to the "sys" and <machine> directories and put them in the include path. This fixes recent breakage of the syscons LKMs and general brokenness of the include paths (headers under /usr/include were used in many cases).
1998-01-26 20:36:38 +00:00
Move beforedepend: outside of the loop. # Note: we should remove the rm kludge soon. It fails in many cases. Submitted by: bde
2001-03-05 06:19:29 +00:00
beforedepend: ${_ILINKS}
If the symbolic links @ or machine exist, do not depend on them. This fixes the problem where if src/sys or src/sys/$MACHINE_ARCH/include changed at all, all the modules would be rebuilt. Reviewed by: bde
2001-02-23 04:49:31 +00:00
# Ensure that the links exist without depending on it when it exists which
# causes all the modules to be rebuilt when the directory pointed to changes.
.for _link in ${_ILINKS}
.if !exists(${.OBJDIR}/${_link})
${OBJS}: ${_link}
.endif
.endfor
Generate symlinks to the "sys" and <machine> directories and put them in the include path. This fixes recent breakage of the syscons LKMs and general brokenness of the include paths (headers under /usr/include were used in many cases).
1998-01-26 20:36:38 +00:00
Add support for compiling kernel modules outside of the tree. If you do not have the kernel you wish to compile against in either /usr/src/sys or /sys, then you will need to set SYSDIR to point to the sys directory of the source tree that contians the source. Also, minor tweaks to the load/unload targets from Bruce. I've had this through several make worlds, as well as using it on a daily basis for the past couple of weeks to build modules needed for testing at Timing Solutions. Reviewed and revised by: bde Work sponsored by: Timing Solutions
2000-04-08 17:20:00 +00:00
# Search for kernel source tree in standard places.
.for _dir in ${.CURDIR}/../.. ${.CURDIR}/../../.. /sys /usr/src/sys
Overdue reversion of revision 1.143. OK'ed by: imp
2004-03-06 21:23:56 +00:00
.if !defined(SYSDIR) && exists(${_dir}/kern/)
Add support for compiling kernel modules outside of the tree. If you do not have the kernel you wish to compile against in either /usr/src/sys or /sys, then you will need to set SYSDIR to point to the sys directory of the source tree that contians the source. Also, minor tweaks to the load/unload targets from Bruce. I've had this through several make worlds, as well as using it on a daily basis for the past couple of weeks to build modules needed for testing at Timing Solutions. Reviewed and revised by: bde Work sponsored by: Timing Solutions
2000-04-08 17:20:00 +00:00
SYSDIR= ${_dir}
.endif
.endfor
Overdue reversion of revision 1.143. OK'ed by: imp
2004-03-06 21:23:56 +00:00
.if !defined(SYSDIR) || !exists(${SYSDIR}/kern/)
Add support for compiling kernel modules outside of the tree. If you do not have the kernel you wish to compile against in either /usr/src/sys or /sys, then you will need to set SYSDIR to point to the sys directory of the source tree that contians the source. Also, minor tweaks to the load/unload targets from Bruce. I've had this through several make worlds, as well as using it on a daily basis for the past couple of weeks to build modules needed for testing at Timing Solutions. Reviewed and revised by: bde Work sponsored by: Timing Solutions
2000-04-08 17:20:00 +00:00
.error "can't find kernel source tree"
.endif
Update the kld glue Pre-Approved by: jkh
1998-10-16 03:32:03 +00:00
${_ILINKS}:
Add support for compiling kernel modules outside of the tree. If you do not have the kernel you wish to compile against in either /usr/src/sys or /sys, then you will need to set SYSDIR to point to the sys directory of the source tree that contians the source. Also, minor tweaks to the load/unload targets from Bruce. I've had this through several make worlds, as well as using it on a daily basis for the past couple of weeks to build modules needed for testing at Timing Solutions. Reviewed and revised by: bde Work sponsored by: Timing Solutions
2000-04-08 17:20:00 +00:00
@case ${.TARGET} in \
machine) \
path=${SYSDIR}/${MACHINE_ARCH}/include ;; \
@) \
path=${SYSDIR} ;; \
esac ; \
Update the kld glue Pre-Approved by: jkh
1998-10-16 03:32:03 +00:00
path=`(cd $$path && /bin/pwd)` ; \
${ECHO} ${.TARGET} "->" $$path ; \
ln -s $$path ${.TARGET}
Generate symlinks to the "sys" and <machine> directories and put them in the include path. This fixes recent breakage of the syscons LKMs and general brokenness of the include paths (headers under /usr/include were used in many cases).
1998-01-26 20:36:38 +00:00
Style fixes, including: - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
2004-10-12 15:04:10 +00:00
CLEANFILES+= ${PROG} ${KMOD}.kld ${OBJS} ${_ILINKS}
In the !DEBUG case, we were passing foo.ko two times on the rm -f command line when doing a make clean. Fix this. Reviewed by: ru
2002-11-06 17:40:13 +00:00
Reduce the number of knobs controlling the build of debug modules to one, DEBUG_FLAGS, which is also compatible with <bsd.prog.mk>. Previously one had to set both DEBUG and DEBUG_FLAGS to build the .ko.debug with debugging symbols which was boring when doing this manually.
2004-02-13 10:40:54 +00:00
.if defined(DEBUG_FLAGS)
In the !DEBUG case, we were passing foo.ko two times on the rm -f command line when doing a make clean. Fix this. Reviewed by: ru
2002-11-06 17:40:13 +00:00
CLEANFILES+= ${FULLPROG}
.endif
A make system file for building LKMs, derived from bsd.prog.mk.
1994-09-14 21:59:28 +00:00
.if !target(install)
Don't install KO's with the "schg" flag. We are way too inconsistent with our setting of the "schg" flag, and in our default install, it doesn't really offer any additional security. Reviewed by: arch@
2001-04-25 20:56:15 +00:00
_INSTALLFLAGS:= ${INSTALLFLAGS}
Add variable INSTALLFLAGS_EDIT used to remove arbitrary INSTALLFLAGS. Specifically intended for removing -fschg ("INSTALLFLAGS_EDIT=:S/schg/uchg/") this makes the NOFSCHG flag redundant. NOFSCHG will still be honoured by bsd.lib.mk but is valid for buildworld only. NOFSCHG is still implemented in the old way (ie. _not_ ".if NOFSCHG then { INSTALLFLAGS_EDIT+=:S/schg/,/ }" to emphasize the fact that NOFSCHG is only supported in a limited fashion and for buildworld. The interface and implementation are such that future use of flags such as sappnd can also be easily removed or altered (perhaps to uappnd). This commit brought to you by the letters B, D, and E, and the numbers six, one, thirteen, and three.
1999-07-31 20:27:33 +00:00
.for ie in ${INSTALLFLAGS_EDIT}
_INSTALLFLAGS:= ${_INSTALLFLAGS${ie}}
.endfor
Style fixes, including: - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
2004-10-12 15:04:10 +00:00
.if !target(install.debug) && defined(DEBUG_FLAGS)
Merge bsd.obj.mk's version of the _SUBDIR target with bsd.subdir.mk. Ensure all standard targets honor SUBDIR. Now `make obj' descends into SUBDIRs even if NOOBJ is set (some descendants may still need an object directory, but we do not have such precedents). Now `make install' in non-bsd.subdir.mk makefiles runs `afterinstall' target _after_ `install' in SUBDIRs, like we do in bsd.subdir.mk. Nothing depended on the wrong order anyway. Fixed `distribute' targets (except for the bsd.subdir.mk version) so that they do not depend on _SUBDIR; `distribute' calls `install' which already depends on _SUBDIR. De-standardize `maninstall', otherwise manpages would be installed twice. (To be revised later.)
2002-04-23 09:03:56 +00:00
install.debug:
The install.debug and reinstall.debug targets are needed solely to build kernel and kernel modules so stop supporting them in bsd.subdir.mk and reimplement them in kern.post.mk and kmod.mk as special versions of the install and reinstall targets, and only define them if DEBUG is also defined (when debug versions are really built). Prompted by: bde
2002-04-24 11:26:19 +00:00
cd ${.CURDIR}; ${MAKE} -DINSTALL_DEBUG install
.endif
Support the "install.debug" and "reinstall.debug" targets for kernel modules. Small tweaks to kldxref may be necessary to avoid the surprising (but harm- less) behaviour of 'kldload foo' loading foo.ko.debug instead of foo.ko if it is present in the kernel directory. Approved by: a week of silence on -arch MFC after: 2 weeks
2001-10-27 00:52:50 +00:00
Handle installation of links through bsd.links.mk. Removed comments that no longer directly apply here.
2002-07-17 08:21:50 +00:00
.if !target(realinstall)
realinstall: _kmodinstall
.ORDER: beforeinstall _kmodinstall
_kmodinstall:
Reduce the number of knobs controlling the build of debug modules to one, DEBUG_FLAGS, which is also compatible with <bsd.prog.mk>. Previously one had to set both DEBUG and DEBUG_FLAGS to build the .ko.debug with debugging symbols which was boring when doing this manually.
2004-02-13 10:40:54 +00:00
.if defined(DEBUG_FLAGS) && defined(INSTALL_DEBUG)
Drop support for COPY, -c has been the default mode of install(1) for a long time now. Approved by: bde
2002-07-29 09:40:17 +00:00
${INSTALL} -o ${KMODOWN} -g ${KMODGRP} -m ${KMODMODE} \
Handle installation of links through bsd.links.mk. Removed comments that no longer directly apply here.
2002-07-17 08:21:50 +00:00
${_INSTALLFLAGS} ${FULLPROG} ${DESTDIR}${KMODDIR}
The install.debug and reinstall.debug targets are needed solely to build kernel and kernel modules so stop supporting them in bsd.subdir.mk and reimplement them in kern.post.mk and kmod.mk as special versions of the install and reinstall targets, and only define them if DEBUG is also defined (when debug versions are really built). Prompted by: bde
2002-04-24 11:26:19 +00:00
.else
Drop support for COPY, -c has been the default mode of install(1) for a long time now. Approved by: bde
2002-07-29 09:40:17 +00:00
${INSTALL} -o ${KMODOWN} -g ${KMODGRP} -m ${KMODMODE} \
Handle installation of links through bsd.links.mk. Removed comments that no longer directly apply here.
2002-07-17 08:21:50 +00:00
${_INSTALLFLAGS} ${PROG} ${DESTDIR}${KMODDIR}
.include <bsd.links.mk>
Run kldxref on sparc64, it works now.
2003-01-21 05:52:48 +00:00
.if !defined(NO_XREF)
Handle installation of links through bsd.links.mk. Removed comments that no longer directly apply here.
2002-07-17 08:21:50 +00:00
afterinstall: _kldxref
.ORDER: realinstall _kldxref
.ORDER: _installlinks _kldxref
_kldxref:
Check that kldxref(8) exists before running it.
2002-05-14 07:49:12 +00:00
@if type kldxref >/dev/null 2>&1; then \
${ECHO} kldxref ${DESTDIR}${KMODDIR}; \
kldxref ${DESTDIR}${KMODDIR}; \
fi
Implement the long-awaited module->file cache database. A userland tool (kldxref(8)) keeps a cache of what modules and versions are inside what .ko files. I have tested this on both Alpha and i386. Submitted by: bp
2001-09-11 01:09:24 +00:00
.endif
The install.debug and reinstall.debug targets are needed solely to build kernel and kernel modules so stop supporting them in bsd.subdir.mk and reimplement them in kern.post.mk and kmod.mk as special versions of the install and reinstall targets, and only define them if DEBUG is also defined (when debug versions are really built). Prompted by: bde
2002-04-24 11:26:19 +00:00
.endif
Handle installation of links through bsd.links.mk. Removed comments that no longer directly apply here.
2002-07-17 08:21:50 +00:00
.endif !target(realinstall)
A make system file for building LKMs, derived from bsd.prog.mk.
1994-09-14 21:59:28 +00:00
Handle installation of links through bsd.links.mk. Removed comments that no longer directly apply here.
2002-07-17 08:21:50 +00:00
.endif !target(install)
A make system file for building LKMs, derived from bsd.prog.mk.
1994-09-14 21:59:28 +00:00
.if !target(load)
Style fixes, including: - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
2004-10-12 15:04:10 +00:00
load: ${PROG}
${KMODLOAD} -v ${.OBJDIR}/${PROG}
A make system file for building LKMs, derived from bsd.prog.mk.
1994-09-14 21:59:28 +00:00
.endif
.if !target(unload)
1) s/mod(un)?load/kld$1load/ 2) s/MODLOAD/KMODLOAD/ to be consistent with the rest of the variables (KMOD, KMODOWN, KMODGRP, etc) and definition of MODLOAD/UNLOAD in the Makefile of the ATAPI module 3) textual fixups
1999-09-06 20:11:59 +00:00
unload:
Style fixes, including: - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
2004-10-12 15:04:10 +00:00
${KMODUNLOAD} -v ${PROG}
Update the kld glue Pre-Approved by: jkh
1998-10-16 03:32:03 +00:00
.endif
Make it easier to create filesystem LKMs by doing most of the work in the Makefile. Just define VFS_LKM and you're off!
1994-09-21 03:49:59 +00:00
Fix the building of null module. In the DIAGNOSTICS case, we include opt_ddb.h. These changes expand green's work of including opt_global.h to prefer opt files in the kernel directory. Further refinement might be needed, but I think this is good. Note: While this is a step on the path to moving the meta information about modules into the config files, it doesn't actually do that. It just pulls in the opt files in a way that allows one to build 'generic' modules outside the tree.
2003-11-16 01:41:38 +00:00
.if defined(KERNBUILDDIR)
.PATH: ${KERNBUILDDIR}
Style fixes, including: - Sort kmod.mk knobs in the documentation section. - Fixed misuses of the word "KLD" which stands for "kernel ld", or "kernel linker", where kernel module is meant. - Removed redundant uses of ${.OBJDIR}. - Whitespace and indentation fixes. - CLEANFILES cleanup. - Target redefinition protection (install.debug). Submitted by: bde, ru Reviewed by: ru, bde
2004-10-12 15:04:10 +00:00
CFLAGS+= -I${KERNBUILDDIR}
Fix the building of null module. In the DIAGNOSTICS case, we include opt_ddb.h. These changes expand green's work of including opt_global.h to prefer opt files in the kernel directory. Further refinement might be needed, but I think this is good. Note: While this is a step on the path to moving the meta information about modules into the config files, it doesn't actually do that. It just pulls in the opt files in a way that allows one to build 'generic' modules outside the tree.
2003-11-16 01:41:38 +00:00
.for _src in ${SRCS:Mopt_*.h}
CLEANFILES+= ${_src}
.if !target(${_src})
${_src}:
Revert the change from rev 1.168. ru convinced me that the situation that was fixed by this should not normally happen, and since I did not record the traces of my failed build attempt that had been solved with that change, it's not entirely clear whether it hadn't been a pilot error on my end. In dubio pro reo. :-)
2004-10-11 21:23:56 +00:00
ln -s ${KERNBUILDDIR}/${_src} ${.TARGET}
Fix the building of null module. In the DIAGNOSTICS case, we include opt_ddb.h. These changes expand green's work of including opt_global.h to prefer opt files in the kernel directory. Further refinement might be needed, but I think this is good. Note: While this is a step on the path to moving the meta information about modules into the config files, it doesn't actually do that. It just pulls in the opt files in a way that allows one to build 'generic' modules outside the tree.
2003-11-16 01:41:38 +00:00
.endif
.endfor
.else
Build and clean device interface files (foo_if.[ch]) and empty options files (opt_*.h) automatically (if they are in ${SRCS}). Clean vnode_if.[ch] automatically (if one of them is in ${SRCS}, not just if VFS_KLD is defined). There are some complications to avoid using the "@" symlink before it is built.
1999-11-28 17:52:40 +00:00
.for _src in ${SRCS:Mopt_*.h}
CLEANFILES+= ${_src}
.if !target(${_src})
${_src}:
touch ${.TARGET}
.endif
.endfor
Fix the building of null module. In the DIAGNOSTICS case, we include opt_ddb.h. These changes expand green's work of including opt_global.h to prefer opt files in the kernel directory. Further refinement might be needed, but I think this is good. Note: While this is a step on the path to moving the meta information about modules into the config files, it doesn't actually do that. It just pulls in the opt files in a way that allows one to build 'generic' modules outside the tree.
2003-11-16 01:41:38 +00:00
.endif
Build and clean device interface files (foo_if.[ch]) and empty options files (opt_*.h) automatically (if they are in ${SRCS}). Clean vnode_if.[ch] automatically (if one of them is in ${SRCS}, not just if VFS_KLD is defined). There are some complications to avoid using the "@" symlink before it is built.
1999-11-28 17:52:40 +00:00
Sort MFILES.
2004-11-20 06:09:11 +00:00
MFILES?= dev/acpica/acpi_if.m dev/eisa/eisa_if.m dev/iicbus/iicbb_if.m \
dev/iicbus/iicbus_if.m dev/mii/miibus_if.m dev/ofw/ofw_bus_if.m \
dev/pccard/card_if.m dev/pccard/power_if.m dev/pci/pci_if.m \
dev/pci/pcib_if.m dev/ppbus/ppbus_if.m dev/smbus/smbus_if.m \
dev/sound/pcm/ac97_if.m dev/sound/pcm/channel_if.m \
dev/sound/pcm/feeder_if.m dev/sound/pcm/mixer_if.m dev/uart/uart_if.m \
dev/usb/usb_if.m isa/isa_if.m kern/bus_if.m kern/device_if.m \
libkern/iconv_converter_if.m opencrypto/crypto_if.m \
Revert rev. 1.166 and remove sparc64/pci/ofw_pci_if.m from MFILES again, sparc64/pci/ofw_pci.h is no longer required for compiling modules.
2004-12-04 14:20:56 +00:00
pc98/pc98/canbus_if.m pci/agp_if.m
Allow the calling Makefile to specify a list of device interfaces instead of relying on the default list provided here.
2000-04-05 10:13:05 +00:00
.for _srcsrc in ${MFILES}
Build and clean device interface files (foo_if.[ch]) and empty options files (opt_*.h) automatically (if they are in ${SRCS}). Clean vnode_if.[ch] automatically (if one of them is in ${SRCS}, not just if VFS_KLD is defined). There are some complications to avoid using the "@" symlink before it is built.
1999-11-28 17:52:40 +00:00
.for _ext in c h
.for _src in ${SRCS:M${_srcsrc:T:R}.${_ext}}
CLEANFILES+= ${_src}
.if !target(${_src})
If the symbolic links @ or machine exist, do not depend on them. This fixes the problem where if src/sys or src/sys/$MACHINE_ARCH/include changed at all, all the modules would be rebuilt. Reviewed by: bde
2001-02-23 04:49:31 +00:00
.if !exists(@)
Build and clean device interface files (foo_if.[ch]) and empty options files (opt_*.h) automatically (if they are in ${SRCS}). Clean vnode_if.[ch] automatically (if one of them is in ${SRCS}, not just if VFS_KLD is defined). There are some complications to avoid using the "@" symlink before it is built.
1999-11-28 17:52:40 +00:00
${_src}: @
Properly handle vnode_if.h dependencies, and don't forget to clean all files.
2004-12-08 07:23:12 +00:00
.else
Use makeobjops.awk rather than makeobjops.pl. (with big thanks to Oliver Fromme <olli@fromme.com>)
2002-05-01 03:28:14 +00:00
${_src}: @/tools/makeobjops.awk @/${_srcsrc}
Build and clean device interface files (foo_if.[ch]) and empty options files (opt_*.h) automatically (if they are in ${SRCS}). Clean vnode_if.[ch] automatically (if one of them is in ${SRCS}, not just if VFS_KLD is defined). There are some complications to avoid using the "@" symlink before it is built.
1999-11-28 17:52:40 +00:00
.endif
Use makeobjops.awk rather than makeobjops.pl. (with big thanks to Oliver Fromme <olli@fromme.com>)
2002-05-01 03:28:14 +00:00
${AWK} -f @/tools/makeobjops.awk @/${_srcsrc} -${_ext}
Build and clean device interface files (foo_if.[ch]) and empty options files (opt_*.h) automatically (if they are in ${SRCS}). Clean vnode_if.[ch] automatically (if one of them is in ${SRCS}, not just if VFS_KLD is defined). There are some complications to avoid using the "@" symlink before it is built.
1999-11-28 17:52:40 +00:00
.endif
.endfor # _src
.endfor # _ext
.endfor # _srcsrc
Unbreak KLDs that use VFS by accounting for changes in the generation process for the vnode header files.
2004-12-08 03:54:32 +00:00
.if ${SRCS:Mvnode_if.c} != ""
CLEANFILES+= vnode_if.c
If the symbolic links @ or machine exist, do not depend on them. This fixes the problem where if src/sys or src/sys/$MACHINE_ARCH/include changed at all, all the modules would be rebuilt. Reviewed by: bde
2001-02-23 04:49:31 +00:00
.if !exists(@)
Unbreak KLDs that use VFS by accounting for changes in the generation process for the vnode header files.
2004-12-08 03:54:32 +00:00
vnode_if.c: @
Properly handle vnode_if.h dependencies, and don't forget to clean all files.
2004-12-08 07:23:12 +00:00
.else
Unbreak KLDs that use VFS by accounting for changes in the generation process for the vnode header files.
2004-12-08 03:54:32 +00:00
vnode_if.c: @/tools/vnode_if.awk @/kern/vnode_if.src
Build and clean device interface files (foo_if.[ch]) and empty options files (opt_*.h) automatically (if they are in ${SRCS}). Clean vnode_if.[ch] automatically (if one of them is in ${SRCS}, not just if VFS_KLD is defined). There are some complications to avoid using the "@" symlink before it is built.
1999-11-28 17:52:40 +00:00
.endif
Unbreak KLDs that use VFS by accounting for changes in the generation process for the vnode header files.
2004-12-08 03:54:32 +00:00
${AWK} -f @/tools/vnode_if.awk @/kern/vnode_if.src -c
.endif
.if ${SRCS:Mvnode_if.h} != ""
Properly handle vnode_if.h dependencies, and don't forget to clean all files.
2004-12-08 07:23:12 +00:00
CLEANFILES+= vnode_if.h vnode_if_newproto.h vnode_if_typedef.h
Unbreak KLDs that use VFS by accounting for changes in the generation process for the vnode header files.
2004-12-08 03:54:32 +00:00
.if !exists(@)
Properly handle vnode_if.h dependencies, and don't forget to clean all files.
2004-12-08 07:23:12 +00:00
vnode_if.h vnode_if_newproto.h vnode_if_typedef.h: @
.else
vnode_if.h vnode_if_newproto.h vnode_if_typedef.h: @/tools/vnode_if.awk \
@/kern/vnode_if.src
Unbreak KLDs that use VFS by accounting for changes in the generation process for the vnode header files.
2004-12-08 03:54:32 +00:00
.endif
Properly handle vnode_if.h dependencies, and don't forget to clean all files.
2004-12-08 07:23:12 +00:00
vnode_if.h: vnode_if_newproto.h vnode_if_typedef.h
Unbreak KLDs that use VFS by accounting for changes in the generation process for the vnode header files.
2004-12-08 03:54:32 +00:00
${AWK} -f @/tools/vnode_if.awk @/kern/vnode_if.src -h
Properly handle vnode_if.h dependencies, and don't forget to clean all files.
2004-12-08 07:23:12 +00:00
vnode_if_newproto.h:
Unbreak KLDs that use VFS by accounting for changes in the generation process for the vnode header files.
2004-12-08 03:54:32 +00:00
${AWK} -f @/tools/vnode_if.awk @/kern/vnode_if.src -p
Properly handle vnode_if.h dependencies, and don't forget to clean all files.
2004-12-08 07:23:12 +00:00
vnode_if_typedef.h:
Unbreak KLDs that use VFS by accounting for changes in the generation process for the vnode header files.
2004-12-08 03:54:32 +00:00
${AWK} -f @/tools/vnode_if.awk @/kern/vnode_if.src -q
Build and clean device interface files (foo_if.[ch]) and empty options files (opt_*.h) automatically (if they are in ${SRCS}). Clean vnode_if.[ch] automatically (if one of them is in ${SRCS}, not just if VFS_KLD is defined). There are some complications to avoid using the "@" symlink before it is built.
1999-11-28 17:52:40 +00:00
.endif
Make it easier to create filesystem LKMs by doing most of the work in the Makefile. Just define VFS_LKM and you're off!
1994-09-21 03:49:59 +00:00
Remove special case from *devs2h loop for usb Move usb out of the loop since the other devs2h programs don't grok -h Add new rule for usbdevs_data.h
2004-12-30 23:22:08 +00:00
.for _i in mii pccard
Move to generating pccarddevs.h on the fly, both for the kernel and the modules. Also generate usbdevs.h automatically now, but a non-kernel file is stopping that at the moment.
2004-05-26 00:53:10 +00:00
.if ${SRCS:M${_i}devs.h} != ""
CLEANFILES+= ${_i}devs.h
Remove miidevs.h and generate it from miidevs at compile time. The devlist2h.awk tool to do this has been repocopied to sys/tools/.
2003-01-19 02:59:34 +00:00
.if !exists(@)
Move to generating pccarddevs.h on the fly, both for the kernel and the modules. Also generate usbdevs.h automatically now, but a non-kernel file is stopping that at the moment.
2004-05-26 00:53:10 +00:00
${_i}devs.h: @
Properly handle vnode_if.h dependencies, and don't forget to clean all files.
2004-12-08 07:23:12 +00:00
.else
Move to generating pccarddevs.h on the fly, both for the kernel and the modules. Also generate usbdevs.h automatically now, but a non-kernel file is stopping that at the moment.
2004-05-26 00:53:10 +00:00
${_i}devs.h: @/tools/${_i}devs2h.awk @/dev/${_i}/${_i}devs
Remove miidevs.h and generate it from miidevs at compile time. The devlist2h.awk tool to do this has been repocopied to sys/tools/.
2003-01-19 02:59:34 +00:00
.endif
Move to generating pccarddevs.h on the fly, both for the kernel and the modules. Also generate usbdevs.h automatically now, but a non-kernel file is stopping that at the moment.
2004-05-26 00:53:10 +00:00
${AWK} -f @/tools/${_i}devs2h.awk @/dev/${_i}/${_i}devs
Remove miidevs.h and generate it from miidevs at compile time. The devlist2h.awk tool to do this has been repocopied to sys/tools/.
2003-01-19 02:59:34 +00:00
.endif
Move to generating pccarddevs.h on the fly, both for the kernel and the modules. Also generate usbdevs.h automatically now, but a non-kernel file is stopping that at the moment.
2004-05-26 00:53:10 +00:00
.endfor # _i
Remove miidevs.h and generate it from miidevs at compile time. The devlist2h.awk tool to do this has been repocopied to sys/tools/.
2003-01-19 02:59:34 +00:00
Remove special case from *devs2h loop for usb Move usb out of the loop since the other devs2h programs don't grok -h Add new rule for usbdevs_data.h
2004-12-30 23:22:08 +00:00
.if ${SRCS:Musbdevs.h} != ""
CLEANFILES+= usbdevs.h
.if !exists(@)
usbdevs.h: @
.else
usbdevs.h: @/tools/usbdevs2h.awk @/dev/usb/usbdevs
.endif
${AWK} -f @/tools/usbdevs2h.awk @/dev/usb/usbdevs -h
.endif
.if ${SRCS:Musbdevs_data.h} != ""
CLEANFILES+= usbdevs_data.h
.if !exists(@)
usbdevs_data.h: @
.else
usbdevs_data.h: @/tools/usbdevs2h.awk @/dev/usb/usbdevs
.endif
${AWK} -f @/tools/usbdevs2h.awk @/dev/usb/usbdevs -d
.endif
Hook acpi_quirks up to the build for kernel and modules.
2004-06-24 06:29:22 +00:00
.if ${SRCS:Macpi_quirks.h} != ""
CLEANFILES+= acpi_quirks.h
.if !exists(@)
acpi_quirks.h: @
Properly handle vnode_if.h dependencies, and don't forget to clean all files.
2004-12-08 07:23:12 +00:00
.else
Hook acpi_quirks up to the build for kernel and modules.
2004-06-24 06:29:22 +00:00
acpi_quirks.h: @/tools/acpi_quirks2h.awk @/dev/acpica/acpi_quirks
.endif
${AWK} -f @/tools/acpi_quirks2h.awk @/dev/acpica/acpi_quirks
.endif
Allow "make lint" to mostly work. Our sources are very unclean WRT lint, so this is turned off by default. Setting WANT_LINT will turn on generation of lint libraries for /usr/libdata/lint/*.ln. Reviewd by: silence in -audit.
2002-03-17 10:05:57 +00:00
lint: ${SRCS}
lint the previous lint commit. Reviewed by: markm
2002-03-18 09:35:45 +00:00
${LINT} ${LINTKERNFLAGS} ${CFLAGS:M-[DILU]*} ${.ALLSRC:M*.c}
Allow "make lint" to mostly work. Our sources are very unclean WRT lint, so this is turned off by default. Setting WANT_LINT will turn on generation of lint libraries for /usr/libdata/lint/*.ln. Reviewd by: silence in -audit.
2002-03-17 10:05:57 +00:00
Fix the ordering dependency I broke.
1996-06-30 22:16:19 +00:00
.include <bsd.dep.mk>
Fixed dependencies of ${PROG} on ${DPSRCS} and `all' on ${_ILINKS}. There were various races for `make -j'. Half-built versions of vnode_if.h were sometimes #included... Removed a null dependency.
1998-03-06 05:43:46 +00:00
exists() is too aggressive when searching for files without a full path. Inspired by: bsd.prog.mk,v 1.105
2003-03-03 22:51:22 +00:00
.if !exists(${.OBJDIR}/${DEPENDFILE})
Removed support for now-unused FreeBSD misfeature DPSRCS.
1998-03-06 07:28:01 +00:00
${OBJS}: ${SRCS:M*.h}
Fixed dependencies of ${PROG} on ${DPSRCS} and `all' on ${_ILINKS}. There were various races for `make -j'. Half-built versions of vnode_if.h were sometimes #included... Removed a null dependency.
1998-03-06 05:43:46 +00:00
.endif
Fixed `make depend', which I broke here about a month ago by moving the null default for `depend' from bsd.dep.mk to bsd.obj.mk. bsd.kmod.mk included these files in a bad order, so it picked up the null default.
1998-06-09 02:55:40 +00:00
.include <bsd.obj.mk>
Initiate the de-orbit burn sequence for <bsd.kern.mk>. Always use sys/conf/kern.mk when building kernel/modules. <bsd.kern.mk> is only preserved for sys/boot/pc98/boot2 for now, but this will be fixed. If there are other users of <bsd.kern.mk>, please let me know. Reminded by: bde
2003-02-28 22:12:17 +00:00
.include "kern.mk"
Reference in New Issue Copy Permalink