Building

console sudo apt update && \ sudo apt install -y git

You will need the command line tools for Xcode and Homebrew package, if you don't have it you can install it by typing:

console xcode-select --install

and then:

console /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

Assure that brew is properly installed, by checking its version:

console brew --version

*The described instructions have been verified for 4.0.11 brew version.

Then you will be ready for installing git and other required tools:

console brew update && \ brew install git

• Install required packages

console sudo apt update && \ sudo apt install -y curl \ ca-certificates \ gnupg \ lsb-release

• Make docker packages available

console curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg && \ echo \ "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu \ $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

• Install docker packages

console sudo apt-get update && \ sudo apt-get install docker-ce docker-ce-cli containerd.io

• Check if Docker is properly installed (version can be different):

console sudo docker --version

• To make calling docker command without sudo possible type:

console sudo groupadd docker

Even if group docker already exists type then:

console sudo usermod -aG docker $USER && \ newgrp docker

• Check if running docker images without sudo works properly:

console docker run hello-world

For more details and other instructions see

docker.com

You can find the up-to-date instructions on https://docs.docker.com/desktop/install/mac-install/

To make this process simpler below is an example of installation for Mac with the Intel chip:

Download the installer:

console curl -o Docker.dmg "https://desktop.docker.com/mac/main/amd64/Docker.dmg?utm_source=docker&utm_medium=webreferral&utm_campaign=docs-driven-download-mac-amd64"

Run the following commands to install Docker:

console sudo hdiutil attach Docker.dmg && \ sudo /Volumes/Docker/Docker.app/Contents/MacOS/install && \ sudo hdiutil detach /Volumes/Docker

Then add the path to docker binaries to the PATH environment variable:

console export PATH="/Applications/Docker.app/Contents/Resources/bin:$PATH"

It's recommended to place it in .zshrc startup script to export it every time during startup:

console echo 'export PATH=/Applications/Docker.app/Contents/Resources/bin:$PATH' >> $HOME/.zshrc

• Check if Docker is properly installed by checking its version:

console docker --version

• Check if running docker images without sudo works properly:

console docker run hello-world

• If you see the following error: ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. you can try to install colima and check once again:

console brew install colima && \ colima start

console sudo apt update && \ sudo apt install -y build-essential \ mtd-utils \ autoconf \ pkg-config \ texinfo \ genext2fs \ libtool \ libhidapi-dev \ python3 \ python3-jinja2 \ python3-yaml

console brew update && \ brew upgrade && \ brew install bash \ coreutils \ autoconf \ automake \ genext2fs \ make \ libelf \ wget \ gnu-sed \ hidapi \ python3 \ python3-jinja2 \ python3-yaml

*bash in version >= 4.0 and make in version >= 3.82 are needed (associative arrays and undefine used). They may be preinstalled, but in older versions, that's why we install it there.

It's also required to add appropriate paths to the PATH environment variable:

console export PATH=$(brew --prefix make)/libexec/gnubin:$(brew --prefix gnu-sed)/libexec/gnubin:$PATH

and keep it updated, for example by placing the export in the startup script:

console echo 'export PATH=$(brew --prefix make)/libexec/gnubin:$(brew --prefix gnu-sed)/libexec/gnubin:$PATH' >> $HOME/.zshrc

*Note that you have to place the gnubin path that provides make before the /usr/bin in the PATH environment variable to use the gnu version (as it is done above).

Phoenix-RTOS requires the endian.h header, which may exist, but not be visible. If during the building you discover the following error: fatal error: 'endian.h' file not found please create the symlink to this header by the given command:

console sudo ln -s /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/machine/endian.h /usr/local/include/endian.h

If you have encountered some issue during the toolchain build - you probably interrupted a build before or the files in the toolchains directory are broken for some reason. Removing a directory for a specific architecture (arm-phoenix/i386-pc-phoenix/riscv64-phoenix/sparc-phoenix) and launching a build once again should help.

NOTE: Even during the correct compilation process there may be some unresolved warnings.