From owner-freebsd-current Thu May 17 5:11:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from casimir.physics.purdue.edu (casimir.physics.purdue.edu [128.210.146.111]) by hub.freebsd.org (Postfix) with ESMTP id E4CEB37B424 for ; Thu, 17 May 2001 05:11:26 -0700 (PDT) (envelope-from will@physics.purdue.edu) Received: by casimir.physics.purdue.edu (Postfix, from userid 1000) id 6C07118A47; Thu, 17 May 2001 07:11:16 -0500 (EST) Date: Thu, 17 May 2001 07:11:16 -0500 From: Will Andrews To: Michael Harnois Cc: freebsd-current@FreeBSD.ORG Subject: Re: world broken yet again Message-ID: <20010517071116.C26877@casimir.physics.purdue.edu> Reply-To: Will Andrews References: <51503.990091030@axl.fw.uunet.co.za> <86ae4cp5r2.fsf@mharnois.workgroup.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.15i In-Reply-To: <86ae4cp5r2.fsf@mharnois.workgroup.net>; from mdharnois@home.com on Thu, May 17, 2001 at 06:36:01AM -0500 X-Operating-System: Linux 2.2.18 sparc64 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, May 17, 2001 at 06:36:01AM -0500, Michael Harnois wrote: > Are you telling me this error had something to do with optimizations? No. But they can affect compiles in bizarre ways (believe me, in the four years that I've compiled world, I've seen several). If you compile with optimizations, you need to be wary of any failed buildworlds your machine gives. If you are compiling a world that you KNOW works, and optimizations give a problem, then you have a bona fide optimization problem. Sometimes it's correctable, sometimes not. However, in this case, you ran into a bona fide breakage. It was fixed awhile ago, so re-cvsup and re-make world. :) -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message