Most versions of Linux that have a 64-bit build also create a 32-bit build, and almost all libraries are available for both, so you only need to install the corresponding 32-bit libraries in parallel with 64-bit. The configuration of the paths is no different from the configuration with 64 or 32 bits in most cases. There may be several libraries that have problems, but you really need to look for them. All major packages will have libraries that work with 32- and 64-bit versions of libraries installed at the same time.
When it comes to “volume libc”, etc., this is a more complicated question, since it will really depend on what your clients have on their machines, and it is unlikely that you can dictate that they should use one of Debian , RedHat or SuSE - they will be very versed in using what they use. Using a "too old" library is as bad as using a "too new" library. The usual solution for this is to create several versions, one for the selected version of RedHat (and this should work with several stages of a newer / older version, usually, as well as Fedora versions in the same range), the Debian version and SuSE version, possibly one or two distributions.
And yes, at that moment you probably want to set up an assembly machine with several virtual machines on it so that you don't have to have 3, 5, or 12 physical machines.
source share