error #11018: Cannot open C:\Visual Studio 2008\Projects\TSEx\L

Frank_M · ‎11-17-2010

The error #11018: Cannot open C:\\Visual Studio 2008\\Projects\\TSEx\\Lib1\\Debug\\Lib1 has afflictted ALL my fortran libriaries when linking with intel C++ since the installation of V12.

Obviously I've got something configured wrong.

How do I set the properties of the fortran & c++ projects to make the magic work?

note: I also get the above error with the sample c++ calls fortran in the included examples.

Thanks.

Steven_L_Intel1 · ‎11-17-2010

It sounds as if the Fortran integration is not installed properly. Please do Help > About in VS, click Copy Info and paste the results into a reply here.

You can also try running th repair tool in this article.

Frank_M · ‎11-18-2010

I tried the three steps in the article and the Integration tool. No success. Here is the info.

Microsoft Visual Studio 2008
Version 9.0.30729.1 SP
Microsoft .NET Framework
Version 3.5 SP1

Installed Edition: Standard

Microsoft Visual Basic 2008 Microsoft Visual Basic 2008

Microsoft Visual C# 2008
Microsoft Visual C# 2008

Microsoft Visual C++ 2008
Microsoft Visual C++ 2008

Microsoft Visual F#
Microsoft Visual F# for Visual Studio 2008

Microsoft Visual Web Developer 2008
Microsoft Visual Web Developer 2008

Intel Visual Fortran
Intel Visual Fortran Composer XE 2011 Integration for Microsoft Visual Studio* 2008, 12.0.3470.2008, Copyright (C) 2002-2010 Intel Corporation
* Other names and brands may be claimed as the property of others.

Intel Parallel Advisor 2011 Update 1
Intel Parallel Advisor 2011 Update 1, (build 124239), Copyright 2009-2010 Intel Corporation. All rights reserved.

Intel Parallel Amplifier 2011
Intel Parallel Amplifier 2011, (build 114808), Copyright 2008-2010 Intel Corporation. All rights reserved.

Intel Parallel Composer 2011
Intel Parallel Composer 2011 (Package ID: composer_2011.063), Copyright 2002-2010 Intel Corporation

This product includes software developed at The Apache Software Foundation (http://www.apache.org/).

Portions of this software were originally based on the following:
- software copyright (c) 1999, IBM Corporation., http://www.ibm.com.
- software copyright (c) 1999, Sun Microsystems., http://www.sun.com.
- the W3C consortium (http://www.w3c.org) ,
- the SAX project (http://www.saxproject.org)
- voluntary contributions made by Paul Eng on behalf of the Apache Software Foundation that were originally developed at iClick, Inc., software copyright (c) 1999.

This product includes software developed by the MX4J project (http://mx4j.sourceforge.net).

This product includes software from the book "Linux Device Drivers" by Alessandro Rubini and Jonathan Corbet, published by O'Reilly & Associates.

This product includes hashtab.c. Bob Jenkins, 1996.

Intel Parallel Inspector 2011
Intel Parallel Inspector 2011, (build 111926), Copyright 2008-2010 Intel Corporation. All rights reserved.

Steven_L_Intel1 · ‎11-18-2010

Please report this problem to Intel Premier Support. I am traveling this week and won't be able to provide the detailed help you need.

Frank_M · ‎11-23-2010

A week ago sunday was the last time I was able to get Intel Fortran to compile and link. After the installation of v12 the fortran compiler would no longer output anykind of file. The only advice I've gotten from Premier Support is to not put fortran projects in a Read Only folder. Unfortunately all folders in windows XP are by default Read Only. ( http://support.microsoft.com/kb/326549) The attrib trick mentioned in the link has no effect on this problem. Neither does the microsoft windows fixit tool or the intel sv2008 fortran integration repair tool.

In addition the Intel C++ compiler is just happy to output files to the SV2008 projects directory.

I've tried removing v12 and reinstalling v11.1.067 but Fortan is still not working. What ever the instalation of v12 did, I don't know how to undo it. Any advice would be greatly appreciated.

Jugoslav_Dujic · ‎11-23-2010

Quoting Frank_M

The error #11018: Cannot open C:\Visual Studio 2008\Projects\TSEx\Lib1\Debug\Lib1 has afflictted ALL my fortran libriaries when linking with intel C++ since the installation of V12.

Obviously I've got something configured wrong.

How do I set the properties of the fortran & c++ projects to make the magic work?

note: I also get the above error with the sample c++ calls fortran in the included examples.

Thanks.

There is a bug, apparently in Fortran VS integration in VS2010, that I stumbled upon. I haven't came yet to report it, because I have to find some time to reduce the solution to a simple example. It is not reproducible with any set of project settings, but here are the basic conditions:

1) You have a mixture of C++ and Fortran projects in the solution. Fortran projects depend on C++ projects (which are dlls or static libs). Let's call them CProj and FProj.

2) You use solution dependencies (and set "Link library dependencies" to yes) to tie them together (FProj depends on CProj). I think that CProj also has to have further dependencies for the bug to emerge.

3) When linking FProj, you get one of the errors "Cannot open D:\PathToFProj\FProj.lib", or "Cannot open C:\Program Files\Lib\FProj.lib" (the latter directory does not even exist). When examining the BuildLog.htm, one can see that the linker is given as input the library it needs to create (apparently, by the integration).

The workaround is to set "Link library dependencies" in FProj to "no", and specify the CProj.lib explicitly as the Linker/Input/Additional dependencies.

Update: Now reported as issue 611109.

Frank_M · ‎11-24-2010

Thanks for the help. I did try your solution and got nowhere. My problem is a little more basic. The fortran compiler will not output anything. I took the basics full debug , no optimazation, NQueens example that caomes with every compiler and tried to get Intel fortran to do something with it. NOTHING. It claims it is compiled but outputs no files.

Steven_L_Intel1 · ‎11-24-2010

It is not true that "all folders in XP are read-only". The admonition about folders applies to Windows 7 and Windows Vista where folders under Program Files are not writable except with Administrator privilege. If you build in a folder not under Program Files it should be fine, and XP doesn't have this issue.

Please attach the buildlog.htm from a failed build.

Frank_M · ‎11-24-2010

I just finished a restore from external backup of all things intel compiler and studio vision 2008 related (except the license files) and am back to where I was before upgrading to v12. If I work up the courage I may attempt to uninstall v11.1.067 and install v12. If I do and fortran fails to compile I will certainly post the build file.