| 1 |
"John P. Burkett" <burkett@×××.edu> posted 4A2E900F.1070607@×××.edu, |
| 2 |
excerpted below, on Tue, 09 Jun 2009 12:38:39 -0400: |
| 3 |
|
| 4 |
> My first priority now is to respond to the error message mentioned in my |
| 5 |
> 9:11 a.m. note: |
| 6 |
> error while loading shared libraries: libgfortran.so.1: cannot open |
| 7 |
> shared object file: No such file or directory. |
| 8 |
> |
| 9 |
> Trying to see what related files are on my computer, I did "locate |
| 10 |
> libgfortran.so" and got the following response: |
| 11 |
> /usr/lib64/gcc/x86_64-pc-linux-gnu/4.3.2/32/libgfortran.so |
| 12 |
> /usr/lib64/gcc/x86_64-pc-linux-gnu/4.3.2/32/libgfortran.so.3.0.0 |
| 13 |
> /usr/lib64/gcc/x86_64-pc-linux-gnu/4.3.2/32/libgfortran.so.3 |
| 14 |
> /usr/lib64/gcc/x86_64-pc-linux-gnu/4.3.2/libgfortran.so |
| 15 |
> /usr/lib64/gcc/x86_64-pc-linux-gnu/4.3.2/libgfortran.so.3.0.0 |
| 16 |
> /usr/lib64/gcc/x86_64-pc-linux-gnu/4.3.2/libgfortran.so.3 |
| 17 |
> |
| 18 |
> To start R, octave, and other applications that look for |
| 19 |
> libgfortran.so.1, I presumably need to either reinstall libgfortran.so.1 |
| 20 |
> or rebuild the applications so they look for libgfortran.so.3. It's not |
| 21 |
> obvious to me which approach is better or how to implement either. |
| 22 |
|
| 23 |
With that info I can update my previous "caveat, no fortran here, but |
| 24 |
I'll try to help" recommendations. |
| 25 |
|
| 26 |
libgfortran.so.1 must have belonged to either an earlier gcc, or an |
| 27 |
alternate fortran provider. Assuming you want to use the gcc fortran |
| 28 |
version, now .so.3, you'll need to remerge anything depending on it. I'm |
| 29 |
not sure whether revdep-rebuild spots those dependencies or not. If it |
| 30 |
does (as I'd expect given the *.so), that's easy enough. If not, you may |
| 31 |
need to rebuild individual applications as you come across them, which |
| 32 |
could get difficult if it's not the application itself with the |
| 33 |
dependency issue, but one of its dependencies. |
| 34 |
|
| 35 |
But hopefully revdep-rebuild spots it. If your revdep-rebuild list is |
| 36 |
too long, try feeding it just that one library, like so: |
| 37 |
|
| 38 |
revdep-rebuild -L libgfortran.so.1 |
| 39 |
|
| 40 |
(You can of course use -p first, to get a list.) |
| 41 |
|
| 42 |
BTW, my lack of fortran experience is evident, as in the first reply I |
| 43 |
entirely missed that "g", and was calling it libfortran.so.1, not |
| 44 |
libgfortran.so.1. Hope that didn't cause any confusion, but FWIW, that |
| 45 |
caveat was there for a reason. =:^\ |
| 46 |
|
| 47 |
-- |
| 48 |
Duncan - List replies preferred. No HTML msgs. |
| 49 |
"Every nonfree program has a lord, a master -- |
| 50 |
and if you use the program, he is your master." Richard Stallman |
Archives