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