Searched hist:69775 (Results 1 - 2 of 2) sorted by relevance
/freebsd-10.2-release/share/mk/ | ||
H A D | bsd.kmod.mk | diff 69775 Fri Dec 08 20:36:32 MST 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. |
/freebsd-10.2-release/sys/conf/ | ||
H A D | kmod.mk | diff 69775 Fri Dec 08 20:36:32 MST 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. |
Completed in 129 milliseconds