summaryrefslogtreecommitdiffstats
path: root/sys/conf/kern.post.mk
Commit message (Collapse)AuthorAgeFilesLines
* Minor cleanups to post.mk from bde. Mostly orderingimp2002-03-201-26/+32
|
* Backed out the part of the previous commit related to xargs. It justbde2002-03-191-6/+4
| | | | | broke things, since "name=value ... cmd ..." only works for simple commands (not for pipelines).
* Removed env(1) commands. make(1) uses a real shell, andbde2002-03-191-14/+16
| | | | | | | "env name=value ... cmd ..." is just a pessimized way of doing "name=value ... cmd ..." in real shells. Set the environment (without using env(1)) before starting xargs so that env(1) is not needed in "xargs env name=value ... cmd ..."
* lint the previous lint commit.ru2002-03-181-1/+1
| | | | Reviewed by: markm
* Allow "make lint" to mostly work. Our sources are very unclean WRTmarkm2002-03-171-0/+3
| | | | | | | 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.
* Use vnode_if.awk rather than vnode_if.plobrien2002-03-011-4/+4
|
* Don't echo a comment during make depend.jake2002-02-231-3/+2
|
* Use make -V VARIABLE | xargs ... to pass argument lists to programluigi2002-02-221-5/+8
| | | | | | | | | | | | | so that this is safe even if VARIABLE is longer than kern.argmax. There is another instance of CFILES which might need the same treatment, and might be noticed when doing a "make links". The same has to be done in RELENG_4 (on some different file). Noticed-by: picobsd cross-compiling LINT Suggested-by: Alfred (bright@mu.org), des@freebsd.org MFC-after: 3 days
* Eliminate the use of commons in the kernel and modules,msmith2002-01-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* s/oferride/override/imp2002-01-061-1/+1
| | | | submitted by: dima
* Move initialization of the MKMODULESENV envorinoment to kern.pre.mkimp2002-01-051-14/+4
| | | | | | from kern.post.mk so port makefiles can augment it. Submitted by: nyan
* Move all: target to kern.pre.mk so it matters less where you includeimp2001-11-111-2/+0
| | | | | | | | | kern.post.mk. # this should allow us to move kern.post.mk to the last line of the makefiles, # but I'll do that slowly as I verify that one can do that w/o breaking things. Submitted by: naddy
* Move machine link creation from genassym to kernel-depend, per nyan@imp2001-11-041-3/+3
|
* Arrgh. A clean pc98 build failed due to bogons on my part :-(.imp2001-11-021-0/+3
| | | | | | | | Fix it by putting back the link of machine to sys/i386/include rather than ../../include (aka sys/pc98/include). I had a stale machine link on my first test. Not sure what the "right" fix is, but this unbreaks things.
* Factor the common parts of the Makefile.foo files. This introduces twoimp2001-11-021-0/+240
new files: kern.pre.mk, which contains most of the definitions, and kern.post.mk, which contains most of the rules. I've tested this on i386 and pc98. I have had feedback on the sparc64 port, but no reports from anybody on alpha, ia64 or powerpc. I appologize in advance if I've broken you. Reviewed by: jake, jhb, arch@
OpenPOWER on IntegriCloud