QuantumATK Forum

QuantumATK => Installation and License Questions => Topic started by: Anders Blom on December 11, 2008, 15:56

Title: FAQ: libg2c.so.0: cannot open shared object file: No such file or directory
Post by: Anders Blom on December 11, 2008, 15:56
One of the most common error messages when trying to start VNL/ATK is

Quote
'Not available', 'libg2c.so.0: cannot open shared object file: No such file or directory'

Quite obviously, this is because the library libg2c is missing. In many cases it is straightforward to install this library from the relevant package/software/update manager (look for libg2c, libf2c or g77), but one needs to pay some attention to which version to install, especially on 64-bit platforms, since VNL is a 32-bit application and therefore needs the corresponding 32-bit g2c library.

Some more detailed advice on specific platform will appear in further posts on this thread!

In general, a good resource for locating missing libraries to download is http://rpm.pbone.net/ (click "Search", then go to "Advanced Search" to be able to select distribution, otherwise you usually get way too many results in the search).
Title: CentOS 4.0/5.1 and RHEL 5
Post by: Anders Blom on December 11, 2008, 15:59
Either you can use the software manager to locate and install the needed package (search for libg2c.so), or you can download the needed packages manually:
Code
rpm --install libf2c-3.4.6-11.i386.rpm 

Title: Novell Linux Desktop 9 SP3 x86
Post by: Anders Blom on December 11, 2008, 16:10
In Software Management mark the package "gcc-g77" for install (need Install CD1).

This will install the following 3 packages:
and the problem should be resolved.
Title: SUSE Linux Enterprise Desktop
Post by: Anders Blom on December 11, 2008, 16:19
Install the GNU Fortran Compiler Runtime Library (containing libg2c.so) to fix the issue.

The library is not located on the installation CDs, so instead use http://rpm.pbone.net to locate a 32-bit version of the library.
Code
rpm --install libg2c33-3.3.3-42.5.i586.rpm
Title: Re: FAQ: libg2c.so.0: cannot open shared object file: No such file or directory
Post by: Anders Blom on December 11, 2008, 16:21
Sometimes, after installing the library, you need to link VNL to it:

Go to the VNL lib directory and give the command
Code
ln -s /usr/lib/libg2c.so.0.0.0 libg2c.so.0
(or the appropriate location of the lib2c.so.* files).
Title: Ubuntu Linux
Post by: artitw on March 5, 2009, 23:43
Missing libg2c.so.0 can be fixed by installing libg2c0 from the Synaptic Package Manager or

Code
sudo apt-get install libg2c0
Title: Re: FAQ: libg2c.so.0: cannot open shared object file: No such file or directory
Post by: srdguezb on March 8, 2010, 12:42
I need to obtain libg2c in Ubuntu 9.10

Any idea about it?

Thank you
Title: Re: FAQ: libg2c.so.0: cannot open shared object file: No such file or directory
Post by: Anders Blom on March 8, 2010, 12:52
See http://quantumwise.com/forum/index.php?topic=432.0. Hope that helps
Title: Re: FAQ: libg2c.so.0: cannot open shared object file: No such file or directory
Post by: lystor on June 2, 2010, 20:26
I need to obtain libg2c in Ubuntu 9.10
Any idea about it?

You can download it for Ubuntu:
http://packages.acl.org.ua/en/search/name/libg2c0
Title: Re: FAQ: libg2c.so.0: cannot open shared object file: No such file or directory
Post by: milenko76 on June 14, 2010, 11:42
I need libf2c for Ubuntu 9.04.Where to find it?
Title: Re: FAQ: libg2c.so.0: cannot open shared object file: No such file or directory
Post by: milenko76 on June 14, 2010, 11:47
I have downloaded from the link above but computer tells me that the newer version is already installed.
./xtramp: error while loading shared libraries: libf2c.so.2: cannot open shared object file: No such file or directory
Still I get this when I try to run program.
What should I do?
Title: Re: FAQ: libg2c.so.0: cannot open shared object file: No such file or directory
Post by: bhushan_bhujang on January 4, 2011, 13:30
I got an indirect alternative solution to this problem in ubuntu (jaunty)
I downloaded f2c-20000510-5.i386.rpm  (since i could not find the same 32-bit package in .deb) from rpm site then converted .rpm to .deb by alien, i.e
in the terminal type
alien -d f2c-20000510-5.i386.rpm
then execute your problem. It will fix the error.