741720 - B2G should build with the arm-linux-androideabi toolchain

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: General, defect)

Description

[Mike Hommey [:glandium]]

B2G currently builds with the old, pretty broken, arm-eabi toolchain from the android NDK. It should use the arm-linux-androideabi toolchain instead.

Another reason you should switch, besides the arm-eabi toolchain being awful, is that it doesn't contain the atomic intrinsics that the new jemalloc uses.

Yet another reason is that it would help make the glue/gonk/prebuilt repository lighter. Much lighter.

Comment 1

[Andreas Gal :gal]

Mike, any chance we could rope you into making the switch for us? You know toolchains like nobody else.

Comment 2

[Mike Hommey [:glandium]]

From what I see in the B2G main Makefile, you're already using the arm-linux-androideabi toolchain for config-nexuss-ics. Maybe it would just work to change TOOLCHAIN_PATH default.

Comment 3

[Andreas Gal :gal]

In that case this should take care of itself soon. We are killing GB over the next weeks.

Comment 4

[Mike Hommey [:glandium]]

So, one main thing that prevents this from being fixable is that the only toolchains available under toolchains/ (so, from a git repo pov, git://github.com/mozilla-b2g/b2g-toolchains.git), are linux-x86.

Comment 5

[Michael Wu [:mwu]]

We switched to arm-linux-androideabi with the switch to ICS.

Comment 6

[Mike Hommey [:glandium]]

... but the build slaves are still building for GB.

Comment 7

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

GB builds of b2g are not a Tier I config, r+ on killing them on tb.

Comment 8

[Mike Hommey [:glandium]]

The slaves are building for ICS, with the arm-linux-androideabi toolchain now.