| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
# DO NOT DELETE THIS LINE -- make depend uses it
|
|
|
|
|
|
| |
commented out in the entire life of the 2.x+ branch and given the amount
of gcc-specific code we have and the warning checks that gcc does I'm not
sure that it is going to get us much for some time.
|
|
|
|
|
|
| |
debugging support as well. Debugging module support is handled
identically to kernel debugging support, right down to poor
choice of make variable names.
|
| |
|
| |
|
|
|
|
|
|
|
| |
sys/compile/${MACHINE}/FOO.
Reviewed by: arch, obrien, peter and
the USENIX terminal room secret kernel cabal
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Replace the a.out emulation of 'struct linker_set' with something
a little more flexible. <sys/linker_set.h> now provides macros for
accessing elements and completely hides the implementation.
The linker_set.h macros have been on the back burner in various
forms since 1998 and has ideas and code from Mike Smith (SET_FOREACH()),
John Polstra (ELF clue) and myself (cleaned up API and the conversion
of the rest of the kernel to use it).
The macros declare a strongly typed set. They return elements with the
type that you declare the set with, rather than a generic void *.
For ELF, we use the magic ld symbols (__start_<setname> and
__stop_<setname>). Thanks to Richard Henderson <rth@redhat.com> for the
trick about how to force ld to provide them for kld's.
For a.out, we use the old linker_set struct.
NOTE: the item lists are no longer null terminated. This is why
the code impact is high in certain areas.
The runtime linker has a new method to find the linker set
boundaries depending on which backend format is in use.
linker sets are still module/kld unfriendly and should never be used
for anything that may be modular one day.
Reviewed by: eivind
|
|
|
|
|
| |
cc arguments. Otherwise ipfilter's bogus #include lines will compile
reference /usr/include/netinet/ip_frag.h etc.
|
| |
|
| |
|
|
|
|
| |
kernel's out in wild that still have these flags set.
|
|
|
|
|
|
|
| |
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@
|
|
|
|
| |
directories work.
|
|
|
|
|
|
|
|
|
| |
instead of all of them. You can put this in /etc/make.conf or in
makeoptions.
Reviewed by: arch@
# docs to follow.
|
|
|
|
|
|
|
|
| |
that I removed in my last commit dealing with `make depend' bogons.
This commit has some races, but hopefully they are too short to matter.
Unfortuneatly, neither .newdep nor .olddep is removed by `make clean'.
Submitted by: bde
|
|
|
|
|
|
| |
builds. This may be disabled using the NO_CPU_COPTFLAGS variable.
Reviewed by: arch
|
|
|
|
| |
generated stuff, leaving only 'version' in the build dir.
|
|
|
|
|
|
|
|
|
|
| |
by the compiler. ie: char foo[0] comes out as 4 bytes on a.out, and
we depended on it coming out as 0 for the script version. :-(
Make double sure that genassym.o is built and nm'ed in elf mode.
(ia64 skipped since it is stuck on the linux toolchain and doesn't
understand the -elf switches)
|
| |
|
|
|
|
| |
when rebuilding it is just Wrong.
|
| |
|
|
|
|
|
|
|
|
|
| |
o Use objdump instead of gensetdefs(1) to build the linker sets.
o Allow overriding of nm and objdump in resp. genassym.sh and
gensetdefs.pl for non-native toolchains.
Reviewed by: arch
Perl improvements: Jos Backus <josb@cncdsl.com>, benno
|
|
|
|
|
|
| |
{kernel,modules}-reinstall.debug rather than {kernel,modules}-reinstall.
Otherwise, the '.debug' portion of the target is lost, and you end up
reinstalling the non debug version instead of the debug version.
|
|
|
|
| |
the NFOO count option.
|
|
|
|
|
| |
I cannot find a way to do this with the more esoteric source dir schemes
I thought of.
|
| |
|
| |
|
|
|
|
| |
header include path to include sys/dev to avoid massive #include updates.
|
|
|
|
| |
things like MFILES= or CONFFILES= without having to modify config code.
|
|
|
|
|
| |
Based on patch submitted by: Makoto MATSUSHITA <matusita@jp.freebsd.org>
Reviewed by: marcel, bde
|
| |
|
| |
|
|
|
|
| |
Do so for LINT.
|
|
|
|
|
|
|
| |
the kernel" patch.
This commit is only the "Do not prepend `DESTDIR' to `KMODDIR' as
sys/conf/kmod.mk already does that for us" change.
|
|
|
|
| |
that for us.
|
| |
|
|
|
|
| |
installation. This is need for the release build.
|
|
|
|
| |
Acceptability explained by: rgrimes
|
| |
|
| |
|
|
|
|
| |
live in ``/boot/kernel/''.
|
|
|
|
|
| |
then include the hints with a marker indicating that it is a fallback.
The kernel side of this is to come shortly.
|
|
|
|
|
| |
Do not install a kernel unless a device.hints exists. Yes, you can
create an empty hints file if you refuse to use them.
|
|
|
|
| |
* Don't ignore error returns.
|
|
|
|
| |
exists.
|
|
|
|
|
|
| |
doesn't exist. This could bite you by allowing you merrily install your
modules one on top of the other as the regular file ${DESTDIR}/modules
and think it completed properly...
|
|
|
|
|
|
|
| |
the list of .o files comes from - if we change the list of files that
are built, we need to rescan the files)
Obtained from: bde (indirectly)
|
|
|
|
| |
kernel build dir doesn't really say what your intentions are.
|
|
|
|
|
|
|
| |
world as was our old way, rather than when building a kernel.
Some people do not like the new way, and the release building still assumes
modules are built with the world.
|
| |
|