Toolchains can't be built in restricted area

Bero, how did we do restricted toolchain builds so far? Did we do them at all? (We can't dedicate too many resources to this right now, or we'd have to drop other work that was planned for this cycle)

We didn't -- the toolchains in restricted were built in open (no problem because they contain only open code anyway) and then moved to restricted.

Danilo, any eta on this?

ping

This is currently blocking juice releases: Gesha, Paul, please look at this asap.

Update: I made needed changes to enable restricted toolchain builds yesterday evening, but testing failed due to compilation error in bzr trunk, confirmed by the same issue in 4.6-bzr and 4.7-bzr daily builds. I'm currently trying to find good reference gcc build to test restricted build changes.

Ok, we got successful build which behaves as expected re: access control: https://android-build.linaro.org/builds/~linaro-android-restricted/toolchain-4.7-2012.12-restr-pfalcon/

To set up a restricted toolchain build, you must use "BUILD_TYPE=build-android-toolchain-linaro-restricted" (yes, that's getting long, but adheres to existing naming convention and is fully explicit (which was design requirement for naming convention)). The rest of settings as for normal toolchain build.

<bero> pfalcon: https://android-build.linaro.org/builds/~linaro-android-restricted/juice-toolchain-4.7-bzr/ <-- running
<bero> pfalcon: Build succeeded

Checked that downloads access restriction apply. Closing.