From owner-freebsd-stable Wed Mar 7 1:44:29 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 0D9A937B718 for ; Wed, 7 Mar 2001 01:44:24 -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 f279hNH19313; Wed, 7 Mar 2001 01:43:23 -0800 (PST) (envelope-from jkh@osd.bsdi.com) To: kris@obsecurity.org Cc: ohartman@klima.physik.uni-mainz.de, antony@abacus.co.uk, freebsd-stable@FreeBSD.ORG Subject: Re: ARCH flag in new make.conf In-Reply-To: <20010307012454.A14664@mollari.cthul.hu> References: <20010307011446.A8574@mollari.cthul.hu> <20010307012454.A14664@mollari.cthul.hu> 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: <20010307014323M.jkh@osd.bsdi.com> Date: Wed, 07 Mar 2001 01:43:23 -0800 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think the point is that you can be no more certain that Mr. Hartman's problems were *not* caused by setting the -march flag to i686 than I can be absolutely certain that they were. Given no better than 50/50 certainty, however, the warning appeared prudent given that we're unlikely to know with anything substantially better than 50/50 on release day and the penalty for being "wrong" is fairly high, whereas the penalty for being "right" is no worse than a gratuitous warning which scares a few people away from an option which wouldn't have saved them anything truly substantial in any case. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message