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.
in short, I have the feeling my linker does not look at lib*.a libraries.
This is the problem:
#g++-3.2 -lGL -lGLU -lglut -L../Meshlib/Lib -lmesh main.o load.o glnav.o glnavapp.o waypoints.o fonts.o
glnavapp.o: In function `GlNavApp::debug(int)':
glnavapp.o(.text+0x1d00): undefined reference to `getFrustumGL(t_3DVector&, t_3DVector&, t_3DVector&, t_3DVector&, t_3DVector&, t_3DVector&)'
The function 'getFrustumGL' is located in the file support-opengl.o, which in turn is located in the library libmesh.a. When I take the -Lpath option out, the linker complains (of course) about not finding the library libmesh.a. When I link the program with support-opengl.o (which I have present beside the library), no error comes up.
That leads me to the assumption that the linker does not search the library correctly. Beside, the GL library only exists as libGL.so, not as static libGL.a. Does that mean the linker only tries to link to shared libraries?
Does anybody have an idea?
P.S.: g++ 3.2.1 gcc 3.2.1
The library is compiled with the same version.
Debian 3.0 testing/unstable, because I need glibc 2.3 for libmesh.a
No, I don't think so. ldconfig is for dynamic libraries, and furthermore just accessible as root. In my case, I have the static library libmesh.a, which is not installed in a system path (that's why I supply the exact path with the -L option), and I don't want it to be in a system path. It's just intended for the same user who compiles the program.