On Sat, 07 Mar, 2015 at 00:07:02 GMT, Michael Catanzaro wrote: > It looks like the CMake developers identified the cause of the issue and > will have it fixed before 3.2 is released. 3.2.0 had already been tagged. 3.2.1 will contain the fix. --Ben