freebsd-skq/libexec/rpc.rstatd/Makefile

# $FreeBSD$

PROG =	rpc.rstatd
SRCS =	rstatd.c rstat_proc.c
MAN =	rpc.rstatd.8

LIBADD=	rpcsvc devstat

WARNS?=	1

.include <bsd.prog.mk>
$Id$ -> $FreeBSD$ 1999-08-28 00:22:10 +00:00			`# $FreeBSD$`
rstatd -- from FreeBSD-1.1.5.1, with changes for 4.4-Lite kvm interface. Original rstatd by John Brezak Submitted by: Geoff. 1994-08-28 14:49:04 +00:00
			`PROG = rpc.rstatd`
			`SRCS = rstatd.c rstat_proc.c`
- Backout botched attempt to intoduce MANSECT feature. - MAN[1-9] -> MAN. 2001-03-26 14:22:12 +00:00			`MAN = rpc.rstatd.8`
rstatd -- from FreeBSD-1.1.5.1, with changes for 4.4-Lite kvm interface. Original rstatd by John Brezak Submitted by: Geoff. 1994-08-28 14:49:04 +00:00
Convert to LIBADD Reduce overlinking 2014-11-25 21:18:18 +00:00			`LIBADD= rpcsvc devstat`
rstatd -- from FreeBSD-1.1.5.1, with changes for 4.4-Lite kvm interface. Original rstatd by John Brezak Submitted by: Geoff. 1994-08-28 14:49:04 +00:00
Make WARNS=6 the default for libexec/. Just like bin/ and sbin/, I think setting WARNS to the highest value possible will make it more attractive for people to fix warnings. - The WARNS variable is set in the Makefile in the directory of the application itself, making it more likely that it will be removed out of curiosity to see what happens. - New applications will most likely build with WARNS=6 out of the box, because the author would more likely fix the warnings during development than lower WARNS. Unfortunately almost all apps in libexec require a lowered value of WARNS. 2010-01-02 09:50:19 +00:00			`WARNS?= 1`

rstatd -- from FreeBSD-1.1.5.1, with changes for 4.4-Lite kvm interface. Original rstatd by John Brezak Submitted by: Geoff. 1994-08-28 14:49:04 +00:00			`.include <bsd.prog.mk>`