On Tue, 8 Nov 2005 10:19:33 -0600
James Chacon <jmc@netbsd.org> wrote:

> On Tue, Nov 08, 2005 at 09:13:26AM -0500, Perry E. Metzger wrote:
> > 
> > Marcin Jessa <lists@yazzy.org> writes:
> > > It also suprises me a simple thing like CPU flag could break the
> > > build.
> > 
> > It will break the build on other OSes as well.
> > 
> > gcc is buggy. (Other compilers are also buggy to greater or lesser
> > extents). The more files you are compiling, the larger the odds are
> > you will hit a bug, and NetBSD has a *lot* of files.
> > 
> > There is nothing wrong with trying other flag combinations, but you
> > should never assume that problems are caused by the OS if you are
> > using non-standard build flags or a non-standard compiler (or both).
> 
> It's also most likely hard coding the optimization level is what
> broke more than anything else. Due to gcc bugs there are places in
> the source tree which downgrade the -O level at times. 

Could you please include it somewhere at
http://www.netbsd.org/Documentation/current/#what-to-do 
so noone else struggles with this silly issue like me?
And add the CPUFLAGS part to man of mk.conf ?

Thanks for clearing this up for me. You guys made my day.

Cheers,
Marcin.