[CMake] Problem running cmake 2.8.4 on Ubuntu 10.04

[pellegrini]

thanks Alan for your help,

indeed 'ifort_release_win' stands for a build with ifort using  a 
graphical user interface. I just realize it was certainly not the best 
name for my build directory (ifort_release_gui would have led to less 
confusion I guess).

In the meantime, I found that cmake 2.8.0, 2.8.1, 2.82 works and 
starting from 2.8.3 the ABI steps fails. I may be wrong but it seems to 
be related to some "addings" in the version 2.8.3 and 2.8.4.

Eric

Alan W. Irwin a écrit :
> On 2011-07-06 11:36+0200 pellegrini wrote:
>
>> Hello everybody,
>>
>> I have troubles running cmake 2.8.4 on my ubuntu 10.04 machine.
>> I must use that version because of a bug fix concerning rc files.
>>
>> When running cmake, I get the following error message:
>>
>> ##################################################################
>>
>> -- The Fortran compiler identification is Intel
>> -- Check for working Fortran compiler: /home/pellegrini/bin/ifort
>> -- Check for working Fortran compiler: /home/pellegrini/bin/ifort  -- 
>> works
>> -- Detecting Fortran compiler ABI info
>> CMake Error at 
>> /home/pellegrini/Downloads/cmake-2.8.4-Linux-i386/share/cmake-2.8/Modules/CMakeDetermineCompilerABI.cmake:31 
>> (TRY_COMPILE):
>> Cannot copy output executable
>>
>>   ''
>>
>> to destination specified by COPY_FILE:
>>
>>   
>> '/home/pellegrini/Diffraction/crysfml/build/ifort_release_win/CMakeFiles/CMakeDetermineCompilerABI_Fortran.bin' 
>>
>>
>> Unable to find the executable at any of:
>>
>>   
>> /home/pellegrini/Diffraction/crysfml/build/ifort_release_win/CMakeFiles/CMakeTmp/cmTryCompileExec 
>>
>>   
>> /home/pellegrini/Diffraction/crysfml/build/ifort_release_win/CMakeFiles/CMakeTmp/Debug/cmTryCompileExec 
>>
>>   
>> /home/pellegrini/Diffraction/crysfml/build/ifort_release_win/CMakeFiles/CMakeTmp/Development/cmTryCompileExec 
>>
>>
>> Call Stack (most recent call first):
>> /home/pellegrini/Downloads/cmake-2.8.4-Linux-i386/share/cmake-2.8/Modules/CMakeTestFortranCompiler.cmake:59 
>> (CMAKE_DETERMINE_COMPILER_ABI)
>> CMakeLists.txt:73 (PROJECT)
>>
>>
>> -- Detecting Fortran compiler ABI info - done
>> CMake Error at 
>> /home/pellegrini/Downloads/cmake-2.8.4-Linux-i386/share/cmake-2.8/Modules/CMakeDetermineCompilerABI.cmake:48 
>> (FILE):
>> file STRINGS file
>> "/home/pellegrini/Diffraction/crysfml/build/ifort_release_win/CMakeFiles/CMakeDetermineCompilerABI_Fortran.bin" 
>>
>> cannot be read.
>> Call Stack (most recent call first):
>> /home/pellegrini/Downloads/cmake-2.8.4-Linux-i386/share/cmake-2.8/Modules/CMakeTestFortranCompiler.cmake:59 
>> (CMAKE_DETERMINE_COMPILER_ABI)
>> CMakeLists.txt:73 (PROJECT)
>>
>>
>> -- Checking whether /home/pellegrini/bin/ifort supports Fortran 90
>> -- Checking whether /home/pellegrini/bin/ifort supports Fortran 90 -- 
>> yes
>> -- Configuring incomplete, errors occurred!
>>
>> ##################################################################
>>
>> The same settings work well on my windows machine ...
>>
>> would you have any idea ?
>
> Hi Eric:
>
> I have no experience with ifort, but I do have just a quick thought
> which may or may not have anything to do with the Linux build errors
> you are seeing.
>
> I noticed "ifort_release_win" in your above error messages.  Just in
> case that "win" has anything to do with your Windows build, you must
> do your Linux build starting with a completely empty build tree. For
> example, stale Windows build results in that tree would completely
> mess up your Linux build.  Even if you confine your builds to one
> platform, if things go wrong (like above) it is always a good idea to 
> start over
> with a fresh build starting with an empty build tree in case your
> build is getting messed up by stale build results on the same
> platform.  Of course, none of these comments are relevant if you
> get the above error messages starting with an empty build tree.
>
> Alan
> __________________________
> Alan W. Irwin
>
> Astronomical research affiliation with Department of Physics and 
> Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
>
> Programming affiliations with the FreeEOS equation-of-state 
> implementation
> for stellar interiors (freeeos.sf.net); PLplot scientific plotting 
> software
> package (plplot.org); the libLASi project (unifont.org/lasi); the 
> Loads of
> Linux Links project (loll.sf.net); and the Linux Brochure Project
> (lbproject.sf.net).
> __________________________
>
> Linux-powered Science
> __________________________


-- 
Eric Pellegrini
Calcul Scientifique
Institut Laue-Langevin
Grenoble, France