Date: Tue, 2 Nov 2004 18:55:04 -0500 From: michael johnson <ahze@ahze.net> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-current@freebsd.org Subject: Re: HEADS UP: Ports are not ready for CFLAGS=-O2 in 6.0 Message-ID: <9DDB4C0A-2D2A-11D9-8349-000A95BB7150@ahze.net> In-Reply-To: <20041102234821.GA76782@xor.obsecurity.org> References: <20041102222000.GA65845@xor.obsecurity.org> <200411021736.21034.kirk@strauser.com> <20041102234821.GA76782@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 2, 2004, at 6:48 PM, Kris Kennaway wrote: > On Tue, Nov 02, 2004 at 05:36:17PM -0600, Kirk Strauser wrote: >> On Tuesday 02 November 2004 16:20, Kris Kennaway wrote: >> >>> (there are at least 350 ports that emit warnings about aliasing, and >>> would >>> probably have runtime errors when compiled with -O2; moreover, a >>> number of >>> ports fail to even build with -O2). >> >> Out of curiosity, are those ports like to have equivalents in Gentoo's >> "portage" system? Those guys love to build with -O310 >> -fomit-instructions >> but their stuff seems to pretty much work. Why do we seem to have so >> many >> problems with (presumably?) the same software on our system? > > Don't know, perhaps they don't care about the fraction of ports that > don't work properly since the rest of them have such eleet > optimization. Some ports from portage ie http://www.gentoo.org/cgi-bin/viewcvs.cgi/*checkout*/media-libs/gst- plugins/gst-plugins-0.8.5-r1.ebuild gst-plugins use replace-flags which is for example ... ${CFLAGS:S/-O2/-O} or filter-flags which removes flags that cause a known build failure. Michael > Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9DDB4C0A-2D2A-11D9-8349-000A95BB7150>