Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
That is an error from the linker, telling you that it cannot find a library it is looking for, called libg2c.so or something very similar to that.
Verify that the library it seeks is actually on the machine somewhere, and add a linker include argument directing the linker where to look for it.
If there is a ./configure script you are using first, before the 'make', you can probably add an argument to that script when you execute it, which will be passed on to the linker.
Cheers,
Sasha
Last edited by GrapefruiTgirl; 06-24-2009 at 03:22 PM.
Well, if you use a configure script first, then type `configure --help` and near the bottom of the output, it will show (or it should show) how to add a location for the linker to look in for the libraries it wants. Something like:
EXTRA_LIBS=-L/usr/local/lib
or
EXTRA_LIB=-l/usr/lib/libg2c.so
Though these are rough examples; you can also "export" these type of arguments, so you don't need to give them with the configure/make commands.
To see if a library actually exists on the machine, try the `locate` or `find` commands.
# Make file for r8s # Updated April 2003 for Linux and Mac OS 10.2. No other builds currently supported #
FC = g77 # Fortran compiler; standard on Linux, may have to go fetch this on OS X! (get it from Fink) CC = gcc # GNU C compiler LIBS = -lg2c -lm # FORTRAN to C library, and standard C library LPATH = -L/sw/lib # This is the directory where Mac's Fink stuck the g2c library #CFLAGS = -g -std=c99 -pedantic # for debugging, etc. CFLAGS = # usual case
I edited LPATH to equal -L/usr/lib, which is where libg2c.so and libm.so can be found. It still gives the same error, though...
Yes, you probably *could* edit the makefile, either to add/adjust the LIBS path, and/or maybe the very gcc command that failed, you could put a linker search path there.
If you do, keep comments anywhere you change something so if you get mixed up, you know what you've done. Of course, you must have an archive of the sourcecode for this anyway, just in case.
Depending how long/complex the Makefile is, it may take a while to figure out all the locations!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.