From owner-freebsd-stable Wed Mar 7 1:35:37 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 7F06437B71A for ; Wed, 7 Mar 2001 01:35:30 -0800 (PST) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.2/8.11.1) with ESMTP id f279YdH19247; Wed, 7 Mar 2001 01:34:39 -0800 (PST) (envelope-from jkh@osd.bsdi.com) To: ohartman@klima.physik.uni-mainz.de Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ARCH flag in new make.conf In-Reply-To: References: X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010307013439I.jkh@osd.bsdi.com> Date: Wed, 07 Mar 2001 01:34:39 -0800 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 37 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: "Hartmann, O." Subject: ARCH flag in new make.conf Date: Wed, 7 Mar 2001 09:30:33 +0100 (CET) > I'm really confused and surprised by the fact, that with the upcoming new > FreeBSD 4.3 in its make.conf we can choose architectural parameters for the > CPU architecture. And I will tell you why. It's not supposed to be set by the "general public" and failing to note this was an error, thanks. I've just committed the following patch: +# $FreeBSD: src/etc/defaults/make.conf,v 1.97.2.38 2001/03/07 08:39:29 jkh Exp $ # # NOTE: Please would any committer updating this file also update the # make.conf(5) manual page, if necessary, which is located in @@ -25,6 +25,16 @@ # (AMD CPUs) k7 k6-2 k6 k5 # (Intel CPUs) p4 p3 p2 i686 i586/mmx i586 i486 i386 # Alpha/AXP architecture: ev6 pca56 ev56 ev5 ev45 ev4 +# +# WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! +# +# It should also be noted that YOU SHOULD NOT SET CPUTYPE TO ANYTHING +# unless you're absolutely 100% sure you know what you are doing! Some +# things are known to break with -march=i686, for example, and simply +# building the world and kernel with CPUTYPE set to something other than +# the default (i386) is currently guaranteed to hurt you. You should +# build things very selectively with CPUTYPE set and proceed only if they +# still appear to work. # #CPUTYPE=i686 #NO_CPU_CFLAGS= true # Don't add -march= to CFLAGS automatically I hope that this will prevent others from following (falling?) in your footsteps. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message