[CMake] Trying to use the latest release of Intel Fortran 2011 (update 9) with cmake...

Fri Apr 13 07:27:17 EDT 2012

I tried that, no joy.  Here is the error it spits out:

Check for working C compiler using: Visual Studio 8 2005

Check for working C compiler using: Visual Studio 8 2005 -- works

Detecting C compiler ABI info

Detecting C compiler ABI info - done

Check for working CXX compiler using: Visual Studio 8 2005

Check for working CXX compiler using: Visual Studio 8 2005 -- works

Detecting CXX compiler ABI info

Detecting CXX compiler ABI info - done

Check for working Fortran compiler using: Visual Studio 8 2005

Check for working Fortran compiler using: Visual Studio 8 2005 -- broken

CMake Error at E:/Program Files/CMake 
2.8/share/cmake-2.8/Modules/CMakeTestFortranCompiler.cmake:40 (MESSAGE):

The Fortran compiler "ifort" is not able to compile a simple test program.

It fails with the following output:

Change Dir: E:/Users/Administrator/Documents/My 
SVN/ESPlanner_Computation_Engine.HEAD/ESPlanner 
Executables-cmake/CMakeFiles/CMakeTmp

Run Build Command:E:\PROGRA~1\MICROS~1\Common7\IDE\devenv.com

CMAKE_TRY_COMPILE.sln /build Debug /project cmTryCompileExec

Microsoft (R) Visual Studio Version 8.0.50727.867.

One or more projects in the solution could not be loaded for the following

reason(s):

The application for the project is not installed.

These projects will be labeled as unavailable in Solution Explorer. Expand

the project node to show the reason the project could not be loaded.

Invalid project

Use:

devenv [solutionfile | projectfile | anyfile.ext] [switches]

The first argument for devenv is usually a solution file or project file.

You can also use any other file as the first argument if you want to have

the

file open automatically in an editor. When you enter a project file, the

IDE

looks for an .sln file with the same base name as the project file in the

parent directory for the project file. If no such .sln file exists, then

the

IDE looks for a single .sln file that references the project. If no such

single

.sln file exists, then the IDE creates an unsaved solution with a default

.sln

file name that has the same base name as the project file.

Command line builds:

devenv solutionfile.sln /build solutionconfig [ /project projectnameorfile

[ /projectconfig name ] ]

Available command line switches:

/Build Builds the solution or project with the specified solution

configuration. For example "Debug". If multiple platforms

are possible, the configuration name must be enclosed in quotes

and contain platform name. For example: "Debug|Win32".

/Clean Deletes build outputs.

/Command Starts the IDE and executes the command.

/Deploy Builds and then deploys the specified build configuration.

/Edit Opens the specified files in a running instance of this

application. If there are no running instances, it will

start a new instance with a simplified window layout.

/LCID Sets the default language in the IDE for the UI.

/Log Logs IDE activity to the specified file for troubleshooting.

/NoVSIP Disables the VSIP developer's license key for VSIP testing.

/Out Appends the build log to a specified file.

/Project Specifies the project to build, clean, or deploy.

Must be used with /Build, /Rebuild, /Clean, or /Deploy.

/ProjectConfig Overrides the project configuration specified in the

solution

configuration. For example "Debug". If multiple platforms are

possible, the configuration name must be enclosed in quotes

and contain platform name. For example: "Debug|Win32".

Must be used with /Project.

/Rebuild Cleans and then builds the solution or project with the

specified configuration.

/ResetAddin Removes commands and command UI associated with the specified

Add-in.

/ResetSettings Restores the IDE's default settings, optionally resets to

the specified VSSettings file.

/ResetSkipPkgs Clears all SkipLoading tags added to VSPackages.

/Run Compiles and runs the specified solution.

/RunExit Compiles and runs the specified solution then closes the IDE.

/SafeMode Launches the IDE in safe mode loading minimal windows.

/Upgrade Upgrades the project or the solution and all projects in it.

A backup of these files will be created as appropriate. Please

see Help on 'Visual Studio Conversion Wizard' for more

information on the backup process.

Product-specific switches:

/debugexe Open the specified executable to be debugged. The

remainder of the command line is passed to this

executable as its arguments.

/useenv Use PATH, INCLUDE, LIBPATH, and LIB environment variables

instead of IDE paths for VC++ builds.

To attach the debugger from the command line, use:

VsJITDebugger.exe -p <pid>

CMake will not be able to correctly generate this project.

Call Stack (most recent call first):

CMakeLists.txt:119 (enable_language)

Configuring incomplete, errors occurred!

On 4/12/12 2:57 PM, Tim Gallagher wrote:
> Did you try wiping out the existing build and starting it from scratch?
>
> It sounds like there are still some module files floating around from the previous build with the previous Fortran version.
>
> Tim
>
> ----- Original Message -----
> From: "Dick Munroe"<munroe at csworks.com>
> To: cmake at cmake.org
> Sent: Thursday, April 12, 2012 2:48:00 PM
> Subject: [CMake] Trying to use the latest release of Intel Fortran 2011 (update 9) with cmake...
>
> on windoze.  I installed the compiler, uninstalled the previous update
> (2), and fired up CMake at which point I can no longer build solutions
> with CMake.  Every time I try, I get a "this solution was built with an
> earlier version of fortran" or words to that effect.
>
> Any clues what the problem might be?
>
> Best,
>
> Dick Munroe
>
> --
>
> 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://www.cmake.org/mailman/listinfo/cmake
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20120413/ca8ae482/attachment-0001.htm>