build failures after stdlib update

Gary Jennejohn gary.jennejohn at freenet.de
Sun Mar 21 13:03:08 UTC 2010


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.

--
Gary Jennejohn


More information about the freebsd-current mailing list