NetBSD/sbin/dump/Makefile

#	$NetBSD: Makefile,v 1.41 2020/09/06 07:20:27 mrg Exp $
#	@(#)Makefile	8.1 (Berkeley) 6/5/93

#	dump.h			header file
#	itime.c			reads /etc/dumpdates
#	main.c			driver
#	optr.c			operator interface
#	dumprmt.c		handles remote tape via rmt(8)
#	rcache.c		read cache
#	tape.c			handles the mag tape and opening/closing
#	traverse.c		traverses the file system
#	unctime.c		undo ctime
#	ffs_inode.c		FFS-specific filestore routines
#	ffs_bswap.c		FFS byte-swapping
#
#	DEBUG			use local directory to find ddate and dumpdates
#	TDEBUG			trace out the process forking
#	FDEBUG			trace dumpdates parsing
#	WRITEDEBUG		trace slave writes
#	STATS			read cache statistics
#	DIAGNOSTICS		read cache diagnostic checks

WARNS?=	3	# XXX: sign-compare issues

.include <bsd.own.mk>

PROG=	dump
LINKS=	${BINDIR}/dump ${BINDIR}/rdump
CPPFLAGS+=-DRDUMP -I${.CURDIR}
# CPPFLAGS+= -DDEBUG -DTDEBUG -DFDEBUG -DWRITEDEBUG -DSTATS -DDIAGNOSTICS
SRCS=	itime.c main.c optr.c dumprmt.c rcache.c snapshot.c tape.c \
	traverse.c unctime.c ffs_inode.c ffs_bswap.c
MAN=	dump.8
MLINKS+=dump.8 rdump.8
DPADD+= ${LIBUTIL}
LDADD+= -lutil

.PATH:  ${NETBSDSRCDIR}/sys/ufs/ffs

COPTS.ffs_inode.c+=	-Wno-pointer-sign
COPTS.traverse.c+=	${GCC_NO_FORMAT_TRUNCATION}
CWARNFLAGS.gcc+=	${GCC_NO_ADDR_OF_PACKED_MEMBER}
CWARNFLAGS.gcc+=	${GCC_NO_FORMAT_TRUNCATION}

.include <bsd.prog.mk>
add support for new GCC 9 warnings that may be too much to fix right now. new address-of-packed-member and format-overflow warnings have new GCC_NO_ADDR_OF_PACKED_MEMBER amd GCC_NO_FORMAT_OVERFLOW variables to remove these warnings. apply to a bunch of the tree. mostly, these are real bugs that should be fixed, but in many cases, only by removing the 'packed' attribute from some structure that doesn't really need it. (i looked at many different ones, and while perhaps 60-80% were already properly aligned, it wasn't clear to me that the uses were always coming from sane data vs network alignment, so it doesn't seem safe to remove packed without careful research for each affect struct.) clang already warned (and was not erroring) for many of these cases, but gcc picked up dozens more. 2020-09-06 10:20:26 +03:00			`# $NetBSD: Makefile,v 1.41 2020/09/06 07:20:27 mrg Exp $`
convert to new RCS Id conventions; reduce my headache 1995-03-18 17:54:19 +03:00			`# @(#)Makefile 8.1 (Berkeley) 6/5/93`
new version from CSRG, via BSDI, with fixes 1993-12-22 13:19:31 +03:00
initial import of 386bsd-0.1 sources 1993-03-21 12:45:37 +03:00			`# dump.h header file`
new version from CSRG, via BSDI, with fixes 1993-12-22 13:19:31 +03:00			`# itime.c reads /etc/dumpdates`
			`# main.c driver`
			`# optr.c operator interface`
			`# dumprmt.c handles remote tape via rmt(8)`
document more of the debug options 2001-12-25 14:56:14 +03:00			`# rcache.c read cache`
new version from CSRG, via BSDI, with fixes 1993-12-22 13:19:31 +03:00			`# tape.c handles the mag tape and opening/closing`
			`# traverse.c traverses the file system`
initial import of 386bsd-0.1 sources 1993-03-21 12:45:37 +03:00			`# unctime.c undo ctime`
Working version of aborted dump{,_lfs} join. 1999-10-01 08:35:21 +04:00			`# ffs_inode.c FFS-specific filestore routines`
			`# ffs_bswap.c FFS byte-swapping`
initial import of 386bsd-0.1 sources 1993-03-21 12:45:37 +03:00			`#`
			`# DEBUG use local directory to find ddate and dumpdates`
			`# TDEBUG trace out the process forking`
document more of the debug options 2001-12-25 14:56:14 +03:00			`# FDEBUG trace dumpdates parsing`
			`# WRITEDEBUG trace slave writes`
			`# STATS read cache statistics`
			`# DIAGNOSTICS read cache diagnostic checks`
initial import of 386bsd-0.1 sources 1993-03-21 12:45:37 +03:00
Enable WARNS=4 by default except for: dump dump_lfs fsck_ffs fsck_lfs fsdb mount_smbfs newfs_ext2fs newfs_lfs resize_lfs setkey 2009-04-11 11:58:11 +04:00			`WARNS?= 3 # XXX: sign-compare issues`

Use ${NETBSDSRCDIR}/some/path instead of ${.CURDIR}/../../some/path 2002-08-19 14:16:51 +04:00			`.include <bsd.own.mk>`

initial import of 386bsd-0.1 sources 1993-03-21 12:45:37 +03:00			`PROG= dump`
new version from CSRG, via BSDI, with fixes 1993-12-22 13:19:31 +03:00			`LINKS= ${BINDIR}/dump ${BINDIR}/rdump`
Working version of aborted dump{,_lfs} join. 1999-10-01 08:35:21 +04:00			`CPPFLAGS+=-DRDUMP -I${.CURDIR}`
Implement a read cache, as announced on tech-userlevel. Default is 32k read buffer size, 512 buffer or 15% of the user memory. Can be changed with the -k and -s options. 1999-03-23 17:22:59 +03:00			`# CPPFLAGS+= -DDEBUG -DTDEBUG -DFDEBUG -DWRITEDEBUG -DSTATS -DDIAGNOSTICS`
Snapshot support for dump(8): - New option `-x backup' takes the dump from a snapshot backed up by `backup'. The snapshot will be deleted on exit. - New option `-X' as a synonym for `-x mountpoint' where `mountpoint' is the file system to be dumped. Reviewed and Approved by: Manuel Bouyer <bouyer@netbsd.org> 2005-04-19 11:26:38 +04:00			`SRCS= itime.c main.c optr.c dumprmt.c rcache.c snapshot.c tape.c \`
			`traverse.c unctime.c ffs_inode.c ffs_bswap.c`
specify man pages the new way. 1994-12-22 13:44:04 +03:00			`MAN= dump.8`
new version from CSRG, via BSDI, with fixes 1993-12-22 13:19:31 +03:00			`MLINKS+=dump.8 rdump.8`
use getfsspecname() 2012-04-07 08:52:20 +04:00			`DPADD+= ${LIBUTIL}`
			`LDADD+= -lutil`
initial import of 386bsd-0.1 sources 1993-03-21 12:45:37 +03:00
Use "wall -g operator" (instead of private code) to broadcast() messages to members of the operator group. Don't install "setgid tty", and remove now unnecessary gid/egid swapping. Remove utmp trawling code pulled in from usr.bin/who. The Code is now simpler, and more portable (without the utmp cruft) too. This is derived from similar work in OpenBSD. 2003-03-27 16:56:46 +03:00			`.PATH: ${NETBSDSRCDIR}/sys/ufs/ffs`
Add support for non-native byte order FFS. The dump is in filesystem byte order, restore already knows how to byteswap dumps. 1998-03-18 19:54:56 +03:00
sprinkle some -fno-strict-aliasing and -Wno-pointer-sign with GCC4. 2006-05-12 03:16:28 +04:00			`COPTS.ffs_inode.c+= -Wno-pointer-sign`
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			`COPTS.traverse.c+= ${GCC_NO_FORMAT_TRUNCATION}`
add support for new GCC 9 warnings that may be too much to fix right now. new address-of-packed-member and format-overflow warnings have new GCC_NO_ADDR_OF_PACKED_MEMBER amd GCC_NO_FORMAT_OVERFLOW variables to remove these warnings. apply to a bunch of the tree. mostly, these are real bugs that should be fixed, but in many cases, only by removing the 'packed' attribute from some structure that doesn't really need it. (i looked at many different ones, and while perhaps 60-80% were already properly aligned, it wasn't clear to me that the uses were always coming from sane data vs network alignment, so it doesn't seem safe to remove packed without careful research for each affect struct.) clang already warned (and was not erroring) for many of these cases, but gcc picked up dozens more. 2020-09-06 10:20:26 +03:00			`CWARNFLAGS.gcc+= ${GCC_NO_ADDR_OF_PACKED_MEMBER}`
			`CWARNFLAGS.gcc+= ${GCC_NO_FORMAT_TRUNCATION}`
sprinkle some -fno-strict-aliasing and -Wno-pointer-sign with GCC4. 2006-05-12 03:16:28 +04:00
initial import of 386bsd-0.1 sources 1993-03-21 12:45:37 +03:00			`.include <bsd.prog.mk>`