Date: Thu, 21 Dec 2006 08:56:00 -0800 From: Freddie Cash <fcash@ocis.net> To: freebsd-hackers@freebsd.org Subject: Re: Properly controlling CFLAGS/CXXFLAGS Message-ID: <200612210856.00910.fcash@ocis.net> In-Reply-To: <458A0620.5020905@u.washington.edu> References: <458A0620.5020905@u.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 20 December 2006 07:57 pm, Garrett Cooper wrote:
> Hello,
> Coming from Gentoo we were taught how to 'rice' our machines.
> Based on my experience though with FreeBSD, this is an improper
> methodology for one to use.
> I was wondering (looking at the make.conf manpage), what's the
> best way to control one's CFLAGS/CXXFLAGS. I'd prefer if only a few
> ports would have optimized compiler flags, while the rest of the system
> used a safe set of compiler flags.
> So, I was wondering what the best course of action for setting
> variables in /etc/make.conf would be? Is this proper given what I'm
> trying to accomplish:
>
> /etc/make.conf snippet:
> CFLAGS= -O2 -pipe
> CXXFLAGS= ${CFLAGS}
> COPTFLAGS= ${CFLAGS} -msse -msse2 -mfpmath=sse,387
>
> NO_CPU_CFLAGS="YES"
> NO_CPU_COPTFLAGS="YES"
>
> CPUTYPE?=pentium4
My suggestion is to leave all mention of *CFLAGS out of /etc/make.conf to
use the system defaults (-O2 -pipe -fno-strict-aliasing), set CPUTYPE
accordingly, and install sysutils/portconf.
That gives you a separate /usr/local/etc/ports.conf file where you can set
global and per-port settings that are only used when compiling things
under /usr/ports (actually $PORTSDIR).
--
Freddie Cash
fcash@ocis.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200612210856.00910.fcash>