From owner-freebsd-stable Wed Mar 7 2:59:22 2001 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-158.dsl.lsan03.pacbell.net [63.207.60.158]) by hub.freebsd.org (Postfix) with ESMTP id ACEE237B71A for ; Wed, 7 Mar 2001 02:59:18 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 722A966E1B; Wed, 7 Mar 2001 02:59:18 -0800 (PST) Date: Wed, 7 Mar 2001 02:59:18 -0800 From: Kris Kennaway To: Claude Buisson Cc: Jordan Hubbard , ohartman@klima.physik.uni-mainz.de, freebsd-stable@FreeBSD.ORG Subject: Re: ARCH flag in new make.conf Message-ID: <20010307025918.A37732@mollari.cthul.hu> References: <20010307013439I.jkh@osd.bsdi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="k+w/mQv8wyuph6w0" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ubc@paris.framatome.fr on Wed, Mar 07, 2001 at 11:51:47AM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 07, 2001 at 11:51:47AM +0100, Claude Buisson wrote: > Please explain: >=20 > If CPUTYPE is potentially dangerous, why make its use automatic ? needing > a special flag (commented OUT in /etc/default/make.conf) to deny it. >=20 > 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 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: >=20 > Does the current setting implying the use of CPUTYPE to build releases ? > (I probably do not want a march=3Dpentiumpro 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 --k+w/mQv8wyuph6w0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6phSGWry0BWjoQKURAqt+AKCMUarCCGbOoFiYQ/cCgA7+wTYpfwCeNvS7 3NGDsfanFnucK9FgPMZOXWI= =kRLh -----END PGP SIGNATURE----- --k+w/mQv8wyuph6w0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message