From owner-freebsd-hackers Sat Apr 28 0:33:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 5FEF437B424 for ; Sat, 28 Apr 2001 00:33:11 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 984 invoked by uid 1000); 28 Apr 2001 07:31:21 -0000 Date: Sat, 28 Apr 2001 10:31:21 +0300 From: Peter Pentchev To: Joao Carlos Mendes Luis Cc: David O'Brien , hackers@freebsd.org, stable@freebsd.org Subject: Re: Trouble with 4.3-RELEASE compiler Message-ID: <20010428103121.D415@ringworld.oblivion.bg> Mail-Followup-To: Joao Carlos Mendes Luis , David O'Brien , hackers@freebsd.org, stable@freebsd.org References: <20010427194022.A18639@roma.coe.ufrj.br> <20010427171531.B15541@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010427171531.B15541@dragon.nuxi.com>; from obrien@freebsd.org on Fri, Apr 27, 2001 at 05:15:31PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Apr 27, 2001 at 05:15:31PM -0700, David O'Brien wrote: > On Fri, Apr 27, 2001 at 07:40:22PM -0300, Joao Carlos Mendes Luis wrote: > > I was installing a squid server with 4.3-RELEASE, and found that > > FreeBSD has now a bug in the compiler that affects squid. The default > > compilation of squid is with CFLAGS=-g -O2 -Wall, and this setup > > triggers the bug. > ... > > Should this be a reason to roll back the compiler to version > > 2.95.2, as it was before Tue Apr 10 19:23:19 2001 UTC, when it > > changed to 2.95.3? What to do with the upcoming CDs? > > No. It means the squid maintainer didn't do a proper job and make it so > that the system CFLAGS were used. Granted most don't know to export > CFLAGS to GNU configure when they run the configure script. (directed more at the original poster, despite replying to David) The www/squid* ports do a great job of using the system CFLAGS. And yes, there is an explicit warning in /etc/defaults/make.conf (which you should read, before setting your system-wide CFLAGS in /etc/make.conf) that using -O2 can trigger bugs. So.. why did you not use the port? :) And yes, -O2 bugs in gcc are a known issue.. :( G'luck, Peter -- This sentence claims to be an Epimenides paradox, but it is lying. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message