I would attempt a little "look before you leap" on such a file. Use commands such as
You might get some idea of what it is and what 32 bit libraries it depends on. The installation process may be hard to clean up if it fails due to missing libraries. If you can install the required libraries ahead of time, that tends to be cleaner than running the installer up to the point of failure, deducing which missing library was at fault, installing that library and repeating.
I would expect a .bin file to usually defeat my limited skills of "look before you leap". Many are weird mixes of shell script and compressed data. So I might go ahead with try it and fix each failure after look ahead fails. But I'd at least try some look ahead first to see if the cleaner approach can work.