[CMake] Re: CMAKE_MAKE_PROGRAM is not set

[Martin Baumann]

Hi,

don't have the Modules installed on the system.

I checked the Modules/CMakeUnixFindMake.cmake but this didn't help me.

The first message is:

 The C compiler "gcc" is not able to compile a simple test program.
 It fails with the following output:
  /lvdraid/user/ry149/local/bin/cmake -H/lvdraid/user/ry149/local/src/cmake/cmake-2.2.3/CMakeTmp
 -B/lvdraid/user/ry149/local/src/cmake/cmake-2.2.3/CMakeTmp --check-build-system CMakeFiles/Makefile.cmake 0
 /usr/freeware/bin/gmake -f CMakeFiles/Makefile2 cmTryCompileExec

What is this message trying to tell me? Ok, the test program is not 
compiled, but what is the error?
I need to know something about the error. Else this message has no use 
at all!

The system now has a gcc-3.3 compiler installed. I checked the gcc 
manual and did some changes to system variables:

  CC=mips-sgi-irix6.5-gcc
  CFLAGS='-O3 -fomit-frame-pointer'
  CPPFLAGS='-I/usr/freeware/include -I/usr/local/include -I/usr/machine/include -I/usr/segment/include -march=mips3'
  CXX=mips-sgi-irix6.5-g++
  CXXFLAGS='-O3 -fomit-frame-pointer'
  GCC=mips-sgi-irix6.5-gcc
  GCFLAGS='-O3 -fomit-frame-pointer'
  GCPPFLAGS='-I/usr/freeware/include -I/usr/local/include -I/usr/machine/include -I/usr/segment/include -march=mips3'
  GCXX=mips-sgi-irix6.5-g++
  GCXXFLAGS='-O3 -fomit-frame-pointer'
  GLDFLAGS='-L/usr/freeware/lib32 -L/usr/lib32 -L/usr/machine/lib32 -Wl,-rpat'
  LDFLAGS='-L/usr/freeware/lib32 -L/usr/lib32 -L/usr/machine/lib32 -Wl,-rpat'

When Cmake is started it checks for compilers. Automatically a cc 
compiler is found, not mips-sgi-irix6.5-gcc as defined in
the CC variable is taken. Why? In the manual of CMake is written, that 
system variables are used as default values.

I changed the CMAKE_XXX variables within CMake to the mentioned values. 
And this is the output at the moment when
I try to configure the source of the latest CMake source:

 The C compiler "gcc" is not able to compile a simple test program.
 It fails with the following output:
  /lvdraid/user/ry149/local/bin/cmake -H/lvdraid/user/ry149/local/src/cmake/cmake-2.2.3/CMakeTmp
 -B/lvdraid/user/ry149/local/src/cmake/cmake-2.2.3/CMakeTmp --check-build-system CMakeFiles/Makefile.cmake 0
 /usr/freeware/bin/gmake -f CMakeFiles/Makefile2 cmTryCompileExec
 gmake[1]: Entering directory `/lvdraid/user/ry149/local/src/cmake/cmake-2.2.3/CMakeTmp'       
 /lvdraid/user/ry149/local/bin/cmake -H/lvdraid/user/ry149/local/src/cmake/cmake-2.2.3/CMakeTmp
 -B/lvdraid/user/ry149/local/src/cmake/cmake-2.2.3/CMakeTmp --check-build-system CMakeFiles/Makefile.cmake 0
 /usr/freeware/bin/gmake -f CMakeFiles/Makefile2 CMakeFiles/cmTryCompileExec.dir/all    
 gmake[2]: Entering directory `/lvdraid/user/ry149/local/src/cmake/cmake-2.2.3/CMakeTmp'
 /usr/freeware/bin/gmake -f CMakeFiles/cmTryCompileExec.dir/build.make CMakeFiles/cmTryCompileExec.dir/depend
 gmake[3]: Entering directory `/lvdraid/user/ry149/local/src/cmake/cmake-2.2.3/CMakeTmp'
 Scanning dependencies of target cmTryCompileExec
 /lvdraid/user/ry149/local/bin/cmake -E cmake_depends  "Unix Makefiles" /lvdraid/user/ry149/local/src/cmake/cmake-2.2.3/CMakeTmp
 /lvdraid/user/ry149/local/src/cmake/cmake-2.2.3/CMakeTmp
 /lvdraid/user/ry149/local/src/cmake/cmake-2.2.3/CMakeTmp/CMakeFiles/cmTryCompileExec.dir/DependInfo.cmake
 gmake[3]: Leaving directory `/lvdraid/user/ry149/local/src/cmake/cmake-2.2.3/CMakeTmp'
 /usr/freeware/bin/gmake -f CMakeFiles/cmTryCompileExec.dir/build.make CMakeFiles/cmTryCompileExec.dir/build
 gmake[3]: Entering directory `/lvdraid/user/ry149/local/src/cmake/cmake-2.2.3/CMakeTmp'
 Building C object CMakeFiles/cmTryCompileExec.dir/testCCompiler.o
 gcc -O3 -fomit-frame-pointer -64 -O3 -fomit-frame-pointer     -o CMakeFiles/cmTryCompileExec.dir/testCCompiler.o   -c
 /lvdraid/user/ry149/local/src/cmake/cmake-2.2.3/CMakeTmp/testCCompiler.c
 gcc: unrecognized option `-64'       
 Linking C executable cmTryCompileExec
 /lvdraid/user/ry149/local/bin/cmake -E remove -f cmTryCompileExec
 gcc -O3 -fomit-frame-pointer -64 -O3 -fomit-frame-pointer    -fPIC -64;-L/usr/freeware/lib32 -L/usr/lib32 -L/usr/machine/lib32 -Wl,-rpat
 "CMakeFiles/cmTryCompileExec.dir/testCCompiler.o"   -o cmTryCompileExec
 gcc: unrecognized option `-64'
 gcc: unrecognized option `-64'
 gcc: no input files
 /bin/sh: -L/usr/freeware/lib32:  not found
 gmake[3]: *** [cmTryCompileExec] Error 127
 gmake[3]: Leaving directory `/lvdraid/user/ry149/local/src/cmake/cmake-2.2.3/CMakeTmp'
 gmake[2]: *** [CMakeFiles/cmTryCompileExec.dir/all] Error 2
 gmake[2]: Leaving directory `/lvdraid/user/ry149/local/src/cmake/cmake-2.2.3/CMakeTmp'
 gmake[1]: *** [CMakeFiles/cmTryCompileExec.dir/rule] Error 2
 gmake[1]: Leaving directory `/lvdraid/user/ry149/local/src/cmake/cmake-2.2.3/CMakeTmp'
 gmake: *** [cmTryCompileExec] Error 2
 
 
 CMake will not be able to correctly generate this project.
 
 CMake Error: You have requested backwards compatibility with CMake version 1.2 or earlier. This version of CMake only supports backwards
 compatibility with CMake 1.4 or later. For compatibility with 1.2 or earlier please use CMake 2.0

I have no idea where the '-64' parameters come from! I did not set any 
'-64' in any system variable! This is some confusing to me.
Does a precompiled verison of VTK-5.0 exist for a SGI Onyx2 6.5 machine 
that can be downloaded?

Thanks, M.B.





William A. Hoffman schrieb:

>At 06:56 AM 3/10/2006, Martin Baumann wrote:
>  
>
>>Hi,
>>
>>on this machine are different programming environments.
>>
>>Here are my environment variables that CMake uses:
>>
>>CC=gcc
>>CFLAGS='-O3 -fomit-frame-pointer'
>>CXX=g++
>>CXXFLAGS='-O3 -fomit-frame-pointer'
>>LDFLAGS='-L/usr/local/lib32 -L/usr/machine/lib32 -L/usr/segment/lib32 -Wl,-rpath
>>
>>is there a list which environment variables are used to set CMake-variables?
>>
>>    
>>
>>>Questions:
>>>1. What version of cmake?
>>>      
>>>
>>CMake Version 2.2 - patch 3
>>
>>    
>>
>>>2. How was cmake built/installed
>>>      
>>>
>>I copied the binaries on the system which I downloaded at the cmake website)
>>
>>    
>>
>>>3. Is either make or gmake in your path?  (which make; which gmake)
>>>      
>>>
>>yes, both. 
>>
>>    
>>
>>>4. Are g++/gcc in your PATH?
>>>      
>>>
>>yes, both
>>
>>    
>>
>>>5. What command line are you using to run CMake?
>>>      
>>>
>>bash
>>
>>    
>>
>>>-Bill
>>>      
>>>
>I am not sure what is wrong. The way it works is the file
>Modules/CMakeUnixFindMake.cmake is read to find the make program.
>You could try putting some MESSAGE commands in there to print out things
>like $ENV{PATH}.  Basically it just looks for gmake or make in the PATH.
>For some reason in the environment you are running it is not finding them.
>It is also not finding the c or cxx compiler.    It sounds like there
>is a problem in your environment but I am not sure what it is.
>
>-Bill
>
>
>  
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://public.kitware.com/pipermail/cmake/attachments/20060312/dd2f38e2/attachment.html