The recent cputest addition broke the build with clang for me,
since clang calculates the stack size differently than gcc.

Put the strict limit into all warning by default
(this starts enforcing it for examples, for example)
and raise the limit by a few orders, which might appear
Sisyphean but I believe it's needed for putting two
conflicting limits on the compiler command line.

Ján Tomko (2):
  build: warn on a large frame by default
  build: relax the relaxed stack frame limit further

 m4/virt-compile-warnings.m4 | 4 ++--
 src/Makefile.am             | 2 --
 tools/Makefile.am           | 2 --
 3 files changed, 2 insertions(+), 6 deletions(-)

-- 
2.19.2

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list