#
272461 |
|
02-Oct-2014 |
gjb |
Copy stable/10@r272459 to releng/10.1 as part of the 10.1-RELEASE process.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
256281 |
|
10-Oct-2013 |
gjb |
Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
|
#
231834 |
|
16-Feb-2012 |
imp |
Fix comma splice, can't ambiguity and quoting.
Submitted by: bde@ MFC after: 2 weeks
|
#
231780 |
|
15-Feb-2012 |
imp |
Wordsmith the can't find kernel error message, and suggest which variable to set to override.
|
#
183736 |
|
09-Oct-2008 |
imp |
ata module additions now nest ata modules one deeper than any prior module. Increase heuristic used to find them by one.
|
#
130854 |
|
21-Jun-2004 |
bde |
Fixed style bugs in previous commit (151 characters of trailing whitespace).
|
#
130835 |
|
21-Jun-2004 |
pjd |
- Missing trailing slash for a kern directory check. - Check in both places if ${_dir}/conf/kmod.mk exists. - Style fixes (lines too long).
Submitted by: bde
|
#
130693 |
|
18-Jun-2004 |
pjd |
Check if ${_dir}/kern exists as well, because if it doesn't exists we will fail later and we can miss good kernel source tree directory. I found this trying to compile kld module and it finds 'conf/kmod.mk' in '../..', but it fails later, because there is no 'kern' directory, but there is valid kernel source tree still in /usr/src/sys/.
|
#
76862 |
|
19-May-2001 |
kris |
(Previous commit was made prematurely before I could finish composing the log message)
Bring in the WARNS directive from NetBSD, localized in a new bsd.sys.mk to avoid polluting sys.mk. This directive controls the addition of compiler warning flags to CFLAGS in a relatively compiler-neutral manner.
The idea is that WARNS can be set in Makefile.inc or in individual Makefiles as they become clean, to prevent the introduction of new warnings in the code (-Werror is added by default when WARNS > 0).
This behaviour can be overridden with the following two knobs: NO_WARNS disables the checking of WARNS completely NO_WERROR disables the addition of -Werror to the flags.
Additionally, setting WFORMAT to 1 (in makefiles) and/or defining FORMAT_AUDIT (by the user) will enable increased checking of format string arguments.
Obtained from: NetBSD Reviewed by: peter
|
#
76861 |
|
19-May-2001 |
kris |
Bring in the WARNS directive from NetBSD, localized in a new bsd.sys.mk to avoid polluting sys.mk. This directive controls the addition of compiler warning flags to CFLAGS in a relatively compiler-neutral manner.
The idea is that WARNS can be set in Makefile.inc or in individual Makefiles as they become clean, to prevent the introduction of new warnings in the code. -Werror is added by default
|
#
69775 |
|
08-Dec-2000 |
jasone |
Do not check for existence of ${_dir}/kern/ , because for modules that set .PATH to ${.CURDIR}/[...]/kern , the "exists" expression will fail for the form exists(${.CURDIR}/[...]/kern/). This appears to be happening because make is searching for the argument to "exists" by using .PATH rather than a relative search, because .PATH and the argument match at the beginning. Additionally, make appears to consider a path that starts with ${.CURDIR} as relative, even though it expands to an absolute path.
The reason that most people aren't seeing this problem is that the absolute paths of /usr/src/sys and /sys are also searched, so as long as the kernel source can be found in at least one of those places, no problems surface. This problem was inadvertently introduced on 1 December 2000, with the addition of the sysvipc modules.
|
#
62748 |
|
07-Jul-2000 |
imp |
Add ${.CURDIR}/../../../.. to the list of places we look for the kernel. The new moudles/sound/drivers/foo pushes us down one more level.
|
#
60965 |
|
26-May-2000 |
peter |
Sigh. Use the correct path to bsd.conf.mk. It's times like this that I regret giving up coffee.
|
#
60963 |
|
26-May-2000 |
peter |
Revive a skeleton for bsd.kmod.mk (which will be in the make search path) that merely locates and includes sys/conf/kmod.mk.
|