- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The xiar tool (archive tool for IPO objects) was not distributed with the
intel-oneapi-compiler-shared-2025.0 rpm pack for Fedora linux.
It was present until intel-oneapi-compiler-shared-2024.2 and stored in
/opt/intel/oneapi/compiler/2024.2/bin
Was this intentional?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I should have remembered - xiar was used for the old Classic Compiler IPO generated objects and libraries.
for the new LLVM lto ( IPO ) binaries we have a ar tool in .../bin/compiler/llvm-ar
This recognizes our objects with Intel GPU offload kernel code along with the CPU code (fat objects)
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am attempting to find our which rpm package has xiar.
But I am curious - you are extracting the RPMs from the installer and using the RPMs directly? From what product download or repo package are you pulling?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Ron.
I'm running Fedora Linux, so I'm using dnf to install/upgrade OneAPI.
The xiar app was provided by:
intel-oneapi-compiler-shared-2024.2-2024.2.1-1079.x86_64 : Intel(R) Compiler Shared Files
Repo : @system
Matched From :
Filename : /opt/intel/oneapi/compiler/2024.2/bin/xiar
I installed all OneAPI files with RPMs provided by the Yum/dnf repository, which I installed as per instructions in:
$>cat /etc/yum.repos.d/oneAPI.repo
[oneAPI]
name=Intel(R) oneAPI repository
baseurl=https://yum.repos.intel.com/oneapi
enabled=1
gpgcheck=1
repo_gpgcheck=1
gpgkey=https://yum.repos.intel.com/intel-gpg-keys/GPG-PUB-KEY-INTEL-SW-PRODUCTS.PUB
I can use the GNU ar, no problem. It's just that I was used to archive objects compiled with ifort/ifx using xiar.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I should have remembered - xiar was used for the old Classic Compiler IPO generated objects and libraries.
for the new LLVM lto ( IPO ) binaries we have a ar tool in .../bin/compiler/llvm-ar
This recognizes our objects with Intel GPU offload kernel code along with the CPU code (fat objects)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
OK, found it.
The syntax is similar to the old xiar, I guess?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yes, very similar.
But if you have older libraries and/or objects built with ifort -ipo then that older IPO format will not be recognized by llvm-ar and you will need an older copy of xiar to manipulate those older binaries.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page