Re: build failures after stdlib update

On Sun, 21 Mar 2010 14:03:04 +0100
Gary Jennejohn <gary.jennejohn_at_freenet.de> wrote:

> On Sun, 21 Mar 2010 13:43:52 +0100 (CET)
> Alexander Best <alexbestms_at_wwu.de> wrote:
> 
> > Pegasus Mc Cleaft schrieb am 2010-03-21:
> > > > > it would be nice if people with arch i386 and amd64 could try to
> > > > > reproduce this (i believe the other archs don't support
> > > > > CPUTYPE=native).
> > > > > again the easiest way to trigger this (you don't need to edit
> > > > > your
> > > > > /etc/make.conf for this) should be running:
> > 
> > > > > gcc -v -x c -E -mtune=native /dev/null -o /dev/null 2>&1
> > 
> > 
> > >         I didnt think  you could add CPUTYPE=native to the
> > >         /etc/make.conf
> > 
> > >         What I used to do when I was compiling native was to do
> > >         something like
> > > the following in the /etc/make.conf
> > 
> > no you can. /usr/share/mk/bsd.cpu.mk doesn't perform any 'native' checks so
> > when you set 'CPUTYPE=native' -mtune gets set to native.
> > 
> > so you can just do:
> > 
> > CPUTYPE=native
> > CFLAGS=-O2 -fno-strict-aliasing -pipe -s
> > 
> > btw: what's the -s switch doing?
> > 
> 
> It "silences" make.  See the man page.  It's useful because basically only
> errors are emitted.
> 

Oops.  That's wrong.  I got confused.  I'd like to know that myself, now
that I'm no longer confused :)

--
Gary Jennejohn