[varnishcache/varnish-cache] explicit_bzero() causing havoc (#3051)

[Geoff Simmons]

On 9/16/19 16:31, Poul-Henning Kamp wrote:
> 
>> The EXPLICIT_BZERO check is still AC_REQUIRE'd in varnish.m4, from
>> VARNISH_PREREQ and _VARNISH_CHECK_DEVEL, which are used in VMOD
>> development. Since it's not defined now, this leads to a cascade of
>> error messages when autogen.sh is called for a VMOD.
> 
> Ticket please, that is out of my comfort area.

devnexen wrote to me that he has a PR up to fix that.

https://github.com/varnishcache/varnish-cache/pull/3062

Looks like the PR will fix the problem.

But it didn't make it into the release? Then there's a somewhat buggy
varnish.m4 in 6.3.0. The workaround is to just ignore the error
messages, but they're going to be annoying to look at from now on.


Best,
Geoff
-- 
** * * UPLEX - Nils Goroll Systemoptimierung

Scheffelstraße 32
22301 Hamburg

Tel +49 40 2880 5731
Mob +49 176 636 90917
Fax +49 40 42949753

http://uplex.de

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-dev/attachments/20190916/009b8388/attachment-0001.bin>