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

unresolved external symbol _for_stop_core_quiet (continuation of 1237762)

OptiAndrew
Beginner
‎02-26-2021 06:16 AM
12,621 Views
Solved Jump to solution

I must preface that this is also a BIT of a Visual Studio question, but discussion #1237762 says to make sure you're using the same version of C++ compilers for everything.

First, I'm pretty sure that I am as I have all of my code contained in the same project (one master project with several sub projects building static LIBs) and I still get "unresolved external symbol _for_stop_core_quiet referenced in function _INTLAS" (INTLAS is a Fortran routine)

Second, where do you even check what versions of compilers you are using for a specific project? I have been through seemingly every VS setting and can't find where that is changeable.

In the original thread, I saw question if 2019 16.8 Preview was being used, which I am indeed using.

Here are both my old and new setups, but installed on the same computer. Thanks for ANY help!

=============== Old Setup ================

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

Installed Version: Professional

Microsoft Visual C++ 2010 01018-587-3756007-70116
Microsoft Visual C++ 2010

Microsoft Visual Studio 2010 Team Explorer 01018-587-3756007-70116
Microsoft Visual Studio 2010 Team Explorer

Critical Update for Microsoft Visual Studio 2010 Professional - ENU (KB2938807) KB2938807
Hotfix for Microsoft Visual Studio 2010 Professional - ENU (KB2529927) KB2529927
Hotfix for Microsoft Visual Studio 2010 Professional - ENU (KB2548139) KB2548139
Hotfix for Microsoft Visual Studio 2010 Professional - ENU (KB2549864) KB2549864
Hotfix for Microsoft Visual Studio 2010 Professional - ENU (KB2565057) KB2565057
Hotfix for Microsoft Visual Studio 2010 Professional - ENU (KB2635973) KB2635973
Hotfix for Microsoft Visual Studio 2010 Professional - ENU (KB2890573) KB2890573
Hotfix for Microsoft Visual Studio 2010 Professional - ENU (KB3002340) KB3002340
Intel(R) Visual Fortran Package ID: w_fcompxe_2011.7.258
Intel(R) Visual Fortran Composer XE 2011 Update 7 Integration for Microsoft Visual Studio* Microsoft Visual Studio 2010 Professional - ENU Service Pack 1 (KB983509) KB983509
Security Update for Microsoft Visual Studio 2010 Professional - ENU (KB2645410) KB2645410

================= New Setup =============

Microsoft Visual Studio Professional 2019
Version 16.8.6
VisualStudio.16.Release/16.8.6+31019.35
Microsoft .NET Framework
Version 4.8.03752

Installed Version: Professional

Visual C++ 2019 00435-60000-00000-AA343
Microsoft Visual C++ 2019

ASP.NET and Web Tools 2019 16.8.560.26713
ASP.NET and Web Tools 2019

Azure App Service Tools v3.0.0 16.8.560.26713
Azure App Service Tools v3.0.0

C# Tools 3.8.0-5.20604.10+9ed4b774d20940880de8df1ca8b07508aa01c8cd
Common Azure Tools 1.10
Cookiecutter 16.8.20241.2
Intel® Fortran Compiler Package ID: w_oneAPI_2021.1.2.148
Intel® Fortran Compiler – toolkit version: 2021.1.2, extension version 19.2.0061.16, Package ID: w_oneAPI_2021.1.2.148, Copyright © 2002-2020 Intel Corporation. All rights reserved.
* Other names and brands may be claimed as the property of others.

IntelliCode Extension 1.0
IntelliCode Visual Studio Extension Detailed Info

Microsoft Azure Tools 2.9
Microsoft Azure Tools for Microsoft Visual Studio 2019 - v2.9.30924.1

Microsoft JVM Debugger 1.0
Microsoft MI-Based Debugger 1.0
Microsoft Visual C++ Wizards 1.0
Microsoft Visual C++ Wizards

Microsoft Visual Studio VC Package 1.0
Microsoft Visual Studio VC Package

NuGet Package Manager 5.8.1
ProjectServicesPackage Extension 1.0
ProjectServicesPackage Visual Studio Extension Detailed Info

Python 16.8.20241.2
Python - Conda support 16.8.20241.2
Python - Django support 16.8.20241.2
Python - IronPython support 16.8.20241.2
Python - Profiling support 16.8.20241.2
Python - VC Project Support 16.1.19129.1
Test Adapter for Boost.Test 1.0
Test Adapter for Google Test 1.0
TypeScript Tools 16.0.21016.2001
TypeScript Tools for Microsoft Visual Studio

Visual Basic Tools 3.8.0-5.20604.10+9ed4b774d20940880de8df1ca8b07508aa01c8cd
Visual Studio Code Debug Adapter Host Package 1.0
Interop layer for hosting Visual Studio Code debug adapters in Visual Studio

Visual Studio Tools for CMake 1.0
Visual Studio Tools for CMake

0 Kudos
1 Solution
Steve_Lionel
Honored Contributor III
‎03-03-2021 01:01 PM
12,370 Views
Solved Jump to solution
In response to OptiAndrew

This log file shows a successful link, but there's something I don't understand...

        Found _for_stop_core_quiet
          Referenced in a0flib-take2.lib(axmain.obj)
          Loaded a0flib-take2.lib(libifcoremdd.dll)

It almost looks to me as if someone inserted a copy of libifcoremdd.lib into import library a0flib-take2.lib. That isn't right. Indeed, later, the linker says that libifcoremdd.lib was not used.

View solution in original post

In response to OptiAndrew
0 Kudos
Copy link

Link Copied

33 Replies
cxqi
Novice
‎03-18-2021 07:14 AM
4,036 Views
Solved Jump to solution
In response to Steve_Lionel

I did that. What changes are supposed to happen?

In response to Steve_Lionel
0 Kudos
Copy link
Steve_Lionel
Honored Contributor III
‎03-18-2021 12:29 PM
4,021 Views
Solved Jump to solution
In response to cxqi

It should have installed the 2021 redistributables under C:\Program Files (x86)\Common Files\intel\Shared Libraries\intel64 (and \ia32) - a somewhat different location than earlier releases. It then adds those folders to the system Path environment variable. As long as you don't have an old copy of libifcoremd.dll floating around in your project folder, it should allow your EXE to run. 

If not, try logging out of Windows and logging in again - sometimes this is needed to be able to "see' changes in Path.

If it still fails, let me know - there are additional diagnostics we can do.

 
In response to cxqi
Copy link
cxqi
Novice
‎03-18-2021 02:07 PM
4,012 Views
Solved Jump to solution
In response to Steve_Lionel

Hi Steve,

It works!!!!!

I just realized I put the old DLL files floating around in my project folder. They are missed DLL when I used the Parallel Studio XE. I deleted them and everything goes well.

I really appreciate your kind help. I am new to oneAPI and sometimes can be struck by small problems. 

In response to Steve_Lionel
Copy link
Steve_Lionel
Honored Contributor III
‎03-18-2021 04:41 PM
4,001 Views
Solved Jump to solution
In response to cxqi

Glad to hear it. Never copy runtime DLLs into your application folder.

In response to cxqi
0 Kudos
Copy link
ParkGY
Beginner
‎05-20-2021 07:11 AM
3,883 Views
Solved Jump to solution
In response to Steve_Lionel

Hello, Steve. I'm Park, a graduate student living in korea. I was using parallel studio XE, but my license expired, so i started oneAPI for the first time. So i deleted all the fortran compilers and proceeded to reinstall them, but i encountered the problem of "the entry point for_stop_core_quiet is not located". I could build the program without any error but i got the error when i executed the .exe program.

1.png

 

I confirmed that libifcoremd.dll exists in my lib path 'C : \ Program Files (x86) \ Intel \ oneAPI \ compiler \ 2021.1.1 \ windows \ lib \ x64' and the version is 11.1.5.5. & 20.0.1.0 (tried both version).

 

And i installed the runtime version of Intel Fortran Compiler Classic for windows. (How do i add it to the system path environment variable?). After this process, i got the following error. (The application program failed to start properly (0xc000007b).)

ParkGY_0-1621519783795.png

 

Thank for your help.

 

Park.

 

In response to Steve_Lionel
0 Kudos
Copy link
Steve_Lionel
Honored Contributor III
‎05-20-2021 02:30 PM
3,866 Views
Solved Jump to solution

See if installing the Visual Studio runtime from The latest supported Visual C++ downloads (microsoft.com) helps. The Intel runtime installer added the correct folders to Path - you don't have to do this yourself.

0 Kudos
Copy link
ParkGY
Beginner
‎05-20-2021 09:45 PM
3,851 Views
Solved Jump to solution
In response to Steve_Lionel

I was advised that an error occurred because of conflict with previous version, so i deleted all compilers and reinstalled oneAPI *& visual studio (2017, 2019).  I got an error that libifcoremd.dll is missing, so i downloaded all of C++ and Fortran compiler classic.

ParkGY_0-1621568138567.png

After that, i get the following error that application program failed to start (0xc000007b), but i don't know how to  deal with it.

ParkGY_1-1621568196478.png

I'm really appreciate with your kindness

Thank you.

Park.

In response to Steve_Lionel
0 Kudos
Copy link
Steve_Lionel
Honored Contributor III
‎05-21-2021 07:50 AM
3,834 Views
Solved Jump to solution

Did you install the Microsoft Visual Studio runtime as I suggested above? The error you are seeing is caused by inconsistent DLLs. The advice I usually see suggests installing the latest Visual Studio runtime.

0 Kudos
Copy link
ParkGY
Beginner
‎05-23-2021 11:23 PM
3,809 Views
Solved Jump to solution
In response to Steve_Lionel

ParkGY_0-1621836821387.png

I have installed above 3 files. I got the same error after installing the 1st and 2nd files.

And when installing the 3rd file, the following error occurs. (The installation package is not supported on the current platform)

ParkGY_1-1621837206825.png

The answer was late because it was a weekend.

Thank you

 

In response to Steve_Lionel
0 Kudos
Copy link
Steve_Lionel
Honored Contributor III
‎05-24-2021 09:13 AM
3,797 Views
Solved Jump to solution

Good thing the third package would not install for you! It's not for your architecture.

Let's try a couple of things. First, in your Fortran project properties, go to Fortran > Libraries. Change "Runtime library" to "Multithreaded" (not Multithread DLL"). Rebuild. Do you get an error when linking, and if not, does the program run?

If it does, reset that property back to Multithread DLL. Now go to property page Linker > General. Change "Show Progress" to "Show all progress Messages". Rebuild. Zip the buildlog.htm from the Debug or Release folder (depending on your configuration) and attach the .zip to a reply here.

0 Kudos
Copy link
ParkGY
Beginner
‎05-24-2021 05:43 PM
3,785 Views
Solved Jump to solution
In response to Steve_Lionel

Through the first method,  No error occurs when rebuild.

But the .exe file does not run. (It does not run without any error)

 

Next, i reset that property back and i attach the zip file that you mentioned.

Thank you.

In response to Steve_Lionel
BuildLog.zip
0 Kudos
Copy link
Steve_Lionel
Honored Contributor III
‎05-25-2021 09:21 AM
3,773 Views
Solved Jump to solution

The log in the zip you attached does not show an error. What do you mean by "the .exe file does not run" when you changed the library property?

0 Kudos
Copy link
ParkGY
Beginner
‎05-25-2021 06:55 PM
3,760 Views
Solved Jump to solution
In response to Steve_Lionel

<Change the fortran library>

ParkGY_2-1621992131819.png-> change the fortran library property.

When i executed the exe file, nothing happened under both x64, x86 release. (No error occurred.)

 

<No change the fortran library property>

Even with the x64 release (exe file) nothing happened.

However, the 0xc000007b error occurs only in x86 release.

 

Thank you.

In response to Steve_Lionel
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.