From owner-freebsd-questions@FreeBSD.ORG Thu May 13 15:48:59 2004 Return-Path: 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 1345D16A4CF for ; Thu, 13 May 2004 15:48:59 -0700 (PDT) Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F69843D5A for ; Thu, 13 May 2004 15:48:58 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (0d85626470725215f8e32f24ba455935@adsl-67-115-73-128.dsl.lsan03.pacbell.net [67.115.73.128])i4DMmvGp006734; Thu, 13 May 2004 17:48:57 -0500 (CDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 0286751BB5; Thu, 13 May 2004 15:48:56 -0700 (PDT) Date: Thu, 13 May 2004 15:48:56 -0700 From: Kris Kennaway To: platanthera Message-ID: <20040513224856.GB19453@xor.obsecurity.org> References: <200405132329.07892.platanthera@web.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Yylu36WmvOXNoKYn" Content-Disposition: inline In-Reply-To: <200405132329.07892.platanthera@web.de> User-Agent: Mutt/1.4.2.1i cc: freebsd-questions@freebsd.org Subject: Re: COPTFLAGS (not?) only for compiling the kernel? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 May 2004 22:48:59 -0000 --Yylu36WmvOXNoKYn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 13, 2004 at 11:29:07PM +0200, platanthera wrote: > [/etc/make.conf] > ... > # To compile just the kernel with special optimizations, you should use > # this instead of CFLAGS (which is not applicable to kernel builds anyway= ). > # There is very little to gain by using higher optimization levels, and d= oing > # so can cause problems. > # > COPTFLAGS=3D [whatever] > ... >=20 > just the kernel... sounds like COPTFLAGS setting should not effect world = or=20 > port builds, but apparently it does. It shouldn't, CFLAGS is used for that. Kris --Yylu36WmvOXNoKYn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAo/tYWry0BWjoQKURAsq0AKDOukssBTbMt59b6lmgwQJsPeLpXwCg18V+ +XYDTI1dUrygxMxfzWIYTjk= =bIw1 -----END PGP SIGNATURE----- --Yylu36WmvOXNoKYn--