Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

Finalising new installation

dieterhansbritzgmail
1,118 Views
I have just installed the latest Intel Fortran in my Suse 11.4 Linux system,
and it told me at thew end, that I must

(replace "intel64" with "ia32" if you are using a 32-bit platform).
For csh/tcsh:
$ source install-dir/bin/compilervars.csh intel64
For bash:
$ source install-dir/bin/compilervars.sh intel64

I don't know how to do the environment thing, and there is
no directory called install-dir etc. I do find the new files under
/opt/intel/ etc, but when I put that into the line followed by intel32,
it still doesn't work. I get told that ifort is an unknown command.
What do I do?

Dieter
0 Kudos
8 Replies
Ron_Green
Moderator
1,118 Views
Hi Dieter,

try this:

source /opt/intel/bin/compilervars.sh ia32

use "ia32" for 32 bit, and "intel64" for 64bit. Yeah, it's confusing and no-symmetric naming. Obviously not well thought out, these names.

ron
0 Kudos
Nikolay_L_Intel
Employee
1,118 Views
Hello Deiter,

You alwayscan find the install locationin two lines above, like
...
To get started using located in
/opt/intel/composer_xe_2011.5.xxx:
- Set the environment variables...

I will address your feedback to the next usability review to modify message wording and make it clearer.

Thank you,
- Nikolay
0 Kudos
mecej4
Honored Contributor III
1,118 Views
Please follow the instructions given at

http://software.intel.com/en-us/articles/intel-compilers-linux-installation-help/

Although Ubuntu may not be officially supported, users have generally installed the Intel compilers on various versions of Ubuntu.

In short, you login with root permissions, open a command shell, change to the directory containing the downloaded installer, set its permission to include 'execute', if necessary, and run it after (i) deciding where to install the compiler and (ii) obtaining the serial number.
0 Kudos
sukantamech
Beginner
1,118 Views
Thnaks for the support. I have installed Intel composer XE-2011.5.200 update5 in Ubuntu 11.04 (64bit).

But after installation i follwed the steps as detailed in the next step in this forum....but I am getting...




sukanta@Energy:~$ sudo /opt/intel/composerxe-2011.5.220/bin/compilervars.sh intel64
[sudo] password for sukanta:
[: 121: intel64: unexpected operator
[: 121: intel64: unexpected operator
[: 121: intel64: unexpected operator
[: 121: intel64: unexpected operator
[: 121: intel64: unexpected operator
[: 121: intel64: unexpected operator
[: 121: intel64: unexpected operator
[: 121: intel64: unexpected operator

ERROR: Unknown option 'intel64'

Syntax:
/opt/intel/composerxe-2011.5.220/bin/compilervars.sh [MKL_interface] [mod]

must be one of the following
ia32 : Set up for IA-32 target
intel64 : Set up for Intel 64 target
mic : Set up for Intel MIC target

mod (optional) - set path to MKL F95 modules

MKL_interface (optional) - MKL programming interface for intel64
Not applicable without mod
lp64 : 4 bytes integer (default)
ilp64 : 8 bytes integer

sukanta@Energy:~$



PLEASE HELP ME.....!!!

0 Kudos
mamut
Beginner
1,118 Views

Hi, I had same error messagess and found previous discution about this script (http://software.intel.com/en-us/forums/showthread.php?t=79115) mentining problems with == operator ...

So changing == operator in ifs to = seems to fix the problem

(I had mine problem with ComposerXE-2011.4.191 on 64 bit debian squeeze )

0 Kudos
TimP
Honored Contributor III
1,118 Views
Did you check which shell is running? If you don't care to check, did you try compilervars.csh?
0 Kudos
diedro
Beginner
1,118 Views
Hi,
I am usuins Ubuntu 11.04 also:
go to:
[bash]/etc[/bash]
then open the bash file with gedit and super user, by shell:
[bash]/etc$ sudo gedit bash.bashrc[/bash]
after that ad at the end of the file:
[bash]source /opt/intel/compilerpro-12.0.0.xxx/bin/ifortvars.sh intel64
export LD_LIBRARY_PATH=/opt/intel/compilerpro-12.0.0.xxx/debugger/lib/intel64:$LD_LIBRARY_PATH
export PATH[/bash]
save and close the file. Open a new shall and check if you get error.
This should work
(maybe you shall restart the bash file but I do not remember)
0 Kudos
Reply