SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Could I possibly impose upon you to post the same snippet of your sucessful make? I think I've spotted what was the problem but would like to know what the sucessfull make looks like. The same part you posted... Thanks.. If not, no biggie.
Yea, that's what I expected to see. Don't you see a difference?
For some reason it wasn't searching /usr/X11R6 as the lack of a linker flag with your first make output shows. But this time around, it's in there, therefore, it picked up on your libs.
CPPFLAGS="-L/usr/X11R6/lib" make (that or tag it to ./configure, or both)
would have fixed your problem. Do a ./configure --help to make sure. It's either CPPFLAGS or CXXFLAGS but I think it's the former. CXXFLAGS should be for specifying includes and CPPFLAGS for libs. Just keep that in mind if anything like this happens again and you know the libs are on your system. That's what those variables are for. To give it a nudge in the right direction if need be.
Do a configure --help. I'm a little fuzzy from pain pills and don't have a linux box at the moment.. CXXFLAGS are used for optimization I believe, not includes. It's something like that... configure will tell you.
As for your final question about your library path, this is what I would do. Look in /etc/profile.d/ and have a peek at the java sh file in there. I'm assuming you have java installed. I'd make a "geda.sh" script to put in /etc/profile.d that does the same thing.
But you probably should add /opt/geda/lib (or whatever) to ld.so.conf anyway. If you find man pages in /opt/geda, you could define that directory with man.conf... ect... ect...
Well spotted. I think it's LDFLAGS="-L/usr/X11R6/lib" ./configure, since it's the linker that's having problems. Anyway, to do that for everything? That'd be a nuisance.
Glad it's all worked out, though!
As for LD_LIBRARY_PATH ... mostly you only need that stuff during compilation, for dynamic linking at run time ... once you've run ld.so.conf with $LD_LIBRARY_PATH="/opt/geda/lib" or similar, the necessary shared libraries will be linked properly, so you shouldn't need to do anything else to make it work.
If you do, then you'll be ok with just adding the library path to ld.so.conf and being done with it.
For packaging, however, jong might be on to something by putting any global environment variables into a profile script and packaging that up too.