| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Sponsored by: EMC / Isilon Storage Division
|
| |
|
|
|
|
|
|
|
|
|
| |
through via CFLAGS, as noted by Jenkins when building sparc64 by re-adding
bsd.sys.mk to bsd.kmod.mk:
https://jenkins.freebsd.org/job/FreeBSD_HEAD_sparc64/225/changes
Tested with:
% cd /sys/modules/bce; make obj; make depend; make all
|
|
|
|
|
|
|
|
|
|
| |
raft of new warnings that appear to be on by default in clang 3.5.0.
Fix RPI-B build issues with new clang not liking the ability to pass
arbitrary flags to as, since some flags are more arbitrary (and thus
verboten) than others.
These warnings should be actually fixed in the code, but this is a
band-aide to get things (almost) building again.
|
|
|
|
|
| |
Submitted by: bde@
MFC after: 2 weeks
|
|
|
|
| |
variable to set to override.
|
|
|
|
| |
Increase heuristic used to find them by one.
|
| |
|
|
|
|
|
|
|
| |
- Check in both places if ${_dir}/conf/kmod.mk exists.
- Style fixes (lines too long).
Submitted by: bde
|
|
|
|
|
|
|
| |
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/.
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
.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.
|
|
|
|
|
| |
kernel. The new moudles/sound/drivers/foo pushes us down one more
level.
|
|
|
|
| |
regret giving up coffee.
|
|
|
|
| |
that merely locates and includes sys/conf/kmod.mk.
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
of relying on the default list provided here.
|
|
|
|
|
|
| |
it into a ``shared'' .ko file. This intermediate file can be directly
linked into a static kernel. This isn't all that useful yet but will
become much more interesting shortly.
|
|
|
|
|
| |
makefiles. Bad examples in fxp/Makefile keep getting copied to new
makefiles.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
is an application space macro and the applications are supposed to be free
to use it as they please (but cannot). This is consistant with the other
BSD's who made this change quite some time ago. More commits to come.
|
|
|
|
|
|
| |
the repo copy as the kernel src/sys/modules stuff uses
/usr/share/mk/bsd.kmod.mk which often gets out of sync with the kernel
source.
|
|
|
|
|
|
|
|
|
| |
we use. The .c half is statically compiled into the kernel. It's kinda
silly to generate a .h file on the fly that has inlines to call the
.c stuff when the .c code is fixed.
Also, zap the special treatment for VFS_KLD modules. This treatment
applies to lots of things, not just VFS's.
|
|
|
|
|
|
| |
dev/pccard/power_if.m.
XXX There has got to be a better way to deal with this.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Pointed out by: bde
|
|
|
|
|
| |
the LHS of the rule for vnode_if.h. This solves a "dunno how to make"
error.
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
/usr/sbin/sysctl -> ${DESTDIR}/sbin/sysctl in some versions of 2.2,
and this link was broken if DESTDIR was set.
Added a SYMLINKS macro. This works the same as LINKS, except it
creates symlinks and the linked-to pathname may be relative. This
is more flexible than LN_FLAGS, since it supports installing
symlinks independently of hard links.
Use `ln -f[s] ...' instead of `rm -f ...; ln [-s] ...' for LINKS and
SYMLINKS. This is equivalent if the target is neither a directory nor
a symlink to a directory.
PR: 8279
|
| |
|
|
|
|
|
| |
${KMOD}.o or ${KMOD}.ko. Otherwise we can delete the source shell script
for linux, joy and ibcs2.
|
|
|
|
| |
Pre-Approved by: jkh
|
|
|
|
|
| |
Support name based dependencies at build time. This is a hack.
These only affect KLD modules.
|
|
|
|
|
| |
Forgot to mention that the previous commit was
Submitted by: Doug Rabson <dfr@freebsd.org>
|
|
|
|
| |
to be removed KMODDEPS define.
|
|
|
|
|
|
| |
src/lkm/Makefile.inc. This fixes broken builds of the syscons LKMs
when OBJFORMAT=elf. Removed src/lkm/Makefile.inc since it became
empty and is worse than useless.
|
|
|
|
|
|
| |
when certain .mk files include other .mk files. This will remove the
need for multiple include protection in some other makefiles around the
tree (and helps some elf conditionals).
|
|
|
|
|
|
|
|
|
|
|
| |
`make world' to avoid problems with picking up (new) target or (stale)
host shared libraries.
Don't honor -static in LDFLAGS for linking LKMs. LDFLAGS is not
actually for ld, but we use it anyway, and must prevent -static being
misinterpreted as -s.
Don't hide any of the link steps.
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
Silently approved by: -hackers, -current
|
| |
|