Package Base Details: intel-parallel-studio-xe

Git Clone URL: https://aur.archlinux.org/intel-parallel-studio-xe.git (read-only, click to copy)
Keywords: compiler intel mpi openmp tbb vtune
Submitter: bred
Maintainer: pika02
Last Packager: xuanruiqi
Votes: 136
Popularity: 1.06
First Submitted: 2012-02-02 21:33
Last Updated: 2020-11-09 22:33

Pinned Comments

shmilee commented on 2021-03-25 05:45

The download url changed. http://registrationcenter-download.intel.com/akdlm/irc_nas/tec/17113/parallel_studio_xe_2020_update4_cluster_edition.tgz

hbhkx commented on 2020-04-21 08:40

@Pete @Svenstaro OK, intel-mkl_psxe has been removed. Anyone who needs MKL package use intel-mkl in [community] please

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 ... Next › Last »

huyz commented on 2019-12-19 07:24

Version 2020's link: http://registrationcenter-download.intel.com/akdlm/irc_nas/tec/16225/parallel_studio_xe_2020_cluster_edition.tgz

janisozaur commented on 2019-11-19 20:00

On my system it used to take days to build the package, unless the "strip" option was disabled. I have investigated this and found there is a non-standard way is shipped by Intel: with debuginfo in static libraries, which when stripped out to separate file, was causing objcopy to calculate the CRC over and over again for each of the entries in the archive. I have submitted patches to llvm-objcopy (https://reviews.llvm.org/D61343; merged) and GNU objcopy (https://sourceware.org/bugzilla/show_bug.cgi?id=24499; replaced with an early exit instead).

It should now take just minutes to build this package instead of days.

carlosal1015 commented on 2019-11-03 19:04

Thank you so much, now I installed with yay and download the *.lic file to the respective path and icc --help works.

bwrsandman commented on 2019-10-30 20:07

It works now. I'm not sure what's different. I disabled debug in my makepkg.conf and modified PKGBUILD to only have pkgname=('intel-vtune-amplifier') this time.

damianj commented on 2019-10-29 03:07

@alyst Yes, that worked. Thank you.

alyst commented on 2019-10-28 21:43

@carlosal1015 @damianj It might be related to the message about FORCE_PKGEXT. I suspect it might be the bug in the new makepkg, because this message leaks into .SRCINFO. I've disabled this message now. Could you please try the updated PKGBUILD?

@bwrsandman I cannot reproduce this with the latest version (which is vtune_amplifier_2019.6.0.602217). Could you check whether the current version of the package works on your system?

damianj commented on 2019-10-28 19:41

Installation fails, last few lines before error pasted below:

    intel-tbb.install ... Passed
    EULA.txt ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting parallel_studio_xe_2019_update5_cluster_edition.tgz with bsdtar
==> Sources are ready.
Can not find package name : [==> Overriding the default PKGEXT with '.pkg.tar.lzo' to save compression time]

bwrsandman commented on 2019-10-28 14:46

Hi, launching amplxe-gui gives me the following message.

/opt/intel/vtune_amplifier_2019.4.0.597835/backend/bin64/amplxe-node: /opt/intel/vtune_amplifier_2019.4.0.597835/backend/bin64/amplxe-node: no version information available (required by /opt/intel/vtune_amplifier_2019.4.0.597835/backend/bin64/amplxe-node)
/opt/intel/vtune_amplifier_2019.4.0.597835/backend/bin64/amplxe-node: symbol lookup error: /opt/intel/vtune_amplifier_2019.4.0.597835/backend/bin64/amplxe-node: undefined symbol: , version 

Failed to launch VTune Amplifier GUI...

Any clues what I need to do?

My PATH includes /opt/intel/vtune_amplifier_2019.4.0.597835/bin64 and I'm running with amplxe-gui --log-level debug --log-to-console from that directory.

carlosal1015 commented on 2019-10-27 22:34

Hi, I installed intel-fortran-compiler 2019.5.281-2 with date 2019-10-27 06:06 in the AUR. At the end, I recived the following message in the terminal.

==> Sources are ready. Can not find package name : [==> Overriding the default PKGEXT with '.pkg.tar.lzo' to save compression time]

I do not modify the PKGBUILD. Someone knows a solution?

alyst commented on 2019-10-27 11:09

@acxz Thanks for the report, I've fixed the PKGBUILD.

@huyizheng I've added these paths to intel-mpi.conf. Could you please check if that works for you?