COPTFLAGS (not?) only for compiling the kernel?

[platanthera]

On Friday 14 May 2004 01:09, Kris Kennaway wrote:
> On Fri, May 14, 2004 at 01:12:41AM +0200, platanthera wrote:
> > On Friday 14 May 2004 00:48, Kris Kennaway wrote:
> > > On Thu, May 13, 2004 at 11:29:07PM +0200, platanthera wrote:
> > > > [/etc/make.conf]
> > > > ...
> > > > # To compile just the kernel with special optimizations, you
> > > > should use # this instead of CFLAGS (which is not applicable to
> > > > kernel builds anyway). # There is very little to gain by using
> > > > higher optimization levels, and doing # so can cause problems.
> > > > #
> > > > COPTFLAGS= [whatever]
> > > > ...
> > > >
> > > > just the kernel... sounds like COPTFLAGS setting should not
> > > > effect world or port builds, but apparently it does.
> > >
> > > It shouldn't, CFLAGS is used for that.
> > >
> > > Kris
> >
> > I'm just compiling koffice and it looks like COPTFLAGS= -O -pipe
> > overrides the koffice defaults (no CFLAGS defined in make.conf).
>
> The default CFLAGS value *is* "-O -pipe".
>
> Kris

OK, but it looks like -O overrides -O2 here, right?
And if that's true, how can I make the port build use the ports default 
instead of the system default?