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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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:
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!