RHEL 6.5: 'import site' failed; use -v for traceback

[chauvjo]

Any idea why I am seeing the following error message when I execute the following command:
source /opt/intel/composer_xe_2013_sp1/bin/compilervars.csh intel64

'import site' failed; use -v for traceback

Thanks....

[Kevin_D_Intel]

I don’t know the cause but Googling suggests a possible relation to Python. If you have done anything in particular with Python lately perhaps that’s related and you might look over anything you have done in that area.

It appears the debuggervars.csh (called by compilarvars.csh) tinkers with python in trying to determine the installed versions so this could be related to the message.

• Do you have multiple versions of python on installed?  Maybe a version in /usr/bin and something else in say /usr/local/bin?
• Do you get the message if you enter the command: ./python
• What particular version of the Composer XE SP1 do you have installed?  And is this a new CXE SP1 installation?
• Is this a new RHEL6.5 installation?

[chauvjo]

I found the problem....the following environment variable was set in my shell script:

setenv PYTHONHOME /opt/intel/composer_xe_2015.0.090/debugger/python/intel64/

Removing this statement fixed the problem...

Thanks for the hints...

[Kevin_D_Intel]

Ah ha!  And I can also reproduce that error when setting that variable and that seems to be the root of the issue.

Your original post references the compilervars.csh from the CXE 2013 SP1 release but your last post notes an env-var setting that references the IPS XE 2015 release; however, that mixing is not the issue. The only relation to mixing those and the error is the python tinkering that's found in the debuggervars.csh under the CXE 2013 SP1 release. I can create the same error when I set the PYTHONHOME as you noted and run the /usr/bin/python.

Maybe the interest in setting PYTHONHOME was to use the python version distributed as part of the debugger component in IPS XE 2015 which does not seem necessary. I’m not a python user but it appears you can set your PATH according first with:

setenv PATH /opt/intel/composer_xe_2015.0.090/debugger/python/intel64/bin:${PATH}

And then use that version of python with:

$ which python
/opt/intel/composer_xe_2015.0.090/debugger/python/intel64/bin/python

$ python
Python 2.7.5 (default, Aug 20 2013, 17:49:47)
[GCC 4.1.2 20080704 (Red Hat 4.1.2-44)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>

Anyway, glad to hear you were able to resolve the issue.

[chauvjo]

The reason I added the PYTHONHOME environment variables was because the debugger gdb would not run.  With  IPS XE 2015 , the Intel Debugger is no longer available and we are told to now use gdb.  What I did not know was the version to use is gdb-ia not gdb.   Anyway, I gave up and just installed the previous version of CXE 2013 SP1 to get the Intel Debugger (idb) back.

Add my vote to bring back the Intel Debugger.  If not, please give step-by-step instructions on how to get eclipse and gdb-ia to work.  Under RHEL 6.5, I have not been able to figure out how to configure eclipse to use gdb-ia. 

[Kevin_D_Intel]

Thanks for the additional insight. I will see what I can find to help with that.