Date: Thu, 12 Feb 2004 20:09:31 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Paul Seniura <pdseniura@techie.com> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: need help on CFLAGS in /etc/make.conf please Message-ID: <20040213040929.GA58196@xor.obsecurity.org> In-Reply-To: <20040213035608.3AA11A38EA@scifi.homeip.net> References: <20040213001703.616C75C3B@techpc04.okladot.state.ok.us> <20040213011324.GA55948@xor.obsecurity.org> <20040213035608.3AA11A38EA@scifi.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--gBBFr7Ir9EOA20Yy
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Feb 12, 2004 at 09:56:08PM -0600, Paul Seniura wrote:
>=20
> Hi Kris,
>=20
> > On Thu, Feb 12, 2004 at 06:17:03PM -0600, Paul Seniura wrote:
> > >=20
> > > Hi y'all,
> > >=20
> > > I'm trying to find a way to do a CFLAGS+=3D'-O' if and only if such a
> > > parm was not already provided before 'make' actually runs.
> > >=20
> > > I had this coded with the single =3D sign, i.e. without ?=3D or +=3D,=
but
> > > the process still acts as if +=3D was coded anyway, thus tacking on
> > > my -O *after* the port's own CFLAGS.
> > >=20
> > > GCC33 docs say the _last_ -O# is the one that will be used.
> > >=20
> > > I've seen other discussion on using -O2 but the point seems to be the
> > > ports that set -O2 explicitly are likely to work correctly.
>=20
> On Thu 12 Feb 2004 17:13:25 -0800, Kris Kennaway replied:
> > That's not a good assumption; many ports simply add -O2 (or -O3, or
> > -O999) because the authors "want their code to run fast". The set of
> > ports for which the authors have run full regression suites for all
> > supported versions of gcc and all supported OS and architecture
> > combinations is probably the null set.
>=20
> Thank you for responding, but I'm *really* not wanting this to
> become another discussion on "how high my Oh-levels should be". ;)
>=20
> My question for this discussion is specifically how to prevent
> overriding a port's own setting for that parm, and to provide a
> default setting -O[1] when the port does not set it at all?
>=20
> (I'll save my l-o-n-g-e-r reply for later... believe me I have reasons ;)
There's no general way. Some ports do ${CFLAGS} -O999, some do -O999
${CFLAGS}. The ports collection policy is that any port that
specifies its own optimization flags by default and uses them in
preference to ${CFLAGS} is a bug and must be fixed.
Kris
--gBBFr7Ir9EOA20Yy
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFALE35Wry0BWjoQKURAvpcAKDKGDBUujGANsAQe14kP20QvXmYQwCgq9NR
Qa3FIOi3C/1hcUHcoWWR/Ts=
=kfzX
-----END PGP SIGNATURE-----
--gBBFr7Ir9EOA20Yy--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040213040929.GA58196>