Linaro Android

Android kernel does not boot if built with default toolchain

Bug #768276 reported by Patrik Ryd on 2011-04-21

6

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Linaro Android	Fix Released	Critical	Patrik Ryd	Linaro Android 11.04
	Linaro Android Build Tools	Fix Released	Critical	Paul Sokolovsky
	Linaro Android Frontend	Invalid	Undecided	Unassigned

Bug Description

The Android kernel does not boot if build with the default Android toolchain.

Must set TARGET_TOOLS_PREFIX=prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- to build kernel

Server need to be updated to use this toolchain for the Android build.
It would be nice :) if this could in the UI when creating a build.

Revision history for this message

Alexander Sack (asac) wrote on 2011-04-21:

#1

critical because it breaks default boot. jserv says 4.4.0 toolchain will fix this. needs action on linaro-cloud-buildd side.

Changed in linaro-android:
assignee:	nobody → Patrik Ryd (patrik-ryd)
importance:	Undecided → Critical
milestone:	none → linaro-11.04
status:	New → Triaged

Paul Sokolovsky (pfalcon) on 2011-04-21

Changed in linaro-android:
status:	Triaged → Invalid
status:	Invalid → New

Revision history for this message

Paul Sokolovsky (pfalcon) wrote on 2011-04-21:

#2

If it's settable in UI, what should the default value be (I suppose not empty)? And what toolchain was used by default (I assume the answer is the same)? I'd appreciate this extra info for quicker turn-around.

Revision history for this message

Patrik Ryd (patrik-ryd) wrote on 2011-04-21:

#3

The default tool chain is prebuilt/linux-x86/toolchain/arm-eabi-4.4.3. This is not as stable as 4.4.0 according to (the all knowing) jserv--.

Changed in linaro-android:
status:	New → Confirmed

Revision history for this message

Patrik Ryd (patrik-ryd) wrote on 2011-04-21:

#4

Verified that the panda board boots Android with UI if TARGET_TOOLS_PREFIX=prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- is used to build the boottarball.

Paul Sokolovsky (pfalcon) on 2011-04-21

Changed in linaro-android-build-tools:
assignee:	nobody → Paul Sokolovsky (pfalcon)
importance:	Undecided → Critical
status:	New → In Progress

Revision history for this message

Paul Sokolovsky (pfalcon) wrote on 2011-04-21:

#5

Ok, it seems prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc is used by default, and if TARGET_TOOLS_PREFIX exists, but empty, android's default will be used.

Revision history for this message

Paul Sokolovsky (pfalcon) wrote on 2011-04-21:

#6

Ok, so setting TARGET_TOOLS_PREFIX in build config is already supported. Actually, all variables in build config will be exported to the environment, so build config may specify any variables which may be recognized by Android build scripts. As TARGET_TOOLS_PREFIX seems to be particularly useful, I described it explicitly in
https://wiki.linaro.org/Platform/Android/LinaroAndroidBuildService?action=diff&rev2=25&rev1=24

Here's sample build: https://android-build.linaro.org/builds/~pfalcon/panda-gcc4.4.0/

Changed in linaro-android-frontend:
status:	New → Invalid
Changed in linaro-android-build-tools:
status:	In Progress → Fix Released

Alexander Sack (asac) on 2011-06-08

Changed in linaro-android:
status:	Confirmed → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.