This is driving me nuts, and it's almost certainly something dumb. One of my CMake users lost a hard drive and had to reimage.
Now she's installed CMake 2.8 and it LOOKS like it's all OK, but any attempt to do a CMake hangs because the attempt to compile CMakeCCompilerId.c winds up passing a bunch of flags and then "-o CMakeCCompilerId.c" - that is, the -o flag, TWO spaces, and then CMakeCCompilerId.c. So there's no output file specification; the input filespec becomes the output, and the compiler dutifully waits for input from stdin. Now, I think I've seen this before, but I'm damned if I can remember what causes it. As far as I can tell, the compiler call is generated within cmake.exe, which kinda makes it hard to debug. Any ideas? Thanks in advance... -- ...phsiii Phil Smith III [email protected]<mailto:[email protected]> Voltage Security, Inc. www.voltage.com<http://www.voltage.com>
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
