7+ days of dogfood

b.f. bf1783 at googlemail.com
Wed Feb 13 00:18:32 UTC 2013

># cat /etc/make.conf|grep FFLAGS
>FFLAGS = -O2 -pipe -march=native -mtune=native

Please do _not_ assign flags unconditionally in make.conf.  In fact,
try to remove or restrict the scope of everything in this file. (It is
unfortunate that some of the examples for the base system in the
sample make.conf have been inappropriate for use with other software,
and also that the recent port options changes have encouraged people
to once again dump a lot of stuff into this file.) This is a very
special file: it is included nearly every time make(1) is invoked.  In
addition to the usual concerns about speed, efficiency, and build
pollution, if a port or some other software invokes make(1) more than
once -- and many do -- make.conf is often re-read, and assignments can
clobber necessary prior additions or changes to a variable that were
made elsewhere, sometimes breaking software, and not always in an
obvious way.

>I get building lapack:
>gfortran47 -O2 -pipe -march=native -mtune=native -funroll-loops -ftree-vectorize -pg -c slatms.f -o slatms.o
>gfortran47: error: unrecognized command line option '-march=native'
>gfortran47: error: unrecognized argument in option '-mtune=native'
>gfortran47: note: valid arguments to '-mtune=' are: itanium2 mckinley

For example, here it looks like you have clobbered some of the rpath
flag additions made in ports/Mk/bsd.gcc.mk.  This may not break
lapack, but similar changes will almost certainly break some other


More information about the freebsd-current mailing list