Skip to main content
Skip to main content

Compling on MacOS

Compile on MacOS

This guide is about how to compile Doris on MacOS.


  • MacOS 12 (Monterey) or later (Both Intel and Apple Silicon are supported.)
  • Homebrew

Compile source code​

  1. Install dependencies using Homebrew
brew install automake autoconf libtool pkg-config texinfo coreutils gnu-getopt \
python@3 cmake ninja ccache bison byacc gettext wget pcre maven llvm@16 openjdk@11 npm

On MacOS, since Homebrew does not provide an installation package for JDK8, JDK11 is used here instead. Alternatively, you can manually download and install JDK8.

  1. Compile source code

The first step of compiling Doris is to download and compile third-party libraries. You can download the pre-compiled versions of third-party libraries provided by the Doris community. Please refer to the instructions below for downloading pre-compiled third-party libraries to speed up the build process.


  1. Increase file descriptors limit
# Increase the file descriptor limit using the ulimit command.
ulimit -n 65536

# Check if the change is effective.
$ ulimit -n

# Add the configuration to your startup script so that you do not have to set it again every time you open a new terminal session.
# If you are using bash, execute the following statement:
echo 'ulimit -n 65536' >>~/.bashrc
# If you are using zsh, execute the following statement:
echo 'ulimit -n 65536' >>~/.zshrc
  1. Start BE
cd output/be/bin
./ --daemon
  1. Start FE
cd output/fe/bin
./ --daemon

Speed up by using pre-compiled third-party libraries​

Download the pre-compiled third-party libraries from Apache Doris Third Party Prebuilt. Refer to the command below:

cd thirdparty
rm -rf installed

# Intel chip
curl -L \
-o - | tar -Jxf -

# Apple Silicon chip
curl -L \
-o - | tar -Jxf -

# Check if protoc and thrift functions normally
cd installed/bin

./protoc --version
./thrift --version

When running protoc and thrift, you may encounter an issue where the binary cannot be opened due to developer verification. To resolve this, you can go to "Security & Privacy" settings. In the "General" tab, click on the "Open Anyway" button to confirm your intent to open the binary. Refer to: