From owner-freebsd-qa Tue Mar 13 14:32:59 2001 Delivered-To: freebsd-qa@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id B031937B71A; Tue, 13 Mar 2001 14:32:56 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f2DMWnG39176; Tue, 13 Mar 2001 14:32:49 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010313141251.A18519@mollari.cthul.hu> Date: Tue, 13 Mar 2001 14:32:28 -0800 (PST) From: John Baldwin To: Kris Kennaway Subject: Re: cputype=486 Cc: kris@FreeBSD.org, jkh@FreeBSD.org, marcel@FreeBSD.org, qa@FreeBSD.org, Marcel Moolenaar , Larry Rosenman Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13-Mar-01 Kris Kennaway wrote: > On Tue, Mar 13, 2001 at 09:48:28PM +0000, Larry Rosenman wrote: >> So, what is the final word from the powers that be re: 4.3 and CPUTYPE? > > CPUTYPE has nothing to do with the problem here, so it doesn't need to > be removed. The issue is that libraries from the host system are > being used in some cases by the installed tools built for the target > system, which is the wrong behaviour and may cause them to fail in > other situations than if they were compiled with CPUTYPE (remember, > CPUTYPE does nothing which you couldn't already do with CFLAGS). > > Kris Well, solving this problem in a sane fashion is not easy, and I don't think we have time to do it before 4.3. I think that there should be a warning that building a world with a CPUTYPE < the CPUTYPE of the build machine is not supported for 4.3. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message