Changes in Makefile

Changes in Makefile http://nxr.netbsd.org/rss/src/usr.sbin/rpc.bootparamd/Makefile en Copyright 2005 Java bsd.own.mk: rename GCC_NO_* to CC_WNO_* 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. /src/usr.sbin/rpc.bootparamd/Makefile - 1.27 Sat Jun 03 09:09:22 UTC 2023 lukem introduce some common variables for use in GCC warning disables: 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." /src/usr.sbin/rpc.bootparamd/Makefile - 1.26 Sun Oct 13 07:28:20 UTC 2019 mrg branches: 1.25.76; Add new Makefile knob, USE_FORT, which extends USE_SSP by turning on the 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. /src/usr.sbin/rpc.bootparamd/Makefile - 1.25 Mon May 28 00:06:39 UTC 2007 tls Need to -I${RPC_XDIR} now, since we don't generate the .h file locally anymore. /src/usr.sbin/rpc.bootparamd/Makefile - 1.24 Mon Jan 06 02:26:53 UTC 2003 thorpej Use <bsd.rpc.mk> /src/usr.sbin/rpc.bootparamd/Makefile - 1.23 Sun Jan 05 19:24:07 UTC 2003 sommerfeld Add a simple test to see if the whoami functionality works. /src/usr.sbin/rpc.bootparamd/Makefile - 1.22 Wed Sep 11 18:19:42 UTC 2002 christos Split the notion of building Hesiod, Kerberos, S/key, and YP infrastructure and using that infrastructure in programs. * MKHESIOD, MKKERBEROS, MKSKEY, and MKYP control building of the infratsructure (libraries, support programs, etc.) * USE_HESIOD, USE_KERBEROS, USE_SKEY, and USE_YP control building of support for using the corresponding API in various libraries/programs that can use it. As discussed on tech-toolchain. /src/usr.sbin/rpc.bootparamd/Makefile - 1.21 Fri Mar 22 18:10:25 UTC 2002 thorpej Move CLEANFILES up so it is actually used. Noted by Bernd Ernesti. /src/usr.sbin/rpc.bootparamd/Makefile - 1.20 Sat Feb 02 17:11:38 UTC 2002 tv Make sure DESTDIR is set before using it in a dependency. /src/usr.sbin/rpc.bootparamd/Makefile - 1.19 Thu Jan 31 15:16:21 UTC 2002 tv ${RPCGEN}, not hard-coded rpcgen /src/usr.sbin/rpc.bootparamd/Makefile - 1.18 Tue Jul 25 06:29:46 UTC 2000 cgd Make the rpcsvc dependencies work a bit better. /src/usr.sbin/rpc.bootparamd/Makefile - 1.17 Mon Jun 12 01:57:25 UTC 2000 mycroft branches: 1.16.6; Use pidfile(3). /src/usr.sbin/rpc.bootparamd/Makefile - 1.16 Sun Jun 06 02:47:47 UTC 1999 thorpej use CPPFLAGS instead of CFLAGS /src/usr.sbin/rpc.bootparamd/Makefile - 1.15 Sat Oct 25 06:58:36 UTC 1997 lukem branches: 1.14.2; WARNSify; generate ansi c code with rpcgen, cleanup manpage /src/usr.sbin/rpc.bootparamd/Makefile - 1.14 Fri Oct 17 15:59:05 UTC 1997 lukem Back out BUILDDIR and NOINSTALL changes. /src/usr.sbin/rpc.bootparamd/Makefile - 1.13 Sat May 31 21:22:15 UTC 1997 cjs These updates to the build allow building against include files and libs in the object tree, if you use a separate object tree, while maintaining backward compatability with other build methods. See the notes in src/share/mk/bsd.README for full details. Note that the `make includes' target now only installs the include files in the build directory (if you use one--otherwise they go in DESTDIR just like before); `make install' will install include files in DESTDIR. /src/usr.sbin/rpc.bootparamd/Makefile - 1.12 Mon May 26 03:59:47 UTC 1997 cjs RCS id police. /src/usr.sbin/rpc.bootparamd/Makefile - 1.11 Fri Aug 30 20:10:25 UTC 1996 thorpej Conform to rpcgen generated names and prototypes. The server-side worker routines now have "_svc" appended to avoid conflict with client-side prototypes. /src/usr.sbin/rpc.bootparamd/Makefile - 1.10 Sat Jun 24 15:03:49 UTC 1995 pk fix typo /src/usr.sbin/rpc.bootparamd/Makefile - 1.9 Wed Apr 12 05:19:51 UTC 1995 jtc Install manpage as both bootparamd(8) and rpc.bootparamd(8). Changed manpage so both bootparamd and rpc.bootparamd are mentioned in NAME section. /src/usr.sbin/rpc.bootparamd/Makefile - 1.8 Wed Apr 12 00:53:09 UTC 1995 jtc