- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I am using Intel compiler (11.1\\0.65)on 64-bit machine.
While building a certain project, I receive the following error:
error LNK2019: unresolved external symbol "__declspec(dllimport) public: bool __cdecl recordingsimulation::AbsDataSource::MoveToNextFile(void)" (__imp_?MoveToNextFile@?$AbsDataSource@PEAX$0PPPPPPPP@@recordingsimulation@@QEAA_NXZ) referenced in function "private: void __cdecl MessageHandler::HandleACLInputError(void)" (?HandleACLInputError@MessageHandler@@AEAAXXZ)
When compiling in win32 it builds fine, but in the x64 configuration it fails.
I switched to the visual c++compiler and the build succeeded.
Most of the methods in the class are virtual, but the specific method it doesn't find isn't (MoveToNextFile).
When I declared it as virtual the problem was solved and the build succeeded, but it shouldn't be virtual.
Do you have any idea why the Intel compiler doesn't "see" the symbol?
Maybe I should turn on some flags?
I don't want to leave the virtual as now.
Thank you,
Liad.
I am using Intel compiler (11.1\\0.65)on 64-bit machine.
While building a certain project, I receive the following error:
error LNK2019: unresolved external symbol "__declspec(dllimport) public: bool __cdecl recordingsimulation::AbsDataSource
When compiling in win32 it builds fine, but in the x64 configuration it fails.
I switched to the visual c++compiler and the build succeeded.
Most of the methods in the class are virtual, but the specific method it doesn't find isn't (MoveToNextFile).
When I declared it as virtual the problem was solved and the build succeeded, but it shouldn't be virtual.
Do you have any idea why the Intel compiler doesn't "see" the symbol?
Maybe I should turn on some flags?
I don't want to leave the virtual as now.
Thank you,
Liad.
Link Copied
4 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Have checked that your directories are the same for x64 config? I had the same problem once and had to add all my include and lib dirs in the x64 config.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Not clear what the issue is without a test case. Can you send a test case that we can use to reproduce the problem?
There's is also the the 11.1.067 compiler available in case you would like to try and see if it resolves the issue.
--mark
There's is also the the 11.1.067 compiler available in case you would like to try and see if it resolves the issue.
--mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Liad,
What configuration do you use for the project?
If it is Release could you try Debug. Or simply try reducing optimization level.
Alex
What configuration do you use for the project?
If it is Release could you try Debug. Or simply try reducing optimization level.
Alex
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, please try not use /Qipo.
But it is still a compiler bug. Is it possible to send the testcase in private post? Or please use Premier Support - https://premier.intel.com/
Thanks,
Jennifer
But it is still a compiler bug. Is it possible to send the testcase in private post? Or please use Premier Support - https://premier.intel.com/
Thanks,
Jennifer

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page