Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
28560 Discussions

ipo: error #11018: Cannot open C:\Program leading to fatal error LNK1107

Ashby__Joe
Beginner
2,843 Views

Hi, 

So I loaded up visual studio 2012 and created a new Fortran console application with the example code. I tried to build it just to check everything was working and I get this in the build: 

1>------ Build started: Project: Console1, Configuration: Debug Win32 ------
1>Linking...
1>ipo: error #11018: Cannot open C:\Program
1>C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\bin\amd64\link.exe : fatal error LNK1107: invalid or corrupt file: cannot read at 0x2E8
1>
1>Build log written to  "file://c:\users\XXXXXX\documents\visual studio 2012\Projects\Console1\Console1\Debug\BuildLog.htm"
1>Console1 - 2 error(s), 0 warning(s)
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
buildlog attached. 

Can anyone please help? It looks like I have a path somewhere that's not quoted but I don't know where to find it. 

Visual Studio 2012

Intel Composer 2013 SP1

 

0 Kudos
16 Replies
mecej4
Honored Contributor III
2,843 Views

Please attach the build log. You may have an improper path in %LIB% or a related environment variable.

0 Kudos
Ashby__Joe
Beginner
2,843 Views

Hi mecej4, buildlog attached as a .txt here. Where could I look to check the paths?

 

0 Kudos
mecej4
Honored Contributor III
2,843 Views

I don't understand why IPO is being used in a debug build, and the build log that you provided does not show any information on the compilation phases, since it shows only information about the linking stage. Please try "clean" and "build".

0 Kudos
Ashby__Joe
Beginner
2,843 Views

Sorry for the delay, I did the clean build and have attached the new log

 

 

0 Kudos
Steve_Lionel
Honored Contributor III
2,843 Views

You're building a 32-bit program but invoking the 64-bit linker. That's not right.

In VS, select Tools > Options > Intel Compilers and Tools > Visual Fortran > Compilers. With the Win32 tab active, click Reset... Click on the x64 tab and click Reset... Click OK.

0 Kudos
Ashby__Joe
Beginner
2,843 Views

Hi Steve,

That did not seem to change anything, it is still calling the 64-bit version. Maybe my PATH is wrong in the Windows environment variables?

0 Kudos
Steve_Lionel
Honored Contributor III
2,843 Views

Go back to that Compilers tab. Click on the ... next to "Executables". Copy the text that is displayed and paste it into a reply here.

Next, open a command prompt window (not a Fortran build environment window) - Press Windows-X and select Command Line (or PowerShell if it appears). Set default (cd) to a writeable folder (not under Windows or Program Files) and type:

set path > path.txt

Attach the path.txt to your reply here.

0 Kudos
Ashby__Joe
Beginner
2,843 Views

> Go back to that Compilers tab. Click on the ... next to "Executables". Copy the text that is displayed and paste it into a reply here.

$(IFortInstallDir)bin\ia32;$(VSInstallDir)Common7\IDE;$(VCInstallDir)BIN;$(VSInstallDir)Common7\Tools;$(VSInstallDir)Common7\Tools\bin;$(FrameworkDir)$(FrameworkVersion);$(WindowsSdkDir)bin\x86;$(PATH)

path.txt attached

 

0 Kudos
mecej4
Honored Contributor III
2,843 Views

I see the following potential problems in your %PATH%:

"C:\Program Files (x86)\Intel\Composer XE 2013 SP1\bin\intel64" appears twice.

"C:\Program Files (x86)\Intel\Composer XE 2013 SP1\bin" appears once; this directory contains only batch files and subdirectories.

"C:\Program Files (x86)\Intel\Composer XE 2013 SP1\bin\ia32" contains tools needed for 32-bit compilations, but is not included in %PATH%.

0 Kudos
Ashby__Joe
Beginner
2,843 Views

I have added "C:\Program Files (x86)\Intel\Composer XE 2013 SP1\bin\ia32", and removed "C:\Program Files (x86)\Intel\Composer XE 2013 SP1\bin", however the problem is still occuring.

 

0 Kudos
Steve_Lionel
Honored Contributor III
2,843 Views

You did the "set path" from a command prompt that was NOT a "Fortran build environment" prompt, as I requested? You should not have any of the \bin folders in PATH. How did they get there?

0 Kudos
Ashby__Joe
Beginner
2,843 Views

Yes I did. I added those folders as I was told it was necessary for the integration of ifort and link with my finite element modelling software ABAQUS which uses fortran for it's user subroutines.

0 Kudos
Steve_Lionel
Honored Contributor III
2,843 Views

Take them out - they don't belong there. The better choice is to use one of the "Fortran build environment" shortcuts or make your own with a call to ifortvars.bat with appropriate options. What you have done is subverted the way the VS integration selects which executables to use.

0 Kudos
Ashby__Joe
Beginner
2,843 Views

Okay, I have removed all of these from the Path, however my problem is still the same. Do I need to reconfigure/reinstall anything?

0 Kudos
Steve_Lionel
Honored Contributor III
2,843 Views

Please reboot first. I would also suggest that you set Tools > Options > Intel Compilers and Tools > Visual Fortran > General > Show Environment in Log to True, do a rebuild, ZIP the buildlog.htm and attach the zip to a reply here.

0 Kudos
Ashby__Joe
Beginner
2,843 Views

Hi Steve (and mecej4),

Thank you so much for your help, it was indeed just the PATH that was messing things up and I have got everything working, including the ABAQUS integration.

Thanks again,

Joe

0 Kudos
Reply