Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: <160508145807.ZM10454@torch.brasslantern.com>
References: <CAEyFG7ZkxS9iuVtEoJT2aa_ErBm=Nm6JqkpSgt=-=3P-nuZBtg@mail.gmail.com>
	<160508105949.ZM9904@torch.brasslantern.com>
	<20160508201217.5924511a@ntlworld.com>
	<160508132406.ZM10234@torch.brasslantern.com>
	<20160508212858.384e3dbf@ntlworld.com>
	<160508145807.ZM10454@torch.brasslantern.com>
Date: Sun, 8 May 2016 15:16:46 -0700
Message-ID: <CAH+w=7Ywz41S3-z=Q62_pwSApkFKNgdt7S6_baed0Aio54hdvA@mail.gmail.com>
Subject: Re: leading '=' in enviroment variable truncated
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Content-Type: text/plain; charset=UTF-8

On Sun, May 8, 2016 at 2:58 PM, Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> If we're going to go so far as to have a configure test, shouldn't we
> include a check that setenv is in fact defined before attempting to
> run a test that uses it?

Never mind.  You included the test but spelled "setenv" wrong, and I
missed that you'd tested anything at all.

However, even if I change the "setsnv" to "setenv" the test still gets
the wrong results.

conftest.c:259:4: warning: type specifier missing, defaults to 'int'
[-Wimplicit-int]
   main()
   ^~~~
conftest.c:261:7: warning: implicit declaration of function 'setenv'
is invalid in C99 [-Wimplicit-function-declaration]
      setenv("NAME", "=VALUE", 1);
      ^
conftest.c:262:29: warning: implicit declaration of function 'getenv'
is invalid in C99 [-Wimplicit-function-declaration]
      return strcmp((char *)getenv("NAME"), "=VALUE");
                            ^
conftest.c:262:21: warning: cast to 'char *' from smaller integer type
'int' [-Wint-to-pointer-cast]
      return strcmp((char *)getenv("NAME"), "=VALUE");
                    ^
4 warnings generated.
configure:12601: $? = 0
configure:12601: ./conftest
./configure: line 1719: 90473 Segmentation fault: 11  (core dumped)
./conftest$ac_exeext