I have no software development knowledge and therefore these error messages
are somehow cryptic to me. But I see, that libIlmThread.so does not refer
(link?) to pthread.so at all:
You're doing fine for a non-dev. Keep it up ;-)
openexr-1.6 > ldd ../../lib/libIlmThread.so
libIex.so.6 => /usr/struct/pack/openexr-1.6/lib/libIex.so.6
(0x00002ae626943000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00002ae626b60000)
libm.so.6 => /lib64/libm.so.6 (0x00002ae626e80000)
libc.so.6 => /lib64/libc.so.6 (0x00002ae627104000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00002ae62745a000)
/lib64/ld-linux-x86-64.so.2 (0x00000031e8c00000)
openexr-1.6 >
Could that be the problem and is there a way to fix it?
That's the issue; the tough question is two-part: (1) where did the
process screw up exactly --> (2) once we know the 'where' in more
detail, what can we do to kick it into cooperating.
... oh dang. dang. dang. I forgot. Had this issue already /several/
times in a row with other folks on Linux (it's due to the Linux
package installer systems being geared a bit too much to 'using' IMO;
creating a bit of a bother when 'users' take the obvious step thinking
"heck, what's so hard in typing './configure' and 'make install'
anyway?" And then they get a nasty surprise they should _not_ have
got. I got a few nasty surprises myself when I returned to this
platform after several years. But I digress.)
The thing to check:
your system has a 'package installer' of some sort where you select
the 'packages' you want installed on your system, e.g. 'pthreads',
'gcc compiler', 'open office', etc.etc.
Now here's the nasty bit: I bet myself a bottle of good single malt
you've got 'pthreads' or 'libpthreads' or whatever they'll call it in
your package manager (e.g. on Ubuntu: System>Administration>Synaptic
Package Manager) checked as 'already installed' in that manager
(that's why you could find that libpthreads.so loadable library) but
you (and this is my bet) do /not/ have the 'libpthreads-dev' package
installed /as well/ (should be called the same with ' dev' or '-dev'
something appended to the name). Maybe it even comes with a
description where it says that the 'dev' package will install the
'header files'. Tick that one and install, because /that's/ what
./configure is looking for too: to build a piece of software which
depends on a library of any sort, in Linux nowadays you need both the
'libraryXYZ' _plus_ the 'libraryXYZ-dev' packages installed or you get
a situation very much like this one: everything looks good, meanwhile
nothing builds, linker errors galore and you're left pulling your
hair.
If that 'pthreads-dev' package was not yet installed, and now that it
is, rerun all ./configure scripts (IlmBase, OpenEXR, etc.) and 'make',
'make check' and 'make install' commands like you did before, so that
the newfound pthreads 'header files' can be detected by the configure
scripts and alter the OpenEXR build instructions accordingly.
... do I win my bet or did I loose? ;-)