Closed jensskott closed 5 years ago
I just committed a fix for master and will be included in the next release.
That said, fix aside, this tarball was created against master which is tracking Varnish 4.1 so there might be other issues.
For the time being you might want to try using the 4.0 branch instead.
Patched branch 4.0 with this and it now works to build
Thanks for the update.
I will update the code to deal with this. On 3 May 2016 1:08 p.m., "Jens Skott" notifications@github.com wrote:
Patched branch 4.0 with this and it now works to build
— You are receiving this because you modified the open/close state. Reply to this email directly or view it on GitHub https://github.com/varnish/libvmod-digest/issues/20#issuecomment-216508622
With fcbbf7e1911a4c9b12aa7bcbe40de9a1a987cb50 in place, this can be (re-)closed?
We could change master to work with both 4.0.x and 4.1.2 or redirect people using 4.0.x to the 4.0 branch.
What do we want to do? If it's the latter we can close this, otherwise I can work on a fix.
@fgsch did you find any workable solution to support both 4.0 and 4.1 on the same vmod code base? ifdef-ing init_function() and passing the vcc file through the preprocessor? feels rather hackish.
The approach I mentioned works, I have used it before. There is no need for preprocessor since vmodtool.py can understands both $Event and $init. You still need ifdef init_functions though. I will submit a PR for discussing it.
+1
EEOL
varnishd -V varnishd (varnish-4.0.2 revision bfe7cd1) Copyright (c) 2006 Verdens Gang AS Copyright (c) 2006-2014 Varnish Software AS