This patch against next (because the offending patch is not in master yet)
fixes one cause of the valgrind warnings Bill reported recently. It doesn't
fix the C++ code, it only fixes the module that accidentially spotted this by
a bug in itself.
EikeFrom
Thanks.
Applied and pushed to 'next':
http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=20cb5edbcaaf89c35638911c27e6aec1c7fc022f
On Fri, Nov 18, 2011 at 10:18 AM, Rolf Eike Beer e...@sf-mail.de wrote:
This patch against next (because the offending patch is not in master yet)
fixes one