Community
cancel
Showing results for 
Search instead for 
Did you mean: 
eldiener
New Contributor I
195 Views

Problem setting up command line environment with Parallel Studio XE in Linux

I have a number of versions of Intel C++ in Parallel Studio XE implementations on Linux going back to parallel_studio_xe_2013. These include 2013, 2015, 2016, 2017, 2018, 2019, all installed in the same /opt/intel directory.

The releases 2017, 2018, and 2019 give problems when trying to setup the environment for C++ compilation from the command line.

For 2017, whether I invoke:

. /opt/intel/parallel_studio_xe_2017/psxevars.sh ia32

or

. /opt/intel/parallel_studio_xe_2017/psxevars.sh intel64

the resulting PATH has only /opt/intel/parallel_studio_xe_2017.8.066/bin added to it ( for the latest release 8 ) but there is no icpc in that path.

For 2018, when I invoke:

. /opt/intel/parallel_studio_xe_2018/psxevars.sh ia32

the resulting PATH has /opt/intel/compilers_and_libraries_2018.5.274/linux/bin/intel64 as the first entry for finding icpc even though icpc for 32-bit compilation is in /opt/intel/compilers_and_libraries_2018.5.274/linux/bin/ia32. Invoking:

. /opt/intel/parallel_studio_xe_2018/psxevars.sh intel64

works properly.

The situation for 2019 is the same as for 2018. When I invoke:

. /opt/intel/parallel_studio_xe_2019/psxevars.sh ia32

the resulting PATH has /opt/intel/compilers_and_libraries_2019.4.243/linux/bin/intel64 as the first entry for finding icpc even though icpc for 32-bit compilation is in /opt/intel/compilers_and_libraries_2019.4.243/linux/bin/ia32. Invoking:

. /opt/intel/parallel_studio_xe_2019/psxevars.sh intel64

works properly.

Is there any fix for the environmental setup problems in these last three releases ?

 

 

0 Kudos
1 Reply
eldiener
New Contributor I
194 Views

I discovered that if I install the Parallel Studio XE versions as a user off of my HOME directory the setting of the command line environment works correctly. Evidently installing the Parallel Studio XE versions as root, and then setting up the command line environments as a normal user prior to invoking the compiler, is flawed. I do not think that installing the Parallel Studio XE as root should require the end user to use the product as root in order for the C++ compiler to work properly. Almost all Linux packages are installed as root and accessible by the user, and Parallel Studio XE should not be any different.

Reply