Toolchain » History » Revision 9

« Previous | Revision 9/23 (diff) | Next »
steve-m, 02/19/2016 10:49 PM
update info about gcc 4.8 bug

To compile osmocomBB or SIMtrace for the target we need a GNU Toolchain for ARM.
There are various pre-compiled toolchains available but not all of them will produce working firmware.
We will try to support all these configurations but it might take a while to identify the source of a problem.

If you have persistent errors when compiling, try using a different package.

'''note:''' ~as of 2013-10-20, if you use a toolchain with gcc >=4.8, the firmware can be compiled, but will hang as soon as you want to sync to an ARFCN.~ This issue has been [ fixed] in master.

=== Build one from source ===

If you want to build your own toolchain, known to be working with OsmocomBB, see here: [wiki:GnuArmToolchain].

This is the best option to get a fairly recent GCC, and this is the option used by several Osmocom-BB developers.

=== Ubuntu packages ===
gnuarm packages from following ppa are known to work on ubuntu 10.10 to build osmocom-bb. They are known '''not''' to work for SIMtrace

sudo add-apt-repository ppa:bdrung/bsprak
sudo apt-get update
sudo apt-get install arm-elf-toolchain

(FIXME: Should be rechecked, the information might be outdated)

=== Mac OS X ===

Apparently the arm-elf-gcc 4.3.2 from ports for mac os x can compile the sourcecode as well after symlinking /opt/local/bin/arm-elf-ranlib to /opt/local/bin/arm-elf-linux-ranlib and /opt/local/bin/arm-elf-strip to /opt/local/bin/arm-elf-linux-strip.
If you omit the links, there will be unresolvable references to symbols in the libraries.

Files (0)

Updated by steve-m about 8 years ago · 9 revisions

Add picture from clipboard (Maximum size: 48.8 MB)