descriptionMirror of crosstool-ng
last changeWed, 26 Feb 2020 19:07:59 +0000 (11:07 -0800)
8 hours ago Alexey NeymanMerge pull request #1309 from stilor/upgrades master
8 hours ago Alexey NeymanSet --with-cpu-{32,64} for multilib builds 1309/head
8 hours ago Alexey NeymanUpdate ARC patch to glibc 2.31
8 hours ago Alexey Neymanelf2flt: handle binutils 2.34 API
8 hours ago Alexey NeymanNew Linux versions
8 hours ago Alexey NeymanAdd uClibc-ng 1.0.33
8 hours ago Alexey NeymanAdd strace-5.5
8 hours ago Alexey NeymanAdd newlib 3.2.0, 3.3.0
8 hours ago Alexey NeymanAdd ncurses 6.2
8 hours ago Alexey NeymanAdd make 4.3
8 hours ago Alexey NeymanAdd GMP 6.2.0
8 hours ago Alexey NeymanAdd glibc 2.31
8 hours ago Alexey NeymanAdd gdb-9.1
8 hours ago Alexey NeymanSlide the checked out tag of elf2flt
8 hours ago Alexey NeymanAdd binutils 2.34
8 hours ago Alexey NeymanMerge pull request #1306 from cpackham/docker-default-uid
10 months ago crosstool-ng-1.24.0 Tag the 1.24.0 release.
11 months ago crosstool-ng-1.24.0-rc3 Tag RC3 for 1.24.0 release.
12 months ago crosstool-ng-1.24.0-rc2 Tag 1.24.0-rc2.
12 months ago crosstool-ng-1.24.0-rc1 Tag 1.24.0
2 years ago crosstool-ng-1.23.0 Tag 1.23.0
2 years ago crosstool-ng-1.23.0-rc2 Tag 1.23.0-rc2.
2 years ago crosstool-ng-1.23.0-rc1 Tag 1.23.0-rc1
4 years ago crosstool-ng-1.22.0 crosstool-ng-1.22.0
4 years ago crosstool-ng-1.21.0 crosstool-ng-1.21.0
5 years ago crosstool-ng-1.20.0 crosstool-NG 1.20.0
6 years ago crosstool-ng-1.19.0
7 years ago crosstool-ng-1.18.0
7 years ago crosstool-ng-1.17.0
7 years ago crosstool-ng-1.16.0
7 years ago crosstool-ng-1.15.3
7 years ago crosstool-ng-1.15.2
8 hours ago master
3 years ago 1.22
3 years ago update-ncurses
4 years ago 1.21
5 years ago 1.20
6 years ago 1.19
7 years ago 1.18
7 years ago 1.17
7 years ago 1.16
7 years ago 1.15
7 years ago 1.14
7 years ago 1.13
8 years ago 1.12
8 years ago 1.11
8 years ago 1.10
9 years ago 1.9



Crosstool-NG aims at building toolchains. Toolchains are an essential component in a software development project. It will compile, assemble and link the code that is being developed. Some pieces of the toolchain will eventually end up in the resulting binaries: static libraries are but an example.

Before reporting a bug, please read bug reporting guidelines. Bugs that do not provide the required information will be closed without explanation.

Refer to documentation at crosstool-NG website for more information on how to configure, install and use crosstool-NG.

Note 1: If you elect to build a uClibc-based toolchain, you will have to prepare a config file for uClibc with <= crosstool-NG-1.21.0. In >= crosstool-NG-1.22.0 you only need to prepare a config file for uClibc(or uClibc-ng) if you really need a custom config for uClibc.

Note 2: If you call ct-ng --help you will get help for make(2). This is because ct-ng is in fact a make(2) script. There is no clean workaround for this.

Repository layout

To clone the crosstool-NG repository:

git clone

Old repositories

These are the old Mercurial repositories. They are now read-only:

Pull Requests and Issues

You can find open Pull Requests on GitHub here and you can find open issues here.


To contribute to crosstool-NG it is helpful to provide as much information as you can about your change, including any updates to documentation (if appropriate), and test... test... test.

git clone

git checkout -b fix_comment_typo

git add [file(s) that changed, add -p if you want to be more specific]

git diff --cached

git commit -s

The -s automatically adds your Signed-off-by: [name] <email> to your commit message. Your commit will be rejected without this.

Also, please explain what your change does. "Fix stuff" will be rejected. For examples of good commit messages, read the changelog.

git push origin fix_comment_typo

git checkout -b fix_out_of_date_patch origin/1.22 Then when you get to this pull request screen change the base branch from master to 1.22

Add your changes

git add [file(s) that changed, add -p if you want to be more specific]

Verify you are happy with your changes to be commited

git diff --cached

Commit changes

git commit -s

git push origin fix_comment_typo

At this point the PR will be updated to have the latest commit to that branch, and can be subsequently reviewed.

  1. Interactively rebase the offending commit(s) to fix the code review. This option is slightly annoying on Github, as the comments are stored with the commits, and are hidden when new commits replace the old commits. They used to disappear completely; now Github shows a grey 'View outdated' link next to the old commits.

This recipe also comes handy with other issues, like your topic branch not being up-to-date with master:

git fetch --all git rebase --ignore-whitespace origin master git rebase -i <offending-commit-id>^

NOTE: The --ignore-whitespace stops git apply (which is called by rebase) from changing any whitespace when it runs.

Replace pick with edit or remove the line to delete a commit. Fix the issue in the code review.

git add [file(s)] git rebase --continue <update commit comment if needed> git push --force origin fix_comment_typo


We previously used patchwork for development, but it is no longer used. I'd like to see patches that are still applicable turned into Pull Requests on GitHub.

You can find the list of pending patches available on patchwork.

More Info

You can find all of this and more at

Report issues at the project site on GitHub.

We have a mailing list. Archive and subscription info can be found here:

Aloha! :-)