From owner-freebsd-current Sat Sep 16 21:31:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9C3A037B424; Sat, 16 Sep 2000 21:31:22 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id VAA07272; Sat, 16 Sep 2000 21:31:22 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 16 Sep 2000 21:31:22 -0700 (PDT) From: Kris Kennaway To: Steve Kargl Cc: FreeBSD Current Subject: Re: upgrade libgmp? In-Reply-To: <200009170422.VAA07692@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 16 Sep 2000, Steve Kargl wrote: > I'm not fluent in FSF configure scripts, but it looks like > configure tests the compiler for specific features to determine > CPU type. The gross hack would be to add CPU_TYPE="generic" > to /etc/defaults/make.conf, and allow users to define CPU_TYPE > in /etc/make.conf. It appears that for example CPU_TYPE="alpha" > is insufficient because each cpu type 21064, 21164, 21264 has > tuned asm code. The bmake file would then have a cascade of > #ifdef CPU_TYPE to pull in the right code. > > Would a CPU_TYPE variable be useful for others parts of "make world"? The issue is that you have all sorts of possibilities like i386, i486, pentium, pentiumpro, pentiummmx, k6, ... which you need to specify in order of preference. If someone would care to submit example code of how to handle this nicely from both the user and makefile perspective I'd be grateful :-) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message