use -Wno-error=format-truncation for code that seems particularly annoying

or unlikely to actually fail.  some of the syslogd ones are not too hard
to fix, but most remain.
This commit is contained in:
mrg 2019-02-04 10:22:15 +00:00
parent 85303579aa
commit 5e5bf48e2a
2 changed files with 12 additions and 2 deletions

View File

@ -1,4 +1,4 @@
# $NetBSD: Makefile.inc,v 1.16 2018/12/17 01:16:49 uwe Exp $
# $NetBSD: Makefile.inc,v 1.17 2019/02/04 10:22:15 mrg Exp $
#
# Makefile for sysinst
@ -118,6 +118,11 @@ COPTS.bsddisklabel.c += -Wno-format-nonliteral
COPTS.md.c += -Wno-format-nonliteral
COPTS.partman.c += -Wno-format-nonliteral -Wno-stack-protector
# Lots of warnings
.if defined(HAVE_GCC) && ${HAVE_GCC} == 7 && ${ACTIVE_CC} == "gcc"
COPTS.partman.c+= -Wno-error=format-truncation
.endif
# Host to ftp from. Default:
# "ftp.NetBSD.org"
#

View File

@ -1,4 +1,4 @@
# $NetBSD: Makefile,v 1.27 2018/02/09 02:23:32 christos Exp $
# $NetBSD: Makefile,v 1.28 2019/02/04 10:22:15 mrg Exp $
# from: @(#)Makefile 8.1 (Berkeley) 6/6/93
.include <bsd.own.mk>
@ -30,4 +30,9 @@ DPADD+= ${LIBWRAP}
LDADD+= -lssl -lcrypto
# Overflow that appears impossible
.if defined(HAVE_GCC) && ${HAVE_GCC} == 7 && ${ACTIVE_CC} == "gcc"
COPTS.syslogd.c+= -Wno-error=format-truncation
.endif
.include <bsd.prog.mk>