From owner-freebsd-stable  Wed Mar  7  3:28:40 2001
Delivered-To: freebsd-stable@freebsd.org
Received: from eve.framatome.fr (eve.framatome.fr [195.101.50.66])
	by hub.freebsd.org (Postfix) with ESMTP id 4162837B718
	for <freebsd-stable@FreeBSD.ORG>; Wed,  7 Mar 2001 03:28:35 -0800 (PST)
	(envelope-from ubc@paris.framatome.fr)
Received: from localhost (ubc@localhost)
	by eve.framatome.fr (8.9.3/8.9.3) with ESMTP id MAA86041;
	Wed, 7 Mar 2001 12:28:29 +0100 (CET)
	(envelope-from ubc@paris.framatome.fr)
Date: Wed, 7 Mar 2001 12:28:29 +0100 (CET)
From: Claude Buisson <ubc@paris.framatome.fr>
X-Sender: ubc@eve.framatome.fr
To: Kris Kennaway <kris@obsecurity.org>
Cc: Jordan Hubbard <jkh@osd.bsdi.com>,
	ohartman@klima.physik.uni-mainz.de, freebsd-stable@FreeBSD.ORG
Subject: Re: ARCH flag in new make.conf
In-Reply-To: <20010307025918.A37732@mollari.cthul.hu>
Message-ID: <Pine.BSF.4.10.10103071224110.85885-100000@eve.framatome.fr>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Wed, 7 Mar 2001, Kris Kennaway wrote:

> On Wed, Mar 07, 2001 at 11:51:47AM +0100, Claude Buisson wrote:
> > Please explain:
> > 
> > If CPUTYPE is potentially dangerous, why make its use automatic ? needing
> > a special flag (commented OUT in /etc/default/make.conf) to deny it.
> > 
> > Please, revert the default: do NOT use CPUTYPE optimization in a standard
> > build, and let the user ADD it in his /etc/make.conf if he wants to
> > (what I do already by tweaking CFLAGS...).
> 
> Okay, you're getting worked up here for nothing.  There are a couple
> of points:
> 
> * Jordan's warning added to make.conf is under debate, and I think
>   it's excessive.
> 
> * CPUTYPE does nothing by default unless you set it.  Think of it as
>   just a handy way to add the correct -m<foo> flags to your CFLAGS
>   setting without having to grep through info pages looking for the
>   right values.  It also does a bit more than this by enabling asm code
>   in OpenSSL and (soon) some ports, but again, only if you specifically
>   enable it.
> 
> > Furthermore:
> > 
> > Does the current setting implying the use of CPUTYPE to build releases ?
> > (I probably do not want a march=pentiumpro to build software intended
> > to run on a 386).
> 
> If you don't set CPUTYPE, your software will continue to run on all
> i386-class CPUs.  No defaults have changed here, nor will they for as
> long as FreeBSD continues to support the 386 CPU.
> 
> Kris
> 

Thanks for the explanation, but I have another question (I know,
I am dumb):

given that the optimization MUST be activated by a CPUTYPE=XXX in
the user's /etc/make.conf, what is the use of NO_CPU_FLAGS ? 
just needing 2 lines instead of 0 in /etc/make.conf ?

Claude Buisson


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message