Date: Sat, 16 Sep 2000 21:31:22 -0700 (PDT) From: Kris Kennaway <kris@FreeBSD.org> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: FreeBSD Current <freebsd-current@FreeBSD.org> Subject: Re: upgrade libgmp? Message-ID: <Pine.BSF.4.21.0009162128540.6857-100000@freefall.freebsd.org> In-Reply-To: <200009170422.VAA07692@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <forsythe@alum.mit.edu>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0009162128540.6857-100000>