From owner-freebsd-current@FreeBSD.ORG Sat Aug 2 10:23:50 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2950A37B401 for ; Sat, 2 Aug 2003 10:23:50 -0700 (PDT) Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id D255E43FE3 for ; Sat, 2 Aug 2003 10:23:46 -0700 (PDT) (envelope-from ru@sunbay.com) Received: from whale.sunbay.crimea.ua (ru@localhost [127.0.0.1]) h72HNO0U039310 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 2 Aug 2003 20:23:24 +0300 (EEST) (envelope-from ru@sunbay.com) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.12.9/8.12.8/Submit) id h72HNNsd039305; Sat, 2 Aug 2003 20:23:23 +0300 (EEST) (envelope-from ru) Date: Sat, 2 Aug 2003 20:23:23 +0300 From: Ruslan Ermilov To: Peorth Message-ID: <20030802172322.GB36129@sunbay.com> References: <1059796086.35389.255.camel@artificial.ath.cx> <20030802055028.GB55688@sunbay.com> <1059804513.35389.307.camel@artificial.ath.cx> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yEPQxsgoJgBvi8ip" Content-Disposition: inline In-Reply-To: <1059804513.35389.307.camel@artificial.ath.cx> User-Agent: Mutt/1.5.4i cc: current@freebsd.org Subject: Re: groff and mkdep? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Aug 2003 17:23:50 -0000 --yEPQxsgoJgBvi8ip Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 01, 2003 at 11:08:33PM -0700, Peorth wrote: > That seems so weird. > CFLAGS and CXXFLAGS were set to something in the general environment, > for non-port builds, but I thought the FreeBSD make system used for > ports and such wouldn't get polluted by simply having that defined as a > variable in the env. *headscratch* Maybe just my mistake, but thanks a > lot. I never would've realized it was CFLAGS! Perhaps make should warn > if setting CFLAGS/CXXFLAGS are going to pollute, at least on certain > things like in the /usr/src tree, though up 'till that point, everything > built fine, too. *shrug* >=20 Hmm. From the make(1) manpage: : The four different classes of variables (in order of increasing prece- : dence) are: :=20 : Environment variables : Variables defined as part of make's environment. :=20 : Global variables : Variables defined in the makefile or in included makefiles. :=20 : Command line variables : Variables defined as part of the command line. :=20 : Local variables : Variables that are defined specific to a certain target. The : seven local variables are as follows: Are you telling me that setting CFLAGS in the ENVIRONMENT causes this strange behavior? (I cannot reproduce it here, because environment variables are of a lower precedence than globals.) Are you sure you weren't running make(1) with the -e option? (I can reproduce this with this option, as it causes environment variables to take higher precedence than globals.) Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software Ltd, ru@FreeBSD.org FreeBSD committer --yEPQxsgoJgBvi8ip Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE/K/OKUkv4P6juNwoRAhvgAJ9EYMqtCq4BXIOVJPCyrfAw9F7j1gCfW1Md X4HfYH7zyXLHdgIqkzvAbjg= =FWo+ -----END PGP SIGNATURE----- --yEPQxsgoJgBvi8ip--