Thanks for working on this!

I'm thinking if we should split the building of toolchains in different repositories.
The compilation is quite slow, especially on the boxes that travis and docker hub provide for free.
I remember compiling cmake added minutes to travis times.
Also, once we have a recipe for building our own toolchains, we might want to actually do that for other architectures as well. In addition, we might want to make the resulting builds available as seperate downloads.

So I suggest creating a repo in github that has a .travis.yml building the msp430 toolchain and hook it up so on a merge to master, the resulting binaries get tar'ed up and made available as github download. Then in riotbuild, we just download the result.

I can assist with that!

So I suggest creating a repo in github that has a .travis.yml building the msp430 toolchain and hook it up so on a merge to master, the resulting binaries get tar'ed up and made available as github download. Then in riotbuild, we just download the result.

@geromueller I've finally done that. See #99. Could you give it a try?

Closing in favor of #99.

(Note to myself: compare used configure flags)