vtest status

Willy TARREAU wtarreau at haproxy.com
Thu Jan 10 05:49:13 UTC 2019

Hi Poul-Henning!

On Wed, Jan 09, 2019 at 10:09:15PM +0000, Poul-Henning Kamp wrote:
> --------
> In message <1ca72b15-d581-4556-713a-a95106aa2d09 at haproxy.com>, Frederic Lecaille writes:
> Try the stuff I just committed.
> If you say "make vtest" you get no varnishsupport
> If you say "make varnishtest" and point the variable at your
> varnish source tree, you get varnish support.

Indeed, it's much easier now :-)  It's the first time I can build it.
I had to use this since there are probably still options that the user
has to tune :

      make CC='gcc -DHAVE_SYS_VFS_H'

I think we can plan on adding a CFLAGS or whatever variable and enumerate
the most common defines that users may need. They're all supposed to be
sufficiently autonomous developers to be able to figure what they need
to pass to build it.

We also need to make this "python3" thing a variable in the makefile. On
my previous distro, it was called "python". Same, developers will just
have to force the variable if they want.

Everything looks good this way, I'll spread the word here to the team.
We may propose you some patches for the few points above, and after this
I think we can update our doc in haproxy to refer to the vtest repo and
suggest how to build it.

Thank you!

More information about the varnish-dev mailing list