From owner-freebsd-current Sat Sep 16 21:17:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id 6EC5137B423; Sat, 16 Sep 2000 21:17:16 -0700 (PDT) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id VAA07692; Sat, 16 Sep 2000 21:22:35 -0700 (PDT) (envelope-from sgk) From: Steve Kargl Message-Id: <200009170422.VAA07692@troutmask.apl.washington.edu> Subject: Re: upgrade libgmp? In-Reply-To: from Kris Kennaway at "Sep 16, 2000 08:35:00 pm" To: Kris Kennaway Date: Sat, 16 Sep 2000 21:22:35 -0700 (PDT) Cc: FreeBSD Current X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > On Sat, 16 Sep 2000, Steve Kargl wrote: > > > Before I jump in and attempt to do an upgrade of libgmp, > > I thought I'd asked if anyone else has endured this joy? > > > > Note, src/contrib/libgmp is at version 2.0.x and it is > > 3+ years old. The newest version is at 3.1. The Changelog > > indicates that there are numerous fixes and enhancements > > over 2.0.x. > > See http://people.freebsd.org/~kris/libgmp.tar.gz Thanks, Kris. I suspected that either you or markm would have already tackled the job. > I need to get back to this (and update to the latest version), but the > issue is how to specify the partially ordered set of compatible CPU > revisions which you'd like to build asm code for (same issue as with > openssl) 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"? -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message