On Fri, Oct 28, 2011 at 9:18 AM, Bill Hoffman <bill.hoff...@kitware.com> wrote: > On 10/20/2011 5:17 PM, Clinton Stimpson wrote: > >> For the non working build, we get this in the configure output: >> http://www.cdash.org/CDash/buildSummary.php?buildid=1635763 >> -- Checking whether long long and __int64 are the same type >> -- Checking whether long long and __int64 are the same type - yes >> ... >> -- Checking whether C++ compiler has 'long long' >> -- Checking whether C++ compiler has 'long long' - no >> >> >> And a working build gets this: >> http://www.cdash.org/CDash/buildSummary.php?buildid=1633025 >> -- Checking whether long long and __int64 are the same type >> -- Checking whether long long and __int64 are the same type - yes >> ... >> -- Checking whether C++ compiler has 'long long' >> -- Checking whether C++ compiler has 'long long' - yes >> -- Checking if istream supports long long >> -- Checking if istream supports long long - yes >> -- Checking if ostream supports long long >> -- Checking if ostream supports long long - yes >> > > OK, so we have a log from a broken build now. > > http://public.kitware.com/Bug/view.php?id=12523 > > Basically, it seems that > Checking whether C++ compiler has 'long long' failed to compile with the > following output: > .... > > LINK: fatal error LNK1104: File "C: \ work-c \ b1 \ CMake \ Source \ kwsys \ > CMakeFiles \ CMakeTmp \ Debug \ cmTryCompileExec.exe" GE can not be opened. > [C: \ work-c \ b1 \ CMake \ Source \ kwsys \ CMakeFiles \ CMakeTmp \ > cmTryCompileExec.vcxproj] > > > The cmTryCompileExec.exe can not be written to for some reason. Any ideas? > > > -Bill > > > -- > > 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers >
Reboot the machine...? Use Process Explorer to hunt down and kill rogue VS instances? Maybe a hung/dead Visual Studio from a previous run has a lock on the file. -- 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://public.kitware.com/cgi-bin/mailman/listinfo/cmake-developers