From owner-freebsd-questions Fri Nov 8 12:36:27 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5922737B416 for ; Fri, 8 Nov 2002 12:36:20 -0800 (PST) Received: from clunix.cl.msu.edu (clunix.cl.msu.edu [35.9.2.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 950C743E3B for ; Fri, 8 Nov 2002 12:36:19 -0800 (PST) (envelope-from jerrymc@clunix.cl.msu.edu) Received: (from jerrymc@localhost) by clunix.cl.msu.edu (8.11.6+Sun/8.11.6) id gA8Ka7m19671; Fri, 8 Nov 2002 15:36:07 -0500 (EST) From: Jerry McAllister Message-Id: <200211082036.gA8Ka7m19671@clunix.cl.msu.edu> Subject: Re: /etc/make.conf - Multiple Machines To: drew@mykitchentable.net (Drew Tomlinson) Date: Fri, 8 Nov 2002 15:36:07 -0500 (EST) Cc: freebsd-questions@FreeBSD.ORG (FreeBSD Questions) In-Reply-To: <006301c2874e$fc27c9a0$6e2a6ba5@tagalong> from "Drew Tomlinson" at Nov 08, 2002 09:48:02 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > I'm trying to set up a build machine as described in section 21.5 of the > Handbook. The directions say to use a common /etc/make.conf for all > machines that will share binaries. One of my machines is an i686 class > CPU. The other is an i585 CPU. To what value should I set CPUTYPE. > Default (nothing)? i586 as it's the lowest common denominator? And is > there any value in setting CFLAGS and COPTFLAGS after setting CPUTYPE to > whatever I should set it? You can have more than one 'cpu' entry in the conf file. so: cpu I486_CPU cpu I586_CPU cpu I686_CPU Would be legal if you want. Supposedly it makes the kernel just a bit begger, but not a lot. ////jerry > > Thanks, > > Drew > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message