Date: Wed, 20 Dec 2006 19:57:20 -0800 From: Garrett Cooper <youshi10@u.washington.edu> To: freebsd-hackers@freebsd.org Subject: Properly controlling CFLAGS/CXXFLAGS Message-ID: <458A0620.5020905@u.washington.edu>
next in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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
TIA!
- -Garrett
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFigYgEnKyINQw/HARAgG4AKCWjs2FYuG6isov7DCE1plZTDkslgCcDufT
Y64QGayLi0FDKBaT2aS0ZEM=
=HOi0
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?458A0620.5020905>