[ccan] Valgrind + tests

[Tim Post]

Sorry to top post, I realize the need to break on error (even warnings
treated as errors), but importing modules from ccan written for
portability and testing, one should expect this, no? Or why do we have a
config.h?

I think perhaps I remain confused regarding the expected use of drop in
modules.

Cheers,
--Tim

On Tue, 2009-03-24 at 20:48 +0800, Tim Post wrote:
> Hi,
> 
> On Tue, 2009-03-24 at 23:00 +1030, Rusty Russell wrote:
> 
> > Sure.  Or you can submit something that uses it, and it'll break my compile
> > (-Wundef) and I'll update config.h automatically :)
> > 
> 
> Can you please explain the sanity of using -Wundef when knowingly using
> something that explicitly points to (and encourages modification of)
> config.h?
> 
> If HAVE_VALGRIND_VALGRIND_H is not set, it would make little difference
> to someone using a module that they grabbed. However, someone using
> autotools would have this on or off depending on what configure found.
> 
> Or am I missing something? Quite possibly, I am :)
> 
> Cheers,
> --Tim
> 
> 
> _______________________________________________
> ccan mailing list
> ccan at ozlabs.org
> https://ozlabs.org/mailman/listinfo/ccan