Merge lp:~vanvugt/mir/xcompile-wily into lp:mir
| Status: | Work in progress |
|---|---|
| Proposed branch: | lp:~vanvugt/mir/xcompile-wily |
| Merge into: | lp:mir |
| Diff against target: |
12 lines (+1/-1) 1 file modified
tools/setup-partial-armhf-chroot.sh (+1/-1) |
| To merge this branch: | bzr merge lp:~vanvugt/mir/xcompile-wily |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| PS Jenkins bot | continuous-integration | Needs Fixing on 2015-08-17 | |
| Mir development team | 2015-08-17 | Pending | |
|
Review via email:
|
|||
Commit Message
Use the wily build environment for cross compiling, not vivid.
This also fixes build failures related to the archive transition
to g++-5.
| Chris Halse Rogers (raof) wrote : | # |
| Daniel van Vugt (vanvugt) wrote : | # |
Wrong. For future development on mako we should be using devel-proposed (wily) images already.
| Daniel van Vugt (vanvugt) wrote : | # |
Although an option to choose vivid or wily would be handy in future
| Daniel van Vugt (vanvugt) wrote : | # |
Oh. Except wily phone images are now broken and generally not booting. So we've gone backwards and it's actually more likely now people are testing with vivid images again :P
So maybe xcompiling for vivid is still preferred. And some part of the wily archive transition has somehow broken vivid. We need to figure out now what's broken vivid.
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:2846
http://
Executed test runs:
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
SUCCESS: http://
deb: http://
FAILURE: http://
SUCCESS: http://
Click here to trigger a rebuild:
http://
Unmerged revisions
- 2846. By Daniel van Vugt on 2015-08-17
-
Use the wily build environment for cross compiling, not vivid.

Hm. This is almost certainly not going to work, because we're going to be deploying the built packages onto vivid-overlay- imaged makos, right?