I don't recall seeing this go by in the forum, but there's no guarantee I was
always paying attention.
We are trying to move most of our Linux S390 systems from 2.4.7 to 2.4.17. We
started with a Suse 7.2 as a base. The upgrades were done, with a lot of help
from others on the forum, as recommended in developerworks. By that I mean we
upgraded the kernel sources,
added the timer patch,
kerntypes,
the 31 bit qeth module,
binutils 2.12.90.0.14,
gcc 3.1.1,
glibc 2.2.5,
modutils 2.4.7,
s390-tools 1.1.3.
After fighting through that I was too bushed to bother with gdb.
Now as we try to upgrade production systems, we are being hit by various
products that fail to run due to the following:
"error while loading shared library: libc.so.6 : cannot open shared
object file: No such file or directory"
The above message is an approximation, I let the exact messages get away when
backing out of 2.4.17.
Anyway, /lib/libc.so.6 is a link to /lib/libc-2.2.5.so.
We are getting this with WAS 4.0, Tomcat 4.0, IASP 2.0, ....
Interestingly, when tracing most of them, it turns out that they were all
running java when they failed, so maybe it's only java that's a problem.
Dumping a trace here is a bit large, but after java does a fork/execve, it
successfully opens and reads from /lib/libc.so.6, closes it, and tries
/usr/lib/libc.so.6 which doesn't exist, although in desperation we copied it
there just to see what would happen. It didn't help. Typically the execve is for
/usr/bin/expr or /bin/ls, or something that works all time except when done by
java.
Java is IBMJava2-SDK-13.s390.
Anyone have any ideas???
Steve Arden
[EMAIL PROTECTED]
IBM-Global Services @ Lucent
(630)979-7124
