fatal error LNK1104: cannot open file 'KERNEL32.LIB'

fatal error LNK1104: cannot open file 'KERNEL32.LIB'

Hi,

I've been running Intel Visual Fortran Compiler Professional Edition for Windows Version 11.1 Update 2 for some years.

I just upgraded to Intel Visual Fortran Composer XE for Windows 2013 SP1, using it via Microsoft Visual Studio 2010 Ultimate Edition.

I just tried compiling an existing project.

But during linking I get this error:

Error    2     fatal error LNK1104: cannot open file 'KERNEL32.LIB'    LINK    

Regards,
Leigh

11 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

The problem here is that for some reason the linker isn't being supplied the path to the Windows SDK. Normally this is found through the definition of $(WindowsSdkDir) in the list of library directories, but I have seen some customers report this doesn't work.

A solution is to locate the folder on your system (usually in one of the folders under C:\Program Files (x86)\Microsoft SDKs\Windows) and add the full path to Tools > Options > Intel Composer XE > Visual Fortran > Compilers > Libraries.

Steve - Intel Developer Support

Thanks, Steve

I have found the path to the Windows SDK.

But I cannot get to Tools > Options > Intel Composer XE > Visual Fortran > Compilers > Libraries.

I'm in VS2010 Ultimate SP1, here's what I see for Tools > Options:

Regards,

Leigh

That looks like a VB Express display. Please do Help > About, click Copy Info and paste the result into a reply.

Steve - Intel Developer Support

Hi Steve,

Here's the Help | About info.

Cheers,
Leigh

Microsoft Visual Studio 2010
Version 10.0.40219.1 SP1Rel
Microsoft .NET Framework
Version 4.5.50938 SP1Rel

Installed Version: Ultimate

Microsoft Visual Basic 2010   01019-532-2002102-70444
Microsoft Visual Basic 2010

Microsoft Visual C# 2010   01019-532-2002102-70444
Microsoft Visual C# 2010

Microsoft Visual C++ 2010   01019-532-2002102-70444
Microsoft Visual C++ 2010

Microsoft Visual Studio 2010 Architecture and Modeling Tools   01019-532-2002102-70444
Microsoft Visual Studio 2010 Architecture and Modeling Tools
    
UML® and Unified Modeling Language™ are trademarks or registered trademarks of the Object Management Group, Inc. in the United States and other countries.

Microsoft Visual Studio 2010 Code Analysis Spell Checker   01019-532-2002102-70444
Microsoft Visual Studio 2010 Code Analysis Spell Checker

Portions of International CorrectSpell™ spelling correction system © 1993 by Lernout & Hauspie Speech Products N.V. All rights reserved.

The American Heritage® Dictionary of the English Language, Third Edition Copyright © 1992 Houghton Mifflin Company. Electronic version licensed from Lernout & Hauspie Speech Products N.V. All rights reserved.

Microsoft Visual Studio 2010 Team Explorer   01019-532-2002102-70444
Microsoft Visual Studio 2010 Team Explorer

AWS Toolkit for Visual Studio 2010   1.6.3.0
AWS Toolkit for Visual Studio 2010.
Copyright 2011-2013 Amazon.com, Inc. or its affiliates. All Rights Reserved.

This software includes third party software subject to the following copyrights:
- WPF Toolkit for charting and grid controls, Microsoft Public License (Ms-PL)
  [http://wpf.codeplex.com/license]
- Logging from log4net, Apache License
  [http://logging.apache.org/log4net/license.html]
- Putty for PPK to PEM conversion, MIT license
  [http://www.chiark.greenend.org.uk/~sgtatham/putty/licence.html]
- NGit for AWS Elastic Beanstalk incremental push
  [https://github.com/mono/ngit/blob/master/NGit.license.txt]
- NSch dependency for NGit
  [https://github.com/mono/ngit/blob/master/NSch.license.txt]
- Sharpen dependency for NGit
  [https://github.com/mono/ngit/blob/master/Sharpen/AssemblyInfo.cs]
- ICSharpCode.SharpZipLib dependency for NGit
  [http://www.icsharpcode.net/opensource/sharpziplib/]
- Mono.Posix.dll and Mono.Security.dll dependencies for NGit
  [http://mono-project.com/FAQ:_Licensing#Licensing]
- MPFProj for Visual Studio Project Framework
  [http://mpfproj10.codeplex.com/license]
- JSONLint for JSON validation
  [https://github.com/zaach/jsonlint/blob/master/README.md]
- Noesis.Javascript.dll for JSON validation
  [http://javascriptdotnet.codeplex.com/license]

Critical Update for Microsoft Visual Studio 2010 Ultimate - ENU (KB2938807)   KB2938807
This critical update is for Microsoft Visual Studio 2010 Ultimate - ENU.
If you later install a more recent service pack, this critical update will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2938807.

Crystal Reports Templates for Microsoft Visual Studio 2010   
Crystal Reports Templates for Microsoft Visual Studio 2010

Hotfix for Microsoft Visual Studio 2010 Ultimate - ENU (KB2529927)   KB2529927
This hotfix is for Microsoft Visual Studio 2010 Ultimate - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2529927.

Hotfix for Microsoft Visual Studio 2010 Ultimate - ENU (KB2548139)   KB2548139
This hotfix is for Microsoft Visual Studio 2010 Ultimate - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2548139.

Hotfix for Microsoft Visual Studio 2010 Ultimate - ENU (KB2549864)   KB2549864
This hotfix is for Microsoft Visual Studio 2010 Ultimate - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2549864.

Hotfix for Microsoft Visual Studio 2010 Ultimate - ENU (KB2565057)   KB2565057
This hotfix is for Microsoft Visual Studio 2010 Ultimate - ENU.
If you later install a more recent service pack, this hotfix will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2565057.

Intel(R) Visual Fortran     Package ID: w_fcompxe_2013_sp1.3.202
Intel(R) Visual Fortran Composer XE 2013 SP1 Update 3 Integration for Microsoft Visual Studio* 2010, 14.0.0092.2010, Copyright (C) 2002-2014 Intel Corporation
* Other names and brands may be claimed as the property of others.

Microsoft Visual Studio 2010 Ultimate - ENU Service Pack 1 (KB983509)   KB983509
This service pack is for Microsoft Visual Studio 2010 Ultimate - ENU.
If you later install a more recent service pack, this service pack will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/983509.

Security Update for Microsoft Visual Studio 2010 Ultimate - ENU (KB2645410)   KB2645410
This security update is for Microsoft Visual Studio 2010 Ultimate - ENU.
If you later install a more recent service pack, this security update will be uninstalled automatically.
For more information, visit http://support.microsoft.com/kb/2645410.

VSdocman
Code commenter and documentation generator. http://www.helixoft.com. Copyright (c) Helixoft

Well, that's interesting. You should be seeing a LOT more entries under Tools > Options. Try a reboot and see if that changes.

Steve - Intel Developer Support

Steve:

No changes to Tools > Options after reboot.

If it's any consolation, New Project menu shows all the IVF options...

Leigh

At this point I suggest uninstalling Fortran and VS and reinstalling both (VS first). Something is very wrong with your VS install.

Steve - Intel Developer Support

Thanks, Steve,

I gave up on trying to get Composer XE working with Visual Studio 2010.

I've now acquired Visual Studio 2010 - I'll leave my story for another post.

Sorry, I meant to say: "'ve now acquired Visual Studio 2013.

Just for the record, here's what I had to do to get it working with Composer XE:

error rc.exe not found

fixed by adding C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Bin to Tools > Options > Intel Composer XE > Compilers > Executables.

fatal error LNK1104: cannot open file 'KERNEL32.LIB'

fixed by adding C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Lib to Tools > Options > Intel Composer XE > Compilers > Libraries.

 

Yes, rc.exe not found needs a change to the executable path. In most cases this works automatically, but sometimes it doesn't and it can be frustrating to figure out why.

Steve - Intel Developer Support

Leave a Comment

Please sign in to add a comment. Not a member? Join today