- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a user with the 2019 compiler. He tries to load a dll that needs for_alloc_assign_v2 and gets the message that the entry poiint cannot be found in the dynamic link library. I found in the 2015 release notes that this was new for 15.0.2 and any newer compiler should be fine. Where is this routine? What limitations are there on when it will be found. He has 2019 integrated with VS2013. The 2015 release notes do not mention a visual studio dependence. Can you provide a full summary of the requirements?
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Most likely a copy of an older DLL has been placed in some folder earlier on PATH (or worse, in the Windows or Windows\System32 folder). This entry point is in libifcoremd.dll which should be located in C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\ia32_win\compiler and C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\intel64_win\compiler
An easy way to find which DLL is being loaded is to analyze the EXE with Dependency Walker. (Ignore complaints about mixed platforms, but do take note if libifcoremd.dll is being loaded from somewhere else.
There is no dependency on Visual Studio here.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks Steve! That is precisely the problem. He had an old copy listed first on his path. Good to know.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page