Date: Wed, 7 Mar 2001 11:51:47 +0100 (CET) From: Claude Buisson <ubc@paris.framatome.fr> To: Jordan Hubbard <jkh@osd.bsdi.com> Cc: ohartman@klima.physik.uni-mainz.de, freebsd-stable@FreeBSD.ORG Subject: Re: ARCH flag in new make.conf Message-ID: <Pine.BSF.4.10.10103071144200.85885-100000@eve.framatome.fr> In-Reply-To: <20010307013439I.jkh@osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 7 Mar 2001, Jordan Hubbard wrote: > 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=<cpu> to CFLAGS automatically > > I hope that this will prevent others from following (falling?) in your > footsteps. > > - Jordan > 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...). 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). Claude Buisson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.10103071144200.85885-100000>