Running Rhel3 Binaries On Sles9

I am having an application which is currently available & used on RHEL3.
I am trying to use binaries & libraries compiled from this same source code base on SLES9 OS environment.

But I found that my application crashes in multiple places when there calls to glibc library functions such as strcmp, strchr, fwrite or flockfile from libpthread.so.0.

The SPECS of RHEL3 OS installation on which buildng my app is as below:
#:~>uname -a
Linux emeqagrdev5 2.4.21-32.0.1.ELsmp #1 SMP Tue May 17 17:52:23 EDT 2005 i686 i686 i386 GNU/Linux
#:~>cat /etc/redhat-release
Red Hat Enterprise Linux AS release 3 (Taroon Update 4)

Whereas, the SLES9 OS installation on which I am trying to run this build is as below:
#:~/log> uname -a
Linux nyl06a-7007a 2.6.5-7.283-bigsmp #1 SMP Wed Nov 29 16:55:53 UTC 2006 i686 athlon i386 GNU/Linux
#:~/log> cat /etc/SuSE-release
SUSE LINUX Enterprise Server 9 (i586)
VERSION = 9
PATCHLEVEL = 3

Quick comparison of core libraries showed following differences between RHEL3 & SLES9 installations:
Library RHEL3 (build env) SLES9 (Run env)
libstdc++.so.5 libstdc++-3.2.3-24 libstdc++-3.3.3-43.41
libgcc_s.so.1 libgcc-3.2.3-24 libgcc-3.3.3-43.41
libc.so.6 glibc-2.3.2-95.6 glibc-2.3.3-98.73

My queries are:
1) is my application crashing because of these library differences?
2) can I not use the binaries compiled on RHEL3 on SLES9?
3) can I use compat-glibc, etc packages on SLES9 & make RHEL3 build work - to resolve above library differences

Thanks.

Far from knowing but I suspect it is something to do with gcc's installed/used perhaps you can get this to assist better https://build.opensuse.org/

Don't really understand it all but from reading it will build a package for a variety of distro's, though don't see rhel3 but there is rhel5.

Thanks for this,
but I am not looking to create a package or distribtion of my application
I'm trying to run the binaries compiled on RHEL3 on SLES9 OS.

Don't think you can do that at all some things maybe distro specific. Different places for libs for example, different versions, different naming conventions.

Quite challanging. Either build your application two times and provide wrapper (on one SLES9 sles binary will be exectued on RHEL ...) Or build your application staticly. After that you should be able to run it everywhere. I believe that you can`t mangle two types of glibc, gcc, kernel version and using dynamic linking.

Oh sorry, You have only bins. Ok you are trapped You have coupled of options. Copy installation of RHEL into some directory and use chroot /rhel/ You should be able to run your application. Or use some virtualization tool. There is possibility to build all needed libs and put them into separate folder /opt/rhel/.... And run you application with LD_PRELOAD. Lot work to do