[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: |
Ralf Wildenhues |
Subject: |
Re: Autoconf. Generated configure file may use grep but does not unset the GREP_OPTIONS. |
Date: |
Wed, 8 Apr 2009 23:52:10 +0200 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
Hello Eiric, Ilay,
* Eric Blake wrote on Wed, Apr 08, 2009 at 02:56:38PM CEST:
> According to Ilay Bobir on 4/4/2009 5:57 PM:
> > Starting with version 2.4 GNU grep supports specification of default
> > option values via GREP_OPTIONS environment variable. Many if not all of
> > the configure files generated by the autoconf use grep. For example,
> > configure file for libtool uses grep.
>
> 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.
(There has been a report, I think on the mingw-users list, about
somebody with GREP_OPTIONS set in the environment, which caused lots of
spurious configure test failures.)
Thanks,
Ralf