From owner-freebsd-stable Tue Aug 21 13: 1:23 2001 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.dyndns.org (adsl-63-207-60-7.dsl.lsan03.pacbell.net [63.207.60.7]) by hub.freebsd.org (Postfix) with ESMTP id 889AF37B407; Tue, 21 Aug 2001 13:01:20 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 260B066D1C; Tue, 21 Aug 2001 13:01:20 -0700 (PDT) Date: Tue, 21 Aug 2001 13:01:19 -0700 From: Kris Kennaway To: "Karsten W. Rohrbach" Cc: Peter Wemm , Mike Smith , freebsd-stable@FreeBSD.ORG Subject: CPUTYPE and ports Message-ID: <20010821130119.H17739@xor.obsecurity.org> References: <20010819061017.92A3438FD@overcee.netplex.com.au> <20010821181752.V45276@mail.webmonster.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="Cp3Cp8fzgozWLBWL" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010821181752.V45276@mail.webmonster.de>; from karsten@rohrbach.de on Tue, Aug 21, 2001 at 06:17:52PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --Cp3Cp8fzgozWLBWL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Aug 21, 2001 at 06:17:52PM +0200, Karsten W. Rohrbach wrote: > just a quick note: the cpuflags in no way affect build options for > ports. the cpuflags do not affect building the source. would it make > sense for /etc/make.conf to evalute a magic cpu type such as > CPUTYPE=auto or CPUTYPE=local which throws in additional decision logic > for the ports make system. Not sure what you mean in this paragraph. CPUTYPE affects port builds by virtue of compiler optimizations, and there are some ports where it turns on additional code changes. > quick example: > port graphics/png has a flag WITH_PNG_MMX which makes sense. > if we know the cpuflags from the build system we could enable it > depending on the hardware it gets compiled on (or, with a fancier > layout of the way flags are defined in a config file, generate templates > for specific standard boxes). Look at - it's already trivial for the port to automatically enable this support based on MACHINE_CPU: the maintainer just hasn't done it yet. Kris --Cp3Cp8fzgozWLBWL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7gr4PWry0BWjoQKURAovxAKCqcSESPtrP5/UuwNzHpH57jDvMGwCfRwPC f+FxYAT1joBW/6fwo7ITPwE= =zAmU -----END PGP SIGNATURE----- --Cp3Cp8fzgozWLBWL-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message