On 9/12/07, Thomas Hruska <[EMAIL PROTECTED]> wrote:
> My knowledge of the Linux build system is somewhat limited when it comes
> to libraries and conflicts (most of it is usually 'automagically' worked
> out). I'm primarily a Windows developer and occasionally port stuff to
> Linux - that is, I know enough to break things but not necessarily fix
> them. AFAIK, .a is the rough equivalent of .lib and .so is the rough
> equivalent of .dll. In .lib files, they can either contain static code
> or links to external (.dll) files.
I thought that might be the case here also... but on my machine:
-rw-r--r-- 1 root root 229312 Jul 4 17:29 libpthread.a
-rw-r--r-- 1 root root 1296 Jul 4 17:29 libpthread_nonshared.a
-rw-r--r-- 1 root root 216 Jul 4 17:10 libpthread.so
I searched around a bit and could not find any explanation for what
libpthread_nonshared.a is for. Maybe its a library used only for
threaded programs that don't used shared mutexes or shared data.
*shrug*
To the original poster: you probably need not worry about the
libraries, just use -lpthread when you link and all should be well.
:-)
-- Brett
------------------------------------------------------------
"In the rhythm of music a secret is hidden;
If I were to divulge it, it would overturn the world."
-- Jelaleddin Rumi
