- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear All,
After i successfully compiled a programm with the Non-Comercial Fortran Compose XE 2011in an CentOs (RedHat-Derivate) buti always recieved an Error-Message everytime i execute my programm from console:
error while loading shared libraries: libifort.so.5: cannot open shared object file: No such file or directory
But if ido the statement
bin~$ source [MyInstallDir]/bin/compilervars.sh intel64
on my local home directory before, my program works correctly.
Soi thought it could be an Path Problems, and itryed toplace this statement on my /etc/profile file. But unfortunatelly it doesn't help at all.
Couldyou help meto solvethis problem?
Thank you in advance
Soasil
After i successfully compiled a programm with the Non-Comercial Fortran Compose XE 2011in an CentOs (RedHat-Derivate) buti always recieved an Error-Message everytime i execute my programm from console:
error while loading shared libraries: libifort.so.5: cannot open shared object file: No such file or directory
But if ido the statement
bin~$ source [MyInstallDir]/bin/compilervars.sh intel64
on my local home directory before, my program works correctly.
Soi thought it could be an Path Problems, and itryed toplace this statement on my /etc/profile file. But unfortunatelly it doesn't help at all.
Couldyou help meto solvethis problem?
Thank you in advance
Soasil
1 Solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You came close to solving the problem yourself.
Just as the PATH environment variable is searched for executable files, it is the LD_LIBRARY_PATH variable whose value contains a colon (:) separated list of paths which are searched for shared libraries.
Thus, if you want to run an executable that was produced in an earlier session, and you have not sourced the Intel Fortran startup shell script, do
$ export LD_LIBRARY_PATH=<path of directory containing libifport.so.5>
Just as the PATH environment variable is searched for executable files, it is the LD_LIBRARY_PATH variable whose value contains a colon (:) separated list of paths which are searched for shared libraries.
Thus, if you want to run an executable that was produced in an earlier session, and you have not sourced the Intel Fortran startup shell script, do
$ export LD_LIBRARY_PATH=<path of directory containing libifport.so.5>
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You came close to solving the problem yourself.
Just as the PATH environment variable is searched for executable files, it is the LD_LIBRARY_PATH variable whose value contains a colon (:) separated list of paths which are searched for shared libraries.
Thus, if you want to run an executable that was produced in an earlier session, and you have not sourced the Intel Fortran startup shell script, do
$ export LD_LIBRARY_PATH=<path of directory containing libifport.so.5>
Just as the PATH environment variable is searched for executable files, it is the LD_LIBRARY_PATH variable whose value contains a colon (:) separated list of paths which are searched for shared libraries.
Thus, if you want to run an executable that was produced in an earlier session, and you have not sourced the Intel Fortran startup shell script, do
$ export LD_LIBRARY_PATH=<path of directory containing libifport.so.5>
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hallo mecej4,
Thanks for the clue, it works perfectly now, i followed your first suggestion and added a *.conf Data referencing to Ifort/lib in /etc/ directory.
Regards
Soasil
Thanks for the clue, it works perfectly now, i followed your first suggestion and added a *.conf Data referencing to Ifort/lib in /etc/ directory.
Regards
Soasil

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page