I took a look at what the various shared libs for
InsightII show in terms of errno symbols and found that for the
files with errno I see...
nm libcblib.so | grep errno
U errno@@GLIBC_2.0
U __errno_location@@GLIBC_2.0
ldd libcblib.so
linux-gate.so.1 => (0x007c0000)
libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0x00111000)
libm.so.6 => /lib/libm.so.6 (0x00477000)
libc.so.6 => /lib/libc.so.6 (0x00156000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00462000)
/lib/ld-linux.so.2 (0x007c1000)
but for others I only see __errno_location...
nm libchemnote.so | grep errno
U __errno_location@@GLIBC_2.0
ldd libchemnote.so
linux-gate.so.1 => (0x007c0000)
libstdc++-libc6.2-2.so.3 => /usr/lib/libstdc++-libc6.2-2.so.3 (0x00111000)
libm.so.6 => /lib/libm.so.6 (0x00156000)
libc.so.6 => /lib/libc.so.6 (0x0038f000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x0017b000)
/lib/ld-linux.so.2 (0x007c1000)
Jakub, would it be a reasonable from this observation to draw the
conclusion that the bulk of InsightII was built on a properly
configured build machine but that specific libraries must be
stale old copies from much older build? Otherwise it doesn't make
much sense as to why libcblib.so and libchemnote.so shared the
same libraries in their linkage yet one has both the incorrect and
correct errno symbol in it.
Jack
