Re: POSIXLY_CORRECT not correctly unset in getopt.m4?

[Dustin J. Mitchell]

On Sun, Sep 5, 2010 at 10:42 AM, Dustin J. Mitchell <address@hidden> wrote:
> I re-updated my gnulib repository, and I don't see any changes to this
> file, so I'm assuming that the bug is still present.  I will look for
> a fix and send a patch, but I thought I would poll for corroboration
> or any other information that I don't see in the archives.

Patch here:
  
http://github.com/djmitche/gnulib/commit/bb8deed31a76e949301f3b2270899c77c13fae6a
  
http://github.com/djmitche/gnulib/commit/bb8deed31a76e949301f3b2270899c77c13fae6a.patch

I've fixed this by calling setenv() directly in the body of the
AC_TRY_RUN program.

My worry here is that, on a system without setenv, will the setenv
module successfully supply the code from setenv.c to the AC_TRY_RUN
invocation?  If not, is there another way?

Thanks in advance!

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com