On Wed, 9 Nov 2005 18:06:22 +0000 (UTC)
christos@astron.com (Christos Zoulas) wrote:

> In article <20051108135210.3b4a2b1c.lists@yazzy.org>,
> Marcin Jessa  <lists@yazzy.org> wrote:
> >On Mon, 07 Nov 2005 20:33:17 -0500
> >"Perry E. Metzger" <perry@piermont.com> wrote:
> >
> >> 
> >> Marcin Jessa <lists@yazzy.org> writes:
> >> >> [1]
> >> >> #CPUFLAGS=-march=pentium3 -mmmx -msse -mfpmath=sse
> >> >> CPUFLAGS=-march=pentium3 
> >> >> #CFLAGS=-O2 -pipe
> >> >
> >> > All I have in my mk.conf is:
> >> > CFLAGS= -O2 -pipe -march=pentium4
> >> >
> >> > That should not cause any problems...
> >> 
> >> Don't assume. Try building with an emtpy mk.conf.
> >
> >Thanks, having a blank mk.conf fixed the problem however this must me
> >documented at http://www.netbsd.org/Documentation/current/
> >I was pretty close to just give up on NetBSD and abandon my
> >NetBSD-based projects after all those months of having problems with
> >compiling of the base system. And gaving to compile all the binaries
> >I needed by hand. All this becouse of this undocumented issue. 
> >And I am a very patient guy.
> >It also suprises me a simple thing like CPU flag could break the
> >build. Thanks again.
> 
> The CFLAGS is the problem. You should use CFLAGS+= otherwise you can
> overwrite other settings.
 

Thanks for the hint Christos.
Everything works fine now that I abandoned CFLAGS and sticked to only
CPUFLAGS in my mk.conf.


Marcin