Bruno Haible <br...@clisp.org> writes: >> Right. It would be nice if gnulib's valgrind m4 test was a bit >> smarter, maybe it should try to build a small program printing >> something to stdout and see if valgrind is able to run it and that it >> prints the magic string to stdout. If that doesn't work, disable >> valgrind. > > Implemented as follows. Hope I didn't break anything.
Neat, thank you. I'll start to use it, and we'll see how it works.
Btw, I just realized the module is confusingly named, since
modules/*-tests is used in gnulib to designate gnulib module self-tests.
Nothing appears to break, and I can't think of a better name right now
('valgrind' is a bit too general and non-descriptive of what the module
does).
/Simon
signature.asc
Description: PGP signature
