Skip to main content
Skip to main content

Compiling with Arm

Compile with ARM

This topic is about how to compile Doris on the ARM64 platform.

Note that this document is intended as a guide only. Other errors may occur when compiling in different environments. Feel free to issue Doris with problems or solutions.

Hardware/OS environment​

  1. KylinOS:
$> cat /etc/.kyinfo
time=2020-07-11 17:16:54
dist_id=Kylin-Server-10-SP1-Release-Build04-20200711-arm64-2020-07-11 17:16:54

$> cat /proc/cpuinfo
model name : Phytium,FT-2000+/64
  1. CentOS 7.9 or higher
$> lsb_release -a
LSB Version: :core-4.1-aarch64:core-4.1-noarch
Distributor ID: CentOS
Description: CentOS Linux release 7.9.2009 (AltArch)
Release: 7.9.2009
Codename: AltArch

Software Environment​

Software Environment List​

Component NameComponent Version
Commonly Used Components
yum install or apt-get install

Software Environment Installation Command​

  1. Create root directories for pacakges
# Create root directory for software download and installation packages
mkdir /opt/tools
# Create root directory for software installation
mkdir /opt/software

  1. Installing dependencies
  • Git
  # yum install (save the trouble of compilation)
yum install -y git
  • JDK8 (2 methods)
  # 1. yum install, which can avoid additional download and configuration. Installing the devel package is to get tools such as the jps command.
yum install -y java-1.8.0-openjdk java-1.8.0-openjdk-devel

# 2. Download the installation package of the arm64 architecture, decompress it, and configure the environment variables.
cd /opt/tools
wget && \
tar -zxvf jdk-8u291-linux-aarch64.tar.gz && \
mv jdk1.8.0_291 /opt/software/jdk8
  • Maven
  cd /opt/tools
# Download the wget tool, decompress it, and configure the environment variables.
wget && \
tar -zxvf apache-maven-3.6.3-bin.tar.gz && \
mv apache-maven-3.6.3 /opt/software/maven
  • NodeJS
  cd /opt/tools
# Download the installation package of the arm64 architecture
wget && \
tar -xvf node-v16.3.0-linux-arm64.tar.xz && \
mv node-v16.3.0-linux-arm64 /opt/software/nodejs
  • LDB-Toolchain
  cd /opt/tools
# Download LDB-Toolchain ARM version
wget && \
sh /opt/software/ldb_toolchain/

  1. Configure environment variables
# Configure environment variables
vim /etc/profile.d/
export JAVA_HOME=/opt/software/jdk8
export MAVEN_HOME=/opt/software/maven
export NODE_JS_HOME=/opt/software/nodejs
export LDB_HOME=/opt/software/ldb_toolchain

# Save, exit, and refresh environment variables
source /etc/profile.d/

# Test
java -version
> java version "1.8.0_291"
mvn -version
> Apache Maven 3.6.3
node --version
> v16.3.0
gcc --version
> gcc-11

  1. Install other environments and components
# Install required system packages
sudo yum install -y byacc patch automake libtool make which file ncurses-devel gettext-devel unzip bzip2 bison zip util-linux wget git python2

# Install autoconf-2.69
cd /opt/tools
wget && \
tar zxf autoconf-2.69.tar.gz && \
mv autoconf-2.69 /opt/software/autoconf && \
cd /opt/software/autoconf && \
./configure && \
make && \
make install



Currently the only recommended method for ARM environments is to compile with ldb-toolchain, which works for commit 7f3564 for Doris releases after that.


See Compilation with LDB toolchain for the steps then.

The jdk and nodejs should be replaced with the corresponding aarch64 versions:

  1. Java8-aarch64
  2. Node v16.3.0-aarch64

If you have problems compiling with the downloaded precompiled third-party libraries, please use tools/ to compile them by yourself. When compiling the thirdparty library, use gcc:


When compiling Doris on ARM platforms, please disable AVX2 and LIBUNWIND tripartite libraries:

export USE_AVX2=OFF

If you still encounter problems when compiling or starting, please consult the FAQ. If there is no relevant solution, feel free to raise an issue.


Problems about Compiling​

  1. File not found when compiling the third-party library libhdfs3.a.

    • Problem Description

      During the compilation and installation process, the following error occurrs:

      not found lib/libhdfs3.a file or directory

    • Cause

      The third-party library dependency is improperly downloaded.

    • Solution

      • Use a third-party download repository
sh /opt/doris/thirdparty/

REPOSITORY_URL contains all third-party library source packages and their historical versions.

  1. python command not found

    • Problem Description

      • An exception is thrown when executing

        /opt/doris/ line 46: python: command not found

        Python 2.7.18

    • Cause

      The system uses python2.7, python3.6, python2, python3 by default to execute python commands. Doris only requires python 2.7+ to install dependencies, so you just need to add a command python to connect.

    • Solution

      Establish a soft link to the python command in \usr\bin

      # View python installation directory
whereis python
# Establish soft connection
sudo ln -s /usr/bin/python2.7 /usr/bin/python
  1. There is no output directory after compilation

    • Problem Description

      • Cannot find the output folder in the directory after the execution of
    • Cause

      Compilation fails. Try again.

    • Solution

      sh --clean
  1. spark-dpp compilation fails

    • Problem Description

      • After compiling, compiling to Spark-DPP fails with an error

        Failed to execute goal on project spark-dpp

    • Cause

      This error message is caused by download failure (connection to the central repository fails).

      Could not transfer artifact org.apache.spark:spark-sql_2.12:jar:2.4.6 from/to central ( Transfer failed for https://repo Unknown host

    • Solution

      • Rebuild
  2. No space left, compilation fails

    • Problem Description

      • Failed to build CXX object during compilation, error message showing no space left

        fatal error: error writing to /tmp/ccKn4nPK.s: No space left on device

        1112 | } // namespace doris::vectorized

        compilation terminated.

    • Cause

      Insufficient free space on the device

    • Solution

      Expand the free space on the device by deleting files you don't need, etc.

  3. Could not find pkg.m4 file in pkg.config

    • Problem Description

      • A "file not found" error occurs during compilation:

        Couldn't find pkg.m4 from pkg-config. Install the appropriate package for your distribution or set ACLOCAL_PATH to the directory containing pkg.m4.

    • Cause

      There is something wrong with the compilation of the third-party library libxml2 .

      Possible Reasons:

      1. An exception occurs when the Ubuntu system loads the environment variables so the index under the ldb directory is not successfully loaded.
      2. The retrieval of environment variables during libxml2 compilation fails, so the ldb/aclocal directory is not retrieved.
    • Solution

      Copy the pkg.m4 file in the ldb/aclocal directory into the libxml2/m4 directory, and recompile the third-party library.

      cp /opt/software/ldb_toolchain/share/aclocal/pkg.m4 /opt/incubator-doris/thirdparty/src/libxml2-v2.9.10/m4
sh /opt/incubator-doris/thirdparty/
  1. Failed to execute test CURL_HAS_TLS_PROXY

    • Problem Description

      • An error is reported during the compilation process of the third-party package:

        -- Performing Test CURL_HAS_TLS_PROXY - Failed

        CMake Error at cmake/dependencies.cmake:15 (get_property):

        INTERFACE_LIBRARY targets may only have whitelisted properties. The property "LINK_LIBRARIES_ALL" is not allowed.

      • The log shows: curl No such file or directory

        fatal error: curl/curl.h: No such file or directory

        2 | #include <curl/curl.h>

        compilation terminated.

        ninja: build stopped: subcommand failed.

    • Cause

      There is an error in the compilation environment. The gcc is of version 9.3.0 that comes with the system, so it is not compiled with ldb, so you need to configure the ldb environment variable.

    • Solution

      Configure ldb environment variables

      # Configure environment variables
vim /etc/profile.d/
export LDB_HOME=/opt/software/ldb_toolchain
export PATH=$LDB_HOME/bin:$PATH
# Save, exit, and refresh environment variables
source /etc/profile.d/
# Test
gcc --version
> gcc-11
  1. The compilation process aborts with the words "ninja failed with: signal: killed".

    • Problem Description

      BE or thirdparty failed in the middle of compilation with a message containing

      ninja failed with: signal: killed

    • Cause

      Insufficient memory on the machine

    • Solution

      Switch to a machine with more memory(at least 16GB) for compilation

Problems about Starting​

  1. Failed to start FE, transaction error -20

    • Problem Description

      When starting FE, a transaction error 20 is reported with UNKNOWN status.

      [BDBEnvironment.setup():198] error to open replicated environment. will exit. (JE 18.3.12) Problem closing transaction 20. The current state is:UNKNOWN. The node transitioned to this state at:Fri Apr 22 12:48:08 CST 2022

    • Cause

      Insufficient hard disk space

    • Solution

      Free up hard disk space or mount a new hard disk

  2. Abnormal BDB environment setting, disk search error

    • Problem Description

      An exception is reported when starting FE after migrating the drive letter where FE is located

      2022-04-22 16:21:44,092 ERROR (MASTER|1) [] catch an exception when setup bdb environment. will exit. (JE 18.3.12) Disk usage is not within je.maxDisk or je.freeDisk limits and write operations are prohibited: maxDiskLimit=0 freeDiskLimit=5,368,709,120 adjustedMaxDiskLimit=0 maxDiskOverage=0 freeDiskShortage=1,536,552,960 diskFreeSpace=3,832,156,160 availableLogSize=-1,536,552,960 totalLogSize=4,665 activeLogSize=4,665 reservedLogSize=0 protectedLogSize=0 protectedLogSizeMap={}

    • Cause

      FE has been migrated to another location, which doesn't match the hard disk information stored in the metadata; or the hard disk is damaged or not mounted

    • Solution

      • Check if the hard disk is normal, initialized and mounted correctly
      • Fix FE metadata
      • If it is a test machine, you can delete the metadata directory and restart
  3. BE coredumps at startup and the word or glibc-compatibility/ is visible in the core stack.

    • Problem cause The current machine glibc version is too low. You can be confirmed with ldd --version. This may occur if the version is less than 2.27.

    • Solution Recompile the BE, with environment variables added:


Other Component Issues​

  • Problem Description

    The follow error prompts are all due to one root cause.

    • bison related
      1. fseterr.c error when installing bison-3.0.4
    • flex related
      1. flex command not found
    • cmake related
      1. cmake command not found
      2. cmake cannot find the dependent library
      3. cmake cannot find CMAKE_ROOT
      4. Compiler set not found in cmake environment variable CXX
    • boost related
      1. Boost.Build build engine failed
    • mysql related
      1. Could not find mysql client dependency a file
    • gcc related
      1. GCC version requires 11+
  • Cause

    Not compiled with ldb-toolchain

  • Solution

    • Check if the ldb-toolchain environment variable is configured
    • Check that the gcc version matches the one recommended in the compile-with-ldb-toolchain documentation.
    • Delete the ldb directory after the script is executed, re-execute and configure the environment variables, and verify the gcc version