Recently changed the Linux system, changed from i686 to x86-64, resulting in the development of the time out of the original SDK in the 32-bit development tools. So, Bo Master found the following article, Bo Master Pro-Test practical:
How to develop and run 32-bit applications on 64-bit versions of Linux
The contents are as follows:
Many programmers (especially other companies) complain to me that their 32-bit software does not work properly on our 64-bit Linux systems, and that they are normal on their 32-bit machines, which is generally a good solution, usually 64-bit system installed without the default installation of the GLIBC 32-bit version, You can run a 32-bit application on a 64-bit Linux system without reinstalling the operating system by simply executing the following command.
Yum Install Glibc*.i686-y
If you are prompted to reduce a so file, install the corresponding library, If you are prompted for missing libz.so, install both the 64-bit and 32-bit versions of Libzip and Libzip-devel, and if prompted for a missing libssl.so, install the 64-bit and 32-bit versions of OpenSSL and Openssl-devel, as shown in the command line:
Yum Install libzip Libzip-devel-yyum install libzip.i686 libzip-devel.i686-yyum install OpenSSL Openssl-devel-yyum Inst All openssl.i686 openssl-devel.i686-y
If it appears: I386 architecture of input file XXX.O is incompatible with i386:x86-64
It is likely that the original compiled *.O file was not erased. Clear it and then edit it again ~
How to develop and run 32-bit applications on 64-bit versions of Linux