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

23 lines
448 B
Makefile
Raw Normal View History

remove most of the remaining HAVE_GCC tests that are always true in the modern world.
2011-06-20 11:43:56 +04:00
# $NetBSD: Makefile,v 1.8 2011/06/20 07:44:03 mrg Exp $
use NETBSDSRCDIR as appropriate
2002-09-18 07:54:26 +04:00
.include <bsd.own.mk>
to complement my recent kernel changes: add a small tool to build a disklabel (in-core one, of course) from a CD TOC, which is useful to access previous sessions on a multi-session CD
2002-05-29 23:39:06 +04: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 # reads potentially untrustworthy data
to complement my recent kernel changes: add a small tool to build a disklabel (in-core one, of course) from a CD TOC, which is useful to access previous sessions on a multi-session CD
2002-05-29 23:39:06 +04:00
PROG= mscdlabel
-before adding a "partition", check for an ISO9660 filesystem, and print out volume label and creation time -if the drive cannot be open()ed read-write, try read-only and print the information
2004-07-04 18:11:44 +04:00
SRCS= main.c dkcksum.c iso9660.c
clean up {LD,DP}ADD. no need to set WARNS=1 here
2002-11-30 09:00:42 +03:00
DPADD+= ${LIBUTIL}
LDADD+= -lutil
to complement my recent kernel changes: add a small tool to build a disklabel (in-core one, of course) from a CD TOC, which is useful to access previous sessions on a multi-session CD
2002-05-29 23:39:06 +04:00
MAN= mscdlabel.8
use NETBSDSRCDIR as appropriate
2002-09-18 07:54:26 +04:00
DISKLABEL_SRC= ${NETBSDSRCDIR}/sbin/disklabel
to complement my recent kernel changes: add a small tool to build a disklabel (in-core one, of course) from a CD TOC, which is useful to access previous sessions on a multi-session CD
2002-05-29 23:39:06 +04:00
.PATH: ${DISKLABEL_SRC}
CPPFLAGS+= -I${DISKLABEL_SRC}
remove most of the remaining HAVE_GCC tests that are always true in the modern world.
2011-06-20 11:43:56 +04:00
.if defined(HAVE_GCC) || defined(HAVE_PCC)
sprinkle some -fno-strict-aliasing and -Wno-pointer-sign with GCC4.
2006-05-12 03:16:28 +04:00
COPTS.iso9660.c+= -Wno-pointer-sign
.endif
to complement my recent kernel changes: add a small tool to build a disklabel (in-core one, of course) from a CD TOC, which is useful to access previous sessions on a multi-session CD
2002-05-29 23:39:06 +04:00
.include <bsd.prog.mk>