On 05/30/2014 01:47 PM, Kieran Colford wrote:
> The help message generated by a configure script using this module
> implied that valgrind was disabled by default, which it wasn't.
> Left the auto enablement in and patched the help message like:
> s/enable/disable/
> ---
> ChangeLog|
The help message generated by a configure script using this module
implied that valgrind was disabled by default, which it wasn't.
Left the auto enablement in and patched the help message like:
s/enable/disable/
---
ChangeLog|8
m4/valgrind-tests.m4 |4 ++--
2 files ch
On 14-05-30 06:59 AM, Pádraig Brady wrote:
> On 05/28/2014 04:53 PM, Kieran Colford wrote:
>> The help message generated by a configure script using this module
>> implied that valgrind was disabled by default, which it wasn't.
>> Patched so that valgrind is in fact disabled in accordance with th
On 05/28/2014 04:53 PM, Kieran Colford wrote:
> The help message generated by a configure script using this module
> implied that valgrind was disabled by default, which it wasn't.
> Patched so that valgrind is in fact disabled in accordance with the
> documentation.
Note doc/valgrind-tests.texi d
The help message generated by a configure script using this module
implied that valgrind was disabled by default, which it wasn't.
Patched so that valgrind is in fact disabled in accordance with the
documentation.
---
ChangeLog|8
m4/valgrind-tests.m4 |4 ++--
2 files
The help message generated by a configure script using this module
implied that valgrind was disabled by default, which it wasn't.
Patched so that valgrind is in fact disabled in accordance with the
documentation.
---
ChangeLog|7 +++
m4/valgrind-tests.m4 |4 ++--
2 files c
