MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0013343CMakeCMakepublic2012-06-21 18:472013-04-17 08:54
Reportermichael_cow 
Assigned ToDavid Cole 
PrioritynormalSeveritymajorReproducibilityrandom
StatusclosedResolutionno change required 
PlatformIntelOSWindowsOS Version7
Product VersionCMake 2.8.8 
Target VersionFixed in Version 
Summary0013343: Random Configure Failure
DescriptionI am seeing similar behavior that was reported as fixed here: http://public.kitware.com/Bug/view.php?id=12957 [^]

I attempt to configure a cmake project in windows and randomly the project will fail with the following errror message:
Check for working C compiler using: Visual Studio 10
Check for working C compiler using: Visual Studio 10 -- works
Detecting C compiler ABI info
Detecting C compiler ABI info - failed
Check for working CXX compiler using: Visual Studio 10
Check for working CXX compiler using: Visual Studio 10 -- broken
CMake Error at C:/Program Files (x86)/CMake 2.8/share/cmake-2.8/Modules/CMakeTestCXXCompiler.cmake:45 (MESSAGE):
  The C++ compiler "cl" is not able to compile a simple test program.

  It fails with the following output:

   Change Dir: C:/workspaces/sampleproeject/build/cmake/sampleproeject/CMakeFiles/CMakeTmp

  

  Run Build Command:C:\PROGRA~2\MICROS~1.0\Common7\IDE\devenv.com
  CMAKE_TRY_COMPILE.sln /build Debug /project cmTryCompileExec506066143

  

  Microsoft (R) Visual Studio Version 10.0.30319.1.

  Copyright (C) Microsoft Corp. All rights reserved.

  1>------ Build started: Project: cmTryCompileExec506066143, Configuration:
  Debug Win32 ------

  1> Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 16.00.30319.01
  for 80x86

  1> Copyright (C) Microsoft Corporation. All rights reserved.

  1>

  1> cl /c /Zi /W3 /WX- /Od /Ob0 /Oy- /D WIN32 /D _WINDOWS /D _DEBUG /D
  "CMAKE_INTDIR=\"Debug\"" /D _MBCS /Gm- /EHsc /RTC1 /MDd /GS /fp:precise
  /Zc:wchar_t /Zc:forScope /GR /Fo"cmTryCompileExec506066143.dir\Debug\\"
  /Fd"C:/workspaces/rmhsampleproeject/build/cmake/sampleproeject/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec506066143.pdb"
  /Gd /TP /analyze- /errorReport:prompt
  C:\workspaces\sampleproeject\build\cmake\sampleproeject\CMakeFiles\CMakeTmp\testCXXCompiler.cxx
  /Zm1000

  1>

  1> testCXXCompiler.cxx

  1>LINK : fatal error LNK1201: error writing to program database
  'C:\workspaces\sampleproeject\build\cmake\sampleproeject\CMakeFiles\CMakeTmp\Debug\cmTryCompileExec506066143.pdb';
  check for insufficient disk space, invalid path, or insufficient privilege

  ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped
  ==========

  

  

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:3 (project)

Often times the second time will succeed. Once it has passed once it is generally ok. The problem is that Jenkins is running CI and is not so happy when it fails randomly.


Configuring incomplete, errors occurred!
Steps To ReproduceAttempt to build on Win 7 multiple times. Some number of attempts will fail configure.
Additional Information
Tagsvisual studio, Windows 7
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2012-06-21 18:47michael_cowNew Issue
2012-06-21 18:52michael_cowTag Attached: Windows 7
2012-06-21 18:52michael_cowTag Attached: visual studio
2012-06-21 18:54David ColeNote Added: 0029811
2012-06-21 18:55David ColeNote Added: 0029812
2012-06-21 23:38michael_cowNote Added: 0029813
2012-06-21 23:53michael_cowNote Edited: 0029813bug_revision_view_page.php?bugnote_id=29813#r706
2012-06-21 23:56michael_cowNote Edited: 0029813bug_revision_view_page.php?bugnote_id=29813#r707
2012-06-22 07:02David ColeNote Added: 0029814
2012-08-11 21:42David ColeStatusnew => backlog
2012-08-11 21:42David ColeNote Added: 0030448
2012-11-23 13:07David ColeNote Added: 0031689
2012-11-23 13:07David ColeStatusbacklog => resolved
2012-11-23 13:07David ColeResolutionopen => no change required
2012-11-23 13:07David ColeAssigned To => David Cole
2013-04-17 08:54Robert MaynardNote Added: 0032881
2013-04-17 08:54Robert MaynardStatusresolved => closed

Notes
(0029811)
David Cole   
2012-06-21 18:54   
The version number you've indicated "10.0.30319.1" is Visual Studio 10: the original RTM version.

Consider applying the latest service packs and updates to that machine to get the best Visual Studio behavior.

CMake can never "fix" this issue entirely, because we are not the ones causing a problem with our code... It's pretty much squarely on VS and/or Windows when the linker gives you a "LINK : fatal error LNK1201: error writing to program database" when there's only one process trying to write to it at a time.

I think it may be fixed-er with a newer edition of VS 10.

Let us know if you update and the problem appears to go away. Or especially if it still persists.
(0029812)
David Cole   
2012-06-21 18:55   
Also, please make sure the Windows on that machine is also as up-to-date as possible.
(0029813)
michael_cow   
2012-06-21 23:38   
(edited on: 2012-06-21 23:56)
I updated to:
 Microsoft (R) Visual Studio Version 10.0.40219.1.


The problem still persists, and I was pretty sure it wasn't a Cmake generated issue. Since our team does not get to regulate our development machines, I think your answer is that we will have to deal with MS refusal to fix their product. Can you answer whether this problem exists on Win 2008 Server R2 or Win XP? If these are known good platforms then perhaps we can get our continous integration environment on those machines.

Since were also MSDN subscribers, we'll see what the they say:
http://social.msdn.microsoft.com/Forums/en-US/vcgeneral/thread/a8f08041-ad76-44d5-b4a2-057b427b21cf [^]

Thank you for the quick responses!

-Mike
(0029814)
David Cole   
2012-06-22 07:02   
We've only really seen this and heard reports of this problem on Windows 7.

Switching to XP would be a great way to avoid the issue if your testing can be done on XP...
(0030448)
David Cole   
2012-08-11 21:42   
Sending old, never assigned issues to the backlog.

(The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...)

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
(0031689)
David Cole   
2012-11-23 13:07   
Not a CMake issue... see notes in bug. Resolving as "no change required" on the CMake side... Hopefully Microsoft addresses this in Visual Studio and/or Windows updates.
(0032881)
Robert Maynard   
2013-04-17 08:54   
Closing resolved issues that have not been updated in more than 4 months.