summaryrefslogtreecommitdiff
path: root/usr.bin/rdist/Makefile
AgeCommit message (Collapse)Author
2023-06-03bsd.own.mk: rename GCC_NO_* to CC_WNO_*lukem
Rename compiler-warning-disable variables from GCC_NO_warning to CC_WNO_warning where warning is the full warning name as used by the compiler. GCC_NO_IMPLICIT_FALLTHRU is CC_WNO_IMPLICIT_FALLTHROUGH Using the convention CC_compilerflag, where compilerflag is based on the full compiler flag name.
2019-10-13introduce some common variables for use in GCC warning disables:mrg
GCC_NO_FORMAT_TRUNCATION -Wno-format-truncation (GCC 7/8) GCC_NO_STRINGOP_TRUNCATION -Wno-stringop-truncation (GCC 8) GCC_NO_STRINGOP_OVERFLOW -Wno-stringop-overflow (GCC 8) GCC_NO_CAST_FUNCTION_TYPE -Wno-cast-function-type (GCC 8) use these to turn off warnings for most GCC-8 complaints. many of these are false positives, most of the real bugs are already commited, or are yet to come. we plan to introduce versions of (some?) of these that use the "-Wno-error=" form, which still displays the warnings but does not make it an error, and all of the above will be re-considered as either being "fix me" (warning still displayed) or "warning is wrong."
2019-09-29convert HAVE_GCC == 7 to HAVE_GCC >= 7.mrg
2019-02-04- use -Wno-error=format-truncationmrg
2007-05-28Add new Makefile knob, USE_FORT, which extends USE_SSP by turning on thetls
FORTIFY_SOURCE feature of libssp, thus checking the size of arguments to various string and memory copy and set functions (as well as a few system calls and other miscellany) where known at function entry. RedHat has evidently built all "core system packages" with this option for some time. This option should be used at the top of Makefiles (or Makefile.inc where this is used for subdirectories) but after any setting of LIB. This is only useful for userland code, and cannot be used in libc or in any code which includes the libc internals, because it overrides certain libc functions with macros. Some effort has been made to make USE_FORT=yes work correctly for a full-system build by having the bsd.sys.mk logic disable the feature where it should not be used (libc, libssp iteself, the kernel) but no attempt has been made to build the entire system with USE_FORT and doing so will doubtless expose numerous bugs and misfeatures. Adjust the system build so that all programs and libraries that are setuid, directly handle network data (including serial comm data), perform authentication, or appear likely to have (or have a history of having) data-driven bugs (e.g. file(1)) are built with USE_FORT=yes by default, with the exception of libc, which cannot use USE_FORT and thus uses only USE_SSP by default. Tested on i386 with no ill results; USE_FORT=no per-directory or in a system build will disable if desired.
2000-07-03Make gcc 2.96 (and maybe earlier) happier. Include <stdlib.h>,<string.>,matt
etc. as appropriate to get exit,srncmp,abs,abort,etc. Add -I${.CURDIR} to a few Makefiles
1998-04-09.y.c <sys.mk> rule fixes. Don't create a y.tab.h file unless asked for,tv
and use smarter creation of the header file.
1997-10-18merge lite-2.mrg
1997-10-08Don't need -I${.CURDIR}christos
1997-05-26rdist is no longer setuid root.mrg
1996-07-12RCS id police.thorpej
1996-07-12From Christos: kill the last bits of sprintf(), and use regcomp/regexecthorpej
rather than re_comp/re_exec. (I committed my sprintf sweep-up before I realized that Christos had already done it...)
1994-03-07update to newest rdist from berkeley (via uunet). No security fixes, butcgd
general cleanup.
1993-07-31Add RCS indentifiers.mycroft
1993-07-194.4BSD-Lite2mrg
1993-03-21initial import of 386bsd-0.1 sourcescgd