Porting Software from x86 to Kunpeng Linux: Compiled vs Interpreted Languages

From today we will provide a series of articles on porting software from x86 Linux to Kunpeng Linux, covering preparation of the compilation environment, scripts, source code modifications, and handling issues encountered during the migration.

Programming languages can be divided into two categories based on translation method: compiled languages and interpreted languages.

1. Compiled languages

Typical examples are C and C++. The compilation process produces machine instructions that the operating system loads into memory and the CPU executes directly.

2. Interpreted languages

Typical examples are Java and Python. Their source code is compiled into platform‑independent bytecode, which is then executed by a virtual machine that abstracts away platform differences.

3. Applications built with compiled languages

Applications written in C/C++ produce executables that depend on CPU architecture. Therefore, binaries compiled for x86 cannot run directly on Kunpeng servers and must be re‑compiled for the target architecture. Detailed solutions to common porting problems will be provided in subsequent articles.

4. Applications built with interpreted languages

Programs written in Java or Python are architecture‑independent; they can be deployed on Kunpeng servers without modification or recompilation. However, if a Java JAR contains native C/C++ libraries (SO files), those libraries must be re‑compiled for Kunpeng, and the JAR repackaged with the new libraries.

Further reading

Porting C/C++ programs requires a suitable compiler; GCC 7.3 or newer (minimum 4.8.5) is recommended.

GCC 7.3 download: http://ftp.gnu.org/gnu/gcc/gcc-7.3.0/

Installation guide: https://gcc.gnu.org/install/