From owner-freebsd-audit Tue Mar 18 9: 5: 9 2003 Delivered-To: freebsd-audit@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 586AA37B401 for ; Tue, 18 Mar 2003 09:05:08 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37E2043FA3 for ; Tue, 18 Mar 2003 09:05:07 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id EAA23575; Wed, 19 Mar 2003 04:04:49 +1100 Date: Wed, 19 Mar 2003 04:04:49 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Guy Helmer Cc: Guido van Rooij , "" Subject: RE: /bin/sh flag NO_HISTORY In-Reply-To: Message-ID: <20030319035806.Y5708@gamplex.bde.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-audit@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 18 Mar 2003, Guy Helmer wrote: > On Tue, 18 Mar 2003, Bruce Evans wrote: > > However, it's not really necessary to provide a global knob for every > > possible -D option. I sometimes test compiling sh with -DNO_HISTORY > > (too see how much bloatier the library bloat has become). I just use > > something like "make CC='cc -DNOHISTORY'". For more global builds > > like picobsd it would be better to hack on COPTS and fix COPTS to work > > right. I meant to say that it is better to hack on COPTS than CC. First class support for NOHISTORY in sh/Makefile might be better than hacks. It depends on whether you think it is generally useful. I forgot to say that NO_HISTORY is a poor name for a global variable either way. > I usually look at the Makefiles first for knobs like this because I assume > if there are knobs in them, they are knobs that ought to work. If I have > to look deeper into the source for knobs, I assume they may not be > operational because they aren't "published". > > I haven't looked, but is NO_HISTORY used elsewhere? If so, perhaps it would > be a good candidate for a global knob to reduce bloat in a build... FreeBSD never defined it AFAIK. It's surprising that it still works. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-audit" in the body of the message