u-boot builds rely on system mkimage
Bug #1102717 reported by
Bernhard Rosenkraenzer
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Linaro Android |
Confirmed
|
Low
|
Bernhard Rosenkraenzer | ||
Bug Description
Linaro Android builds that use u-boot as their bootloader rely on having a system version of mkimage installed.
This is bad for 2 reasons: The obvious one (build will fail on systems that don't have mkimage) and a less obvious and more important one: If u-boot ever changes the way mkimage works and the system version is not in sync with what we're using, we'll have a hard-to-spot boot failure.
Since mkimage does get built during the u-boot build process, this is probably just a matter of adding $(BUILD_
| Changed in linaro-android: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
| assignee: | nobody → Bernhard Rosenkraenzer (berolinux) |
Revision history for this message
| Botao (botao-sun) wrote | #1 |
Revision history for this message
| Botao (botao-sun) wrote | #2 |
To post a comment you must log in.
Comment from Bero:
"not sure if this was fixed, but it's not a priority because so far mkimage has never changed in a significant way. Still should be fixed though given the fix is so simple."