fedora 12 again

[Kevin_Shuford]

I am having problems getting the fortran compiler running on my 64 bit box running fedora 12. I am aware of the 32 bit library issue, and I believe that issue hasbeen resolved by installing compat-libstdc++-33.i686 and glibc-devel.i686 via yum. Then I set the environment variables bysourcing ifortvars.sh intel64.This seems to set the pathsfor the executable and libraries (as shown by echo),butI still get an error related to not being able to find libstdc++.so.5. IfItry to compile in another window, thepaths are not recognized at all and ifort cannot be found. Moreover, if I restart, once again the paths cannot be found. Do I need to add a line to bash_profile (or /etc/profile for my multiuser workstations) to source upon login and more importantly how can I get ifort up and running? Extremely frustrated...

[Ron_Green]

Quoting - Kevin Shuford

I am having problems getting the fortran compiler running on my 64 bit box running fedora 12. I am aware of the 32 bit library issue, and I believe that issue hasbeen resolved by installing compat-libstdc++-33.i686 and glibc-devel.i686 via yum. Then I set the environment variables bysourcing ifortvars.sh intel64.This seems to set the pathsfor the executable and libraries (as shown by echo),butI still get an error related to not being able to find libstdc++.so.5. IfItry to compile in another window, thepaths are not recognized at all and ifort cannot be found. Moreover, if I restart, once again the paths cannot be found. Do I need to add a line to bash_profile (or /etc/profile for my multiuser workstations) to source upon login and more importantly how can I get ifort up and running? Extremely frustrated...

For a 64bit system you also need compat-libstdc++-33.x86_64 which is the 64bit version of the compatibility library. Did you install that?

multiple windows - each new terminal is a new shell and thus it does NOT inherit the env vars in another window. So yes, you have the right idea to put the source command in /etc/profile OR your ~/.bashrc file. It's a safe way to make sure the source command is always invoked with each new bash shell.

you can use the commands 'which' and 'ldd' to see if all the external references are resolved (note, my paths are different than default)

[rwgreen@dpd22 ~]$ which fortcom
/opt/spdtools/compiler/cpro/Compiler/11.1/064/bin/intel64/fortcom
[rwgreen@dpd22 ~]$ ldd /opt/spdtools/compiler/cpro/Compiler/11.1/064/bin/intel64/fortcom
libm.so.6 => /lib64/libm.so.6 (0x0000003d10000000)
libstdc++.so.5 => /usr/lib64/libstdc++.so.5 (0x00002aaaaaad7000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000003d14800000)
libc.so.6 => /lib64/libc.so.6 (0x0000003d0fc00000)
libdl.so.2 => /lib64/libdl.so.2 (0x0000003d10400000)
/lib64/ld-linux-x86-64.so.2 (0x0000003d0f400000)

[Kevin_Shuford]

Quoting - Ronald W. Green (Intel)

For a 64bit system you also need compat-libstdc++-33.x86_64 which is the 64bit version of the compatibility library. Did you install that?

multiple windows - each new terminal is a new shell and thus it does NOT inherit the env vars in another window. So yes, you have the right idea to put the source command in /etc/profile OR your ~/.bashrc file. It's a safe way to make sure the source command is always invoked with each new bash shell.

you can use the commands 'which' and 'ldd' to see if all the external references are resolved (note, my paths are different than default)

[rwgreen@dpd22 ~]$ which fortcom
/opt/spdtools/compiler/cpro/Compiler/11.1/064/bin/intel64/fortcom
[rwgreen@dpd22 ~]$ ldd /opt/spdtools/compiler/cpro/Compiler/11.1/064/bin/intel64/fortcom
libm.so.6 => /lib64/libm.so.6 (0x0000003d10000000)
libstdc++.so.5 => /usr/lib64/libstdc++.so.5 (0x00002aaaaaad7000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000003d14800000)
libc.so.6 => /lib64/libc.so.6 (0x0000003d0fc00000)
libdl.so.2 => /lib64/libdl.so.2 (0x0000003d10400000)
/lib64/ld-linux-x86-64.so.2 (0x0000003d0f400000)

Everything worked. I had not installed the last library you mentioned. Thanks forthe help.