am__check_pre in the automake-generated Makefile basically runs

	test -d tests || mkdir tests || exit $?

When running out-of-tree with parallel make (as vtest does), this
becomes racy. Avoid the race by a mkdir ignoring the error

The previous commit did not solve the issue for all cases
- we also change OFLAGS in configure

In particular with --enable-developer-warnings, we select strict compiler
options for CFLAGS, which are too strict for the configure built-in conftest.c
code.

Make distcheck calls configure again for an out-of-tree build, so it would
see the CFLAGS the "outer" configure built. To avoid this situation, we
restore the original CFLAGS for the inner configure.

I wonder if there is a better, more autoconf-ish, solution to this problem.

Tested with SolarisStudio 12.4 on amd64/x86

and define it as NOP for Sun CC

It took me way too long to understand that empty declarations
found by suncc were caused by the extra ;

To avoid an undefined symbol __stack_chk_fail_local due to compiling
and linking gcc not seeing the same flags, we need to trick libtool
into passing a flag it would otherwise remove.

Please hold your whitespace ocds and exclude the non-standard indent
chosen to avoid excessive line length.

I am not entirely happy about this and we should try to find a better solution
to this chicken-egg-ish situation:

- part of our documentation is hand-written (in git/srcdir), part is auto-
  generated

- because we add generated rsts to the dist, they are not in srcdir when
  building from git, but they are when building from a dist (tarball)

- sphinx wants all files in one doctree - there seems to be no include path

I tend to lean towards removing generated rsts from the dist to unify the
src tree for git vs. dist builds, but I'd like to avoid too much change at
this point due to other priorities.

... which revealed that they actually fail atm, so another fix will be coming up

This allows unattended updates of vtest.sh itself by looping externally

Fixes #2021

We already had a check that took care of this in an architecture
independent way.

them a clear type.

Fixes #2016

Closes #1750

Closes #2155

Fixes #2134.

HTC_RxInit could write a single '\0' NUL character outside of the
workspace when its called and there is zero bytes left in the
workspace. This would trigger the workspace canary causing subsequent
assertion.

Fix by releaving HTC_RxInit of adding the '\0' character.

HTC_RxStuff now returns HTC_S_Overflow early if the available buffer
space is zero. The '\0' character is inserted just before calling the
completion check function.

Also fix an off-by-one error on the http_{req|resp}_size calculations,
where the maximum number of bytes accepted was one less than the
paramter indicated. c00039.vtc and c00040.vtc has been edited to
reflect that and to be more expressive about the sizes they generate.

Fixes: #1834

Make sure that the workspace can accomodate the pipelined data before
memmoving it into place.

Add a comment on an open issue in the H2 code path that could trigger
this assert.