bsd.own.mk: rename to CC_WNO_ADDRESS_OF_PACKED_MEMBER

Provide a single variable
CC_WNO_ADDRESS_OF_PACKED_MEMBER
with options for both clang and gcc, to replace
CLANG_NO_ADDR_OF_PACKED_MEMBER
CC_NO_ADDR_OF_PACKED_MEMBER
GCC_NO_ADDR_OF_PACKED_MEMBER

Using the convention CC_compilerflag, where compilerflag
is based on the full compiler flag name.

address-of-packed-member warning is no longer a problem here.

branches: 1.9.2;
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.

Disable a couple of warnings until further investigation.

branches: 1.7.44;
Rename MKPRIVATELIB to LIBISPRIVATE, to make it clearer that this is
a variable that is used by in-tree Makefiles to control behaviour.
(MKsomevar variables are generally intended to be controlled by the end-user)

branches: 1.6.24;
Use MKPRIVATELIB=yes instead of providing an empty libinstall:: target and
setting NOLINT, NOPIC, NOPROFILE (etc)

minor makefile delint

MKfoo=no -> NOfoo

set MKLINT=no. noted by NAKAJIMA Yoshihiro <nakayosh@kcn.ne.jp>

convert from NOxxx= to MKxxx=no.
include <bsd.own.mk> if testing a MKxxx variable.

move (using repository copy) bootp{d,ef,gw,test} into a common hierarchy
with a libcommon - to stop unnecessary recompilation of the source.
add Makefile* to suit.

address-of-packed-member warning is no longer a problem here.

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.

Disable a couple of warnings until further investigation.

branches: 1.7.44;
Rename MKPRIVATELIB to LIBISPRIVATE, to make it clearer that this is
a variable that is used by in-tree Makefiles to control behaviour.
(MKsomevar variables are generally intended to be controlled by the end-user)

branches: 1.6.24;
Use MKPRIVATELIB=yes instead of providing an empty libinstall:: target and
setting NOLINT, NOPIC, NOPROFILE (etc)

minor makefile delint

MKfoo=no -> NOfoo

set MKLINT=no. noted by NAKAJIMA Yoshihiro <nakayosh@kcn.ne.jp>

convert from NOxxx= to MKxxx=no.
include <bsd.own.mk> if testing a MKxxx variable.

move (using repository copy) bootp{d,ef,gw,test} into a common hierarchy
with a libcommon - to stop unnecessary recompilation of the source.
add Makefile* to suit.

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.

Disable a couple of warnings until further investigation.

branches: 1.7.44;
Rename MKPRIVATELIB to LIBISPRIVATE, to make it clearer that this is
a variable that is used by in-tree Makefiles to control behaviour.
(MKsomevar variables are generally intended to be controlled by the end-user)

branches: 1.6.24;
Use MKPRIVATELIB=yes instead of providing an empty libinstall:: target and
setting NOLINT, NOPIC, NOPROFILE (etc)

minor makefile delint

MKfoo=no -> NOfoo

set MKLINT=no. noted by NAKAJIMA Yoshihiro <nakayosh@kcn.ne.jp>

convert from NOxxx= to MKxxx=no.
include <bsd.own.mk> if testing a MKxxx variable.

move (using repository copy) bootp{d,ef,gw,test} into a common hierarchy
with a libcommon - to stop unnecessary recompilation of the source.
add Makefile* to suit.

Disable a couple of warnings until further investigation.

Rename MKPRIVATELIB to LIBISPRIVATE, to make it clearer that this is
a variable that is used by in-tree Makefiles to control behaviour.
(MKsomevar variables are generally intended to be controlled by the end-user)

branches: 1.6.24;
Use MKPRIVATELIB=yes instead of providing an empty libinstall:: target and
setting NOLINT, NOPIC, NOPROFILE (etc)

minor makefile delint

MKfoo=no -> NOfoo

set MKLINT=no. noted by NAKAJIMA Yoshihiro <nakayosh@kcn.ne.jp>

convert from NOxxx= to MKxxx=no.
include <bsd.own.mk> if testing a MKxxx variable.

move (using repository copy) bootp{d,ef,gw,test} into a common hierarchy
with a libcommon - to stop unnecessary recompilation of the source.
add Makefile* to suit.