MantisBT - CMake
View Issue Details
0012578CMakeCMakepublic2011-11-14 14:572016-06-10 14:31
Jean-Christophe Houde 
Kitware Robot 
normalminoralways
closedmoved 
Xcode 4.0OSX10.6
CMake 2.8.6 
 
0012578: Parenthesis in source or build path causes Cmake-gui to fail the compiler tests
When using the Cmake gui, specifying a source or build path with an opening parenthesis included causes the compiler tests to fail. Using the same path without a parenthesis works.

1. Create a project directory like the following
   /project (space)
      /src
      /build
2. Start Cmake-gui.
3. Use the absolute path of the "src" directory as the "Where is the source code" variable.
4. Use the absolute path of the "build" directory as the "Where to build the binaries" variable.
5. Use any basic CMakeList file.
6. Try to configure the project.

It now should fail at the

Check for working C compiler using: Xcode
Check for working C compiler using: Xcode -- broken

step.
The error message is

CMake Error at /Applications/CMake 2.8-6.app/Contents/share/cmake-2.8/Modules/CMakeTestCCompiler.cmake:52 (MESSAGE):
  The C compiler "/usr/bin/gcc" is not able to compile a simple test program.

  It fails with the following output:

   Change Dir: /Users/houj2901/Documents/Recherche/Fibernavigator/trunk (test)/build-code/CMakeFiles/CMakeTmp

  
  Run Build Command:/Applications/CMake\ 2.8-6.app/Contents/bin/cmakexbuild
  -project CMAKE_TRY_COMPILE.xcodeproj build -target cmTryCompileExec
  -configuration Debug

  === BUILD NATIVE TARGET cmTryCompileExec OF PROJECT CMAKE_TRY_COMPILE WITH
  CONFIGURATION Debug ===

  Check dependencies

  CompileC
  CMAKE_TRY_COMPILE.build/Debug/cmTryCompileExec.build/Objects-normal/x86_64/testCCompiler.o
  testCCompiler.c normal x86_64 c com.apple.compilers.llvmgcc42

      cd "/Users/houj2901/Documents/Recherche/Fibernavigator/trunk (test)/build-code/CMakeFiles/CMakeTmp"
      /Developer/usr/bin/llvm-gcc-4.2 -x c -arch x86_64 -fmessage-length=0 -pipe -Wno-trigraphs -fpascal-strings -O0 -mdynamic-no-pic -DCMAKE_INTDIR="Debug" -isysroot /Developer/SDKs/MacOSX10.6.sdk -fasm-blocks -mmacosx-version-min=10.6 -gdwarf-2 "-I/Users/houj2901/Documents/Recherche/Fibernavigator/trunk (test)/build-code/CMakeFiles/CMakeTmp/Debug/include" "-I/Users/houj2901/Documents/Recherche/Fibernavigator/trunk (test)/build-code/CMakeFiles/CMakeTmp/CMAKE_TRY_COMPILE.build/Debug/cmTryCompileExec.build/DerivedSources/x86_64" "-I/Users/houj2901/Documents/Recherche/Fibernavigator/trunk (test)/build-code/CMakeFiles/CMakeTmp/CMAKE_TRY** BUILD FAILED **

  

  

  The following build commands failed:

      PhaseScriptExecution "CMake PostBuild Rules"
  CMAKE_TRY_COMPILE.build/Debug/cmTryCompileExec.build/Script-779D508F174847D09D396C67.sh


  (1 failure)
No tags attached.
Issue History
2011-11-14 14:57Jean-Christophe HoudeNew Issue
2012-08-11 21:09David ColeStatusnew => backlog
2012-08-11 21:09David ColeNote Added: 0030329
2016-06-10 14:28Kitware RobotNote Added: 0041933
2016-06-10 14:28Kitware RobotStatusbacklog => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0030329)
David Cole   
2012-08-11 21:09   
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.
(0041933)
Kitware Robot   
2016-06-10 14:28   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.