- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is there a special reason that all avx related .so files (avx, avx2, avx512, vml_avx, vml_avx2, vml_avx512) do not come with a standard .so link, but only as .so.X in the standard intel oneapi hpc toolkit?
Just now with the release of 2022.0.0, this broke our pipeline because it changed from .so.1 to .so.2 and I was already before that release confused that you do not ship it with a link without the number suffix.
Thanks and best wishes,
Miguel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Miguel,
Thanks for reaching out to us.
Intel oneMKL started adding shared library versioning which was not there till Intel MKL 2020 update 4
>>Is there a special reason that all avx related .so files (avx, avx2, avx512, vml_avx, vml_avx2, vml_avx512) do not come with a standard .so link, but only as .so.X ...
By versioning the shared libraries,
> Allows applications to work correctly in an environment with multiple oneMKL and/or Intel® MKL packages installed
> Communicates clearly when incompatible changes are made, and an application should be rebuilt
> Allows you to link against a specific version of shared libraries
>> it changed from .so.1 to .so.2
The starting version of the shared libraries is '1' and it will be incremented if there are any changes that break backward compatibility.
Please refer to the below link for a detailed explanation regarding the versioning of the shared library.
Hope the provided information helps.
Regards,
Vidya.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Miguel,
Thanks for reaching out to us.
Intel oneMKL started adding shared library versioning which was not there till Intel MKL 2020 update 4
>>Is there a special reason that all avx related .so files (avx, avx2, avx512, vml_avx, vml_avx2, vml_avx512) do not come with a standard .so link, but only as .so.X ...
By versioning the shared libraries,
> Allows applications to work correctly in an environment with multiple oneMKL and/or Intel® MKL packages installed
> Communicates clearly when incompatible changes are made, and an application should be rebuilt
> Allows you to link against a specific version of shared libraries
>> it changed from .so.1 to .so.2
The starting version of the shared libraries is '1' and it will be incremented if there are any changes that break backward compatibility.
Please refer to the below link for a detailed explanation regarding the versioning of the shared library.
Hope the provided information helps.
Regards,
Vidya.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Miguel,
Reminder:
Has the information provided helped?
If yes, could you please confirm whether we can close this thread from our end?
Regards,
Vidya.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Miguel,
Thanks for accepting our solution.
As your issue is resolved we are closing this thread from our end.
If you need any additional assistance from Intel, please post a new question as this thread will no longer be monitored.
Have a Nice Day!
Regards,
Vidya.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page