Error when using compilervars.csh/ippvars.csh - arch: Undefined variable.

Reference number: DPD200253488

Products: Intel® C++ Composer XE, Intel® Integrated Performance Primitives for Linux*

Version: 2013 SP1 Update 2 (compiler 14.0), IPP 8.1 (Initial Release)

Operating Systems: Linux* / IA-32, Intel® 64

Problem Description:

A defect exists in the Intel® Integrated Performance Primitives (IPP) 8.1 Initial release in the ippvars.csh file distributed for Linux* (found under: /opt/intel/composer_xe_2013_sp1/ipp).

The IPP 8.1 release (Package ID: l_ipp_8.1.0.144) is available as a stand-alone download or bundled with the Intel® Composer XE 2013 SP1 Update 2 release (Package id: l_ccompxe_2013_sp1.2.144) for customers with valid licenses from the Intel Registration Center.

The defect is caused by improper initialization an internal variable used within the script that leads to the error “arch: Undefined variable.” when the script is sourced directly or indirectly via the compilersvars.csh script (found under: /opt/intel/composer_xe_2013_sp1/bin).

For example:

$ cd /opt/intel/composer_xe_2013_sp1.2.144/bin
$ source ./compilervars.csh intel64
arch: Undefined variable.

Resolution:   This defect is fixed in the Intel® C++ Composer XE 2013 SP1 Update 3 Release (Package id: l_ccompxe_2013.1.3.174 - Version Build 20140422) now available from our Intel Registration Center.

In lieu of a permanent fix, users (or sys-admins) with appropriate root privileges can edit the ippvars.csh file to insert ONLY the new line 37 as noted in the code snippet below (ahead of line 38 which is the original line 37) to set the variable arch to the value of the first incoming argument (e.g. $1):

     37    set arch="$1"
     38    if ( "$1" == "ia32_intel64" ) then
     39     setenv arch intel64
     40    endif


For more complete information about compiler optimizations, see our Optimization Notice.


MAD\rwgreen's picture

This bug is fixed in the Update 3 compiler, version composer_xe_2013_sp1.3.174


Thank you for the feedback. We apologize for the issue. It does only occur when the included IPP from update 2 is installed. I am glad you were able to find an immediate resolution. The issue will be resolved in our next Composer XE 2013 SP1 update tentatively scheduled later this month.

I just installed composer_xe_2013_sp1.2.144, and one of my users immediately ran into this.  I fixed it just the way it's done here, without reference to this forum.  I figured I'd be public-spirited and report it; lo and behold, it's been known about for weeks.

I'm afraid this makes you guys look kinda lame, because for C-shell users, the update's pretty much worthless out of the box. How hard can it be to rebuild the composer_xe_2013_sp1.2.144 tarballs on the download page with the bug fixed?  You could give it a new number, and there's your "future update".

Add a Comment

Have a technical question? Visit our forums. Have site or software product issues? Contact support.