From owner-freebsd-stable@FreeBSD.ORG Mon Nov 7 06:21:58 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B6C0016A41F for ; Mon, 7 Nov 2005 06:21:58 +0000 (GMT) (envelope-from freebsd-stable@auscert.org.au) Received: from titania.auscert.org.au (gw.auscert.org.au [203.5.112.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F24543D45 for ; Mon, 7 Nov 2005 06:21:57 +0000 (GMT) (envelope-from freebsd-stable@auscert.org.au) Received: from app.auscert.org.au (app [10.0.1.192]) by titania.auscert.org.au (8.12.10/8.12.10) with ESMTP id jA76KMio000679 for ; Mon, 7 Nov 2005 16:20:22 +1000 (EST) Received: from app.auscert.org.au (localhost.auscert.org.au [127.0.0.1]) by app.auscert.org.au (8.13.1/8.13.1) with ESMTP id jA76LuC5049734 for ; Mon, 7 Nov 2005 16:21:56 +1000 (EST) (envelope-from freebsd-stable@auscert.org.au) Message-Id: <200511070621.jA76LuC5049734@app.auscert.org.au> To: freebsd-stable@freebsd.org From: Joel Hatton Dcc: Date: Mon, 07 Nov 2005 16:21:56 +1000 Subject: 5.x, 6.x and CPUTYPE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Nov 2005 06:21:58 -0000 Hi, I've noticed that some CPU definitions have changed in /etc/make.conf between 5 and 6. For good or for bad, I have up until now been building 5.x for both p3 and p4 architectures with 'i686' but this particular definition's removal from 6.x has given me cause to rethink my strategy. I'd like to know: Should I use 'i386' and build once for all, or use p3/p4 defs and build once for each? And if the latter, why? (does this give any worthwhile performance increase?) If I don't specify a CPUTYPE at all, will this be auto-detected in some way (which would probably not suit me) or will it fall back to i386? Is this a consistent requirement for world/kernel/ports? Finally, when building on a single host, but where multiple requirements are being met, is it possible to define different make.conf files for make or is it easier to just edit this file before each build? thanks, joel -- Joel Hatton -- Security Analyst | Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland | WWW: www.auscert.org.au Qld 4072 Australia | Email: auscert@auscert.org.au