Package Details: intel-vtune-amplifier 2018.

Git Clone URL: (read-only)
Package Base: intel-parallel-studio-xe
Description: Performance profiler for serial and parallel performance analysis 0.2.525261
Upstream URL:
Licenses: custom
Submitter: bred
Maintainer: fishstamp82
Last Packager: fishstamp82
Votes: 109
Popularity: 0.600692
First Submitted: 2012-02-02 21:33
Last Updated: 2017-12-21 20:40

Latest Comments

alleut commented on 2018-02-22 02:19

Is it possible to build these packages directly from Intel's RPMs or DEBs, without PSXE?

post-factum commented on 2018-01-21 20:50

Could you please consider using default package compressor (xz) instead of lzo? repo-add does not recognise lzo packages, and thus this package cannot be properly installed via aurutils.

karamaz0v commented on 2017-12-21 17:35

In this new update the intel mpi sdk is still missing (mpiicc, mpiifort, mpicc...)

Following mach6 comment for the previous version, I updated the PKGBUILD to include the intel-mpi-sdk rpm from the Intel MPI package at

that provides the MPI development kit.

It can be used with the same open source license as the parallel studio suite.

I uploaded the modified PKGBUILD in this gist:

invik commented on 2017-12-18 19:17

I agree with Invarianz (thanks!): "math_common_define.h" is missing with the current PKGBUILD, and adding his line to the "package_intel-compiler-base" solves the issue.

Invarianz commented on 2017-12-15 11:39

In this version there is some kind of critical error and i am not sure if it is related to the AUR version here.

When i import complex.h included in mkl i get a critical error saying that a specific header called "math_common_define.h" is missing.

EDIT: I unpacked the files directly provided by intel (""). When unpacking i was able to locate the files. It seems that some *.rpm is not unpacked in this AUR-version.

SECOND EDIT: I found the culprit: The new rpm that does not get extracted by this PKGBUILD is: "intel-c-comp-common-18.0.1-163-18.0.1-163.noarch.rpm"

If one adds the entry:

extract_rpms 'intel-c-comp*.rpm' $xe_build_dir

in the PKGBUILD-function "package_intel-compiler-base()" everything should work again.

mach6 commented on 2017-11-22 01:57

Some comments
For those who want to install Intel MPI:
1. First download and decompress the file as kris.keipert mentioned:
tar -zxvf l_mpi_2018.0.128.tgz
cd l_mpi_2018.0.128/rpm
for f in *.rpm; do bsdtar -xf $f; done
cp -r ./opt /opt
2. Change some enviromental variables:
ln -s /opt/intel/advisor_2018.1.0.523188 /opt/intel/advisor_2018
ln -s /opt/intel/inspector_2018.1.0.522981 /opt/intel/inspector_2018
ln -s /opt/intel/vtune_amplifier_2018.0.2.525261 /opt/intel/vtune_amplifier_2018
ln -s /opt/intel/compilers_and_libraries_2018.0.128 /opt/intel/compilers_and_libraries_2018

cd /opt/intel/parallel_studio_xe_2018.0.033/
sed -i 's|SCRIPTPATH=\%.*|SCRIPTPATH=/opt/intel|' *.sh
sed -i 's|SCRIPTPATH=\%.*|SCRIPTPATH=/opt/intel|' *.csh
cp ./bin/
cp psxevars.csh ./bin/

cd /opt/intel/composerxe/linux/bin/
sed -i 's|PROD_DIR=.*|PROD_DIR="/opt/intel/composerxe/linux"|' *.sh
sed -i 's|PROD_DIR=.*|PROD_DIR="/opt/intel/composerxe/linux"|' *.csh

cd /opt/intel/composerxe/linux/mpi/intel64/bin
sed -i 's|I_MPI_ROOT=.*;|I_MPI_ROOT=/opt/intel/composerxe/linux/mpi;|'
"For csh, I'm not sure how to use sed"
3. Once finished, you can excute:
source /opt/intel/parallel_studio_xe_2018.0.033/ intel64
to set enviromental variables. You can test mpi by using mpiicc to compile a mpi code and use mpirun to test running

kris.keipert commented on 2017-10-09 16:39

For those who have the current package installed and want to add on MPI from the cluster edition:

Download MPI from
Run 'bsdtar -xf' on all RPMs
Copy the extracted opt folder to /
Edit the I_MPI_ROOT definition in to point to /opt/intel/compilers_and_libraries_2018.0.128/linux/mpi

microdou commented on 2017-10-08 02:58

I got the same error in compiling r-mkl (AUR).

alexanderp commented on 2017-09-26 17:24


intel-tbb.conf should be modified as such:


About the compiling problem, I'm having trouble compiling r-mkl (AUR).
It fails at the configure stage with:

checking whether mixed C/Fortran code can be run... configure: WARNING: cannot run mixed C/Fortran code
configure: error: Maybe check LDFLAGS for paths to Fortran libraries?

fishstamp82 commented on 2017-09-25 17:27


The PATH variable has nothing to do with this packages, you define it yourself.


You are right, now the cluster version finally works and I will fix the mpi wrappers asap

All comments