[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Autoconf. Generated configure file may use grep but does not unset t
|
From: |
Eric Blake |
|
Subject: |
Re: Autoconf. Generated configure file may use grep but does not unset the GREP_OPTIONS. |
|
Date: |
Wed, 08 Apr 2009 18:44:44 -0600 |
|
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.21) Gecko/20090302 Thunderbird/2.0.0.21 Mnenhy/0.7.6.666 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Ralf Wildenhues on 4/8/2009 3:52 PM:
>> Thanks for the report. I agree that unsetting GREP_OPTIONS as part of
>> AC_PROG_GREP (and friends) sounds reasonable,
>
> Why not just unset it as part of AS_SHELL_SANITIZE? There are lots of
> plain grep uses in configure scripts. I see this as sanitization
> similar to LC_ALL.
Are there any other frequently-used *_OPTIONS variables that we should
also consider unsetting? For example, $LESS affects less(1), but you are
unlikely to use less in a configure script. Or $M4PATH affects m4(1), but
only after the command line options, so it shouldn't affect autom4te's
usage patterns.
- --
Don't work too hard, make some time for fun as well!
Eric Blake address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkndRPwACgkQ84KuGfSFAYCEKQCfb90OcSPwAWxoxRc1xaud7TsI
UsMAoNiiCVOoxdBqF0x5yZZiPwCJ3msr
=dXXI
-----END PGP SIGNATURE-----