Date: Wed, 19 Mar 2003 04:04:49 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: Guy Helmer <ghelmer@palisadesys.com> Cc: Guido van Rooij <guido@gvr.org>, "" <audit@FreeBSD.ORG> Subject: RE: /bin/sh flag NO_HISTORY Message-ID: <20030319035806.Y5708@gamplex.bde.org> In-Reply-To: <FPEBKMIFGFHCGLLKBLMMKENKCBAA.ghelmer@palisadesys.com> References: <FPEBKMIFGFHCGLLKBLMMKENKCBAA.ghelmer@palisadesys.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030319035806.Y5708>