It doesn't fit or explain the error messages you posted, but I think you should start by finding and installing the 32-bit RPMs that contain the three .so files reported by ldd as not found.
You should also use the file command on the relevant files to try to find the explanation for the error messages you posted:
file -L /tmp/eiecho
file -L /lib/libm.so.6
Originally Posted by CowboyRT
I am attempting to install a 32-bit application and I'm getting the error below during the application install.
Does this installer recompile the application from source? And if so, what about the application is "32-bit".
The error messages you posted seem unlikely for most situations. One situation that fits those error messages is an application designed to recompile during install, but using build scripts that are incompatible with a 64-bit RH based distribution (maybe it wouldn't recompile correctly on any 64-bit distribution, or maybe it recompiles correctly as a 64-bit application on Debian based distributions but not RH based).
If that is the case, there is someplace (such as an environment variable) where you can inject the -m32 option to make it recompile as 32-bit instead of recompiling (as I'm guessing it does now) as broken 64-bit. Without more details of what the installer is doing, I don't want to make many guesses about how to put in the -m32. In the simplest cases that would be done by using the command
before launching the installer (from the same shell in which you did that export). But many installers are different and could require a different way to inject -m32 (or I might be entirely wrong in my guess that anything is getting compiled).