Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/usr.sbin/rwhod/Makefile

21 lines
426 B
Makefile
Raw Normal View History

Add RCS identifiers.
1993-07-31 00:50:20 +04:00
# from: @(#)Makefile 5.3 (Berkeley) 5/11/90
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.
2023-06-03 12:09:01 +03:00
# $NetBSD: Makefile,v 1.16 2023/06/03 09:09:23 lukem Exp $
use NETBSDSRCDIR as appropriate
2002-09-18 07:54:26 +04:00
.include <bsd.own.mk>
after 0.2.2 "stable" patches applied
1993-03-21 21:04:42 +03:00
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.
2007-05-28 16:06:17 +04:00
USE_FORT?= yes # network server
after 0.2.2 "stable" patches applied
1993-03-21 21:04:42 +03:00
PROG= rwhod
use utmpx.
2002-08-02 06:38:15 +04:00
SRCS= rwhod.c utmpentry.c
specify man pages the new way.
1994-12-22 14:32:57 +03:00
MAN= rwhod.8
after 0.2.2 "stable" patches applied
1993-03-21 21:04:42 +03:00
use NETBSDSRCDIR as appropriate
2002-09-18 07:54:26 +04:00
.PATH.c: ${NETBSDSRCDIR}/usr.bin/who
CPPFLAGS+=-I${NETBSDSRCDIR}/usr.bin/who -DSUPPORT_UTMPX -DSUPPORT_UTMP
use utmpx.
2002-08-02 06:38:15 +04:00
Use pidfile(3).
1999-06-06 07:27:35 +04:00
LDADD+= -lutil
DPADD+= ${LIBUTIL}
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.
2023-06-03 12:09:01 +03:00
COPTS.rwhod.c+= ${CC_WNO_STRINGOP_TRUNCATION}
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."
2019-10-13 10:28:04 +03:00
after 0.2.2 "stable" patches applied
1993-03-21 21:04:42 +03:00
.include <bsd.prog.mk>