mk.conf is the LAST thing included, is it not?!?

If not, there needs to be a way for someone building a system to
specify flags to append to the blasted compile!  I was given this
means of doing so the last time I posted with problems using
DEFCOPTS directly.

When I said "I'm using DEFCOPTS += ..." I was told, "Don't do that,
use COPTS += ..."

Now I'm using "COPTS += ..." and I'm being told, "Don't do that." with
no suggestion as to what to use this time.

This is ridiculous!  Make up your minds!

On Mon, 10 Jun 2002, Valeriy E. Ushakov wrote:

# Date: Mon, 10 Jun 2002 14:30:30 +0400
# From: Valeriy E. Ushakov <uwe@ptc.spbu.ru>
# To: port-sparc@netbsd.org
# Subject: Re: miniroot.fs too small
#
# On Sat, Jun 08, 2002 at 21:32:58 -0700, Greywolf wrote:
#
# > COPTS += -pipe, NOT COPTS=-pipe!
# >
# > Sorry, should have been more clear.
#
# What the difference does it make if it still *sets* the value of COPTS
# *before*
#
# > # COPTS?=         ${DEFCOPTS}
#
#
# this assignment is (not) executed.
#
# SY, Uwe
# --
# uwe@ptc.spbu.ru                         |       Zu Grunde kommen
# http://www.ptc.spbu.ru/~uwe/            |       Ist zu Grunde gehen
#


				--*greywolf;
--
NetBSD: Professional power!