Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
libstdc++ is the standard c++ library. ie.. that's the definition of standard library functions for all code written in c++. the different versions are just that... versions, so you could need a v5 or v6 library these days depending on the code you are writing. generally you'd only require a version 5 library for older precompiled packages. anything new would just be linked against the standard version 6 object. they are often related to linker issues as that's the first and most important library for c++.
Did you compile the vsipl++ library on your system, or did you just download the binaries from some website? You may want compile it (the source code) on your local system as you did Qt.
I should further add that the last statement in your post does not offer many clues at all as to which example you are attempting to run. Is it a Qt example? Or something you created? If the latter, it might be helpful to see how you compiled the executable example1.
Last edited by dwhitney67; 12-07-2007 at 01:31 AM.
Here's a high-level snapshot of the most important ideas here ...
All programs rely upon the existence of many libraries, which contain pre-written, presumably well-tested subroutines that the programs can therefore simply "rely upon."
In the Linux/Unix systems, you can easily have multiple versions of the same library installed at the same time. Through a simple system of file-names ("that's what the '.6' is for..."), the libraries can be found without conflict by the programs that need them. Programs can be very-generic or very-specific as to their requirements. The library files themselves also contain version-information so the linker can be sure that the library-file it has found is compatible.
One program might compile just fine, because the version it needs is available, while another program doesn't.
A "broken link" occurs when the linker cannot find a compatible subroutine in a compatible library to fulfill the program's stated requirements.