This section describes the setup needed by various operating systems
in order to run crosstool-NG, as well as some OS-specific caveats and limitations.
The package lists given in the following subsections cover all the features tested
by the sample configurations. You particular configuration may not need all those
packages. For example,
git is needed if your configuration is for an uClinux-based
target which requires
elf2flt utilities (which does “rolling releases” and must
be checked out from a Git repository).
If on the other hand you encounter a dependency not listed here, please let us know over the mailing list or via a pull request!
The following packages are needed for crosstool-NG (assuming
pacstrap ... base base-devel
pacman -S grub os-prober were performed during installation):
git help2man python gperf.
Install them with
pacman -S PACKAGES.
- The default color scheme used by Kconfig on ArchLinux makes the active menu selection
hard to see. A workaround for this issue is to put the following line into your shell’s
The following packages need to be installed on CentOS 7:
yum install autoconf gperf bison flex texinfo help2man gcc-c++ patch \ ncurses-devel python-devel perl-Thread-Queue bzip2 git
Linux: Fedora Core
The following packages need to be installed on Fedora Core 25:
dnf install autoconf gperf bison flex texinfo help2man gcc-c++ patch \ ncurses-devel python-devel perl-Thread-Queue git
The following packages need to be installed after installing a minimal profile:
The following packages need to be installed:
apt-get install -y gcc gperf bison flex texinfo help2man make libncurses5-dev \ python-dev autoconf automake libtool libtool-bin gawk
The following packages need to be installed on Ubuntu 16.04.2 (server):
apt-get install gcc gperf bison flex texinfo help2man make libncurses5-dev \ python-dev libtool-bin
macOS (a.k.a Mac OS X, OS X)
Originally contributed by: Titus von Boxberg
The instructions below have been verified on macOS Sierra (10.12). They have been previously reported to work with versions since Mac OS X Snow Leopard (10.6) with Developer Tools 3.2, and with Mac OS X Leopard (10.5) with Developer Tools + GCC 4.3 or newer installed via MacPorts.
You have to use a case sensitive file system for crosstool-NG’s build and target directories. Use a disk or disk image with a case sensitive FS that you mount somewhere.
Install required tools via HomeBrew. The following set is sufficient for HomeBrew:
autoconf binutils gawk gmp gnu-sed help2man mpfr openssl pcre readline wget xz. Install them using
brew install PACKAGEcommand.
homebrew/dupes/grepis recommended. It has been noticed that GNU libc was misconfigured due to a subtle difference between BSD grep (which is used by macOS) and GNU grep. This has since been fixed, but other scripts in various packages may still contain GNUisms.
If you prefer to use MacPorts, refer to the previous version of the instruction below and let us know if it works with current crosstool-NG and macOS releases.
Mac OS X defaults to a fairly low limit on the number of the files that can be opened by a process (256) that is exceeded by the build framework of the GNU C library. Increase this limit to 1024:
ulimit -n 1024
When building on macOS, the following message may be displayed:
clang: error: unsupported option '-print-multi-os-directory' clang: error: no input files
It is reported when the host version of
libiberty(from GCC) is compiled by macOS default compiler,
clang. In absense of any reported multilib information,
libibertyis then configured with the default compilation flags. This does not seem to affect the resulting toolchain.
ct-ng menuconfigwill not work on Snow Leopard 10.6.3 since libncurses is broken with this release. MacOS <= 10.6.2 and >= 10.6.4 are ok.
APFS filesystem is known to have some random issues with parallel build of GCC. See this bug report for details. Don’t use APFS, or turn off the parallel build in crosstool-NG (setting the number of parallel jobs to 1 in the confiuguration) as a workaround.
Previous version of the installation guidelines
Crosstool-NG has been reported to work with MacPorts as well, using the following set of ports:
lzmautils libtool binutils gsed gawk. On Mac OS X Leopard, it is also required to install
On Leopard, make sure that the MacPort’s
gccis called with the default commands (
g++,…), via MacPort’s
On OSX 10.7 Lion / when using Xcode >= 4 make sure that the default commands
g++, etc.) point to
llvm-gcc-4.2by using MacPort’s
gcc_selectfeature. With MacPorts >= 1.9.2 the command is: “sudo port select –set gcc gcc42”
This also requires (like written above) that macport’s
bindirectory comes before the standard directories in your
PATHenvironment variable because the
gccsymlink is installed in
/opt/local/binand the default
/usr/bin/gccis not removed by the
llvm-gcc-4.2(with Xcode 4.1 it is on my machine “gcc version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.15.00)”) cannot boostrap gcc. See this bug
Apparently, GNU make’s builtin variable
.LIBPATTERNSis misconfigured under MacOS: It does not include
lib%.dylib. This affects build of (at least) GDB 7.1 Put
lib%.a lib%.so lib%.dylibas
.LIBPATTERNSinto your environment before executing
ct-ng build. See here for details.
Note however, that GDB 7.1 (and anything earlier than 7.10) are known to fail to build on macOS.
Originally contributed by: Ray Donnelly
Prerequisites and instructions for using crosstool-NG for building a cross toolchain on Windows (Cygwin) as build and, optionally Windows (hereafter) MinGW-w64 as host.
Use Cygwin64 if you can. DLL base-address problems are lessened that way and if you bought a 64-bit CPU, you may as well use it.
You must enable Case Sensitivity in the Windows Kernel (this is only really necessary for Linux targets, but at present, crosstool-ng refuses to operate on case insensitive filesystems). The registry key for this is:
HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\kernel\obcaseinsensitiveRead more here.
Since release 1.7, Cygwin no longer supports the ‘managed’ mount option. You must use case sensitive FS.
setup-x86_64.exe, install the default packages and also the following ones:
Leave “Select required packages (RECOMMENDED)” ticked.
- The packages marked with * are only needed if your host is MinGW-w64.
Although nativestrict symlinks seem like the best idea, extracting glibc fails when they are enabled, so just don’t set anything here. If your host is MinGW-w64 then these ‘Cygwin-special’ symlinks won’t work, but you can dereference them by using tar options –dereference and –hard-dereference when making a final tarball. I plan to investigate and fix or at least work around the extraction problem. Read more here.
- If both BFD and GOLD linkers are enabled in binutils,
collect2.exewill attempt to run
ldwhich is a shell script so you need to make sure that a working shell is in your path. Eventually this will be replaced with a native program for MinGW-w64 host.
- Cygwin is slow. No, really, really slow. Expect about approximately 5x to 10x slowdown compared to a Linux system.
FreeBSD (and other BSD)
FreeBSD support is currently experimental in crosstool-NG.
FreeBSD does not provide a
gcc command by default. Crosstool-NG and many of the packages
used expect this by default. A comprehensive fix for various ways of setting up the OS
is planned after the 1.23 release. Until then, setting up the following packages is
recommended as a prerequisite for crosstool-NG:
Use any supported method of installation, e.g.:
cd /usr/ports/lang/gcc6 make install clean
Even with these packages installed, some of the samples are failing to build. YMMV.
Previous version of the installation guidelines
Contributed by: Titus von Boxberg
Prerequisites and instructions for using ct-ng for building a cross toolchain on FreeBSD as host.
Tested on FreeBSD 8.0
Install (at least) the following ports archivers/lzma textproc/gsed devel/gmake devel/patch shells/bash devel/bison lang/gawk devel/automake110 ftp/wget
Of course, you should have /usr/local/bin in your PATH.
- run ct-ng’s configure with the following tool configuration:
./configure --with-sed=/usr/local/bin/gsed \ --with-make=/usr/local/bin/gmake \ --with-patch=/usr/local/bin/gpatch [...other configure parameters as you like...]
- proceed as described in general documentation but use gmake instead of make