libXaw.so.6 => /usr/i486-linux-libc5/lib/libXaw.so.6 (0x4000c000)
At a guess these symbols have something to do with the libc6 loader. Why does is not work under SuSE but does under Red Hat?
Compare /etc/ld.so.conf of those two systems. It's the file that configures the dynamic loader. Make shure that /usr/i486-linux-libc5/lib does appear in /etc/ld.so.conf on SuSE 6.3. That way the linker will try the libc5 libs before their glibc2 counterpart. AFAIK, the dynamic linker can distinguish between those two versions, so it should not create a problem.
Thanks for your answer! But it doesn't work :-( I never touched that config file, so contents are as for SuSE 6.3: /lib-aout /usr/X11R6/lib/Xaw95 /usr/X11R6/lib/Xaw3d /usr/X11R6/lib /usr/X386/lib /usr/i486-linux/lib /usr/i486-linux-libc5/lib /usr/i486-linux-libc5/lib=libc5 /usr/i486-linux-libc6/lib=libc6 /usr/i486-linuxaout/lib /usr/local/lib /usr/local/X11R6/lib /usr/openwin/lib /opt/kde/lib /opt/gnome/lib Save for the =libc5, the line is there. I tried a few variations (running ldconfig after each change), no change. Doesn't load. The RH6.0 system has: /usr/lib /usr/i486-linux-libc5/lib /usr/X11R6/lib /usr/pukeko/lib /usr/local/lib /usr/local/RH4.2/lib /usr/openwin/lib The binaries execute on this sytem.
But do yourself a favour and either get glibc2 based versions of those programs or recompile them yourself. Running libc5 based programs on a glibc2 system just wastes memory, as two incompatible versions of the C library have to be loaded into memory.
Yes I know - but I don't use them often and compiling takes time... Volker -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/