Package Base Details: intel-parallel-studio-xe

Git Clone URL: https://aur.archlinux.org/intel-parallel-studio-xe.git (read-only)
Keywords: compiler intel mkl mpi openmp tbb vtune
Submitter: bred
Maintainer: alyst (stephencox)
Last Packager: alyst
Votes: 129
Popularity: 0.856062
First Submitted: 2012-02-02 21:33
Last Updated: 2019-04-23 12:12

Latest Comments

1 2 3 4 5 6 ... Next › Last »

alyst commented on 2019-04-23 12:23

I've updated the package to 2019.3 (thanks @hsbadr!) plus did small cleaning ups and rearrangements:

  • intel-compiler-base is split into intel-common-libs, intel-openmp and intel-compiler-base (this one depends on the former two)
  • intel-mkl was implicitly dependent on intel-compiler-base before (required composerxe symlink (not anymore) and libimf.so) -- now it explicitly depends on intel-common-libs
  • the default PKGEXT=.pkg.tar.xz really makes packaging slow, so I've kept PKGEXT=.pkg.tar.lzo override. Now it's mentioned in the log and I've also added support for FORCE_PKGEXT var that you can specify on the command line to avoid editing PKGBUILD.

It works for me with r-mkl, but let me know if you have any problems with the updated packaging.

alyst commented on 2019-04-22 16:53

+1 for removing PKGEXT. In addition to all other reasons, .lzo is not currently understood by pacman's repo-add.

alexanderp commented on 2019-04-22 12:13

Hi. Is the maintainer (fishstamp82) planning to update this package? If not, can you please orphan it so someone else can keep it up to date? Thanks.

hsbadr commented on 2019-04-15 17:08

Intel Parallel Studio XE 2019 Update 3 (2019.3.199):

https://github.com/hsbadr/intel-parallel-studio-xe/commit/17e5d60146f66758e9b1772723132d1a1b0230ce

JoshH100 commented on 2019-03-29 19:43

Can you remove the custom package extension? Although I am a fan of lzop compression, a lot of tools for repository management have issues with it. It's also not standard practice to override the PKGEXT specified in makepkg.conf. Thanks.

ArniDagur commented on 2019-01-13 00:10

@sephencox: Is there any reason why intel-daal and intel-gdb are not offered as subpackages even though they seem to be included in the downloaded archive?

bred commented on 2018-12-24 18:54

The compilers path is not in the system PATH. And, the libraries (mkl ... ) are not in the ldconfig database.

Please fix these two points.

ChrisTX commented on 2018-12-11 16:43

As a hint to anyone trying to using package on Windows Subsystem for Linux: The package will fail to build since several of the library packages (intel-ipp, intel-mkl, …) move a folder that is currently opened during the packaging step. By adding cd ${xe_build_dir} before each of the Move package steps, this issue can be circumvented and the package will work on WSL.

While this isn't a problem on actual Linux per se, WSL still has this limitation - maybe it could be added to the remaining subpackages that don't do this - since it wouldn't have any negative effects anyways?

ChrisTX commented on 2018-12-11 16:23

intel-mpi should now either (as of 2019) depend on libfabric or include compilers_and_libraries_.../linux/mpi/<arch>/libfabric/lib in the ld.so.conf script. Otherwise, Intel MPI will not work due to libfabric.so missing.

stephencox commented on 2018-12-10 08:13

Updated