Cross-buildd: what is currently supported and future planning

Registered by Ricardo Salveti on 2011-10-26

Topics:
 - Describe what is currently supported at the cross-buildd
 - Go over the issues, discuss about how to improve it, and what kind of features do we want to improve/develop

More info at: https://wiki.linaro.org/Platform/DevPlatform/CrossBuildd

Blueprint information

Status:
Not started
Approver:
Ricardo Salveti
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
Wookey
Definition:
Discussion
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Session Notes:

Existing state

What next?:
Wanna-build/sbuild?
Launchpad?
Something else?

Long term solution:
 * Launchpad: add new job type to deal with cross compiling
 * launchpad-build needs mods

 Just ask lamont to give me a wanna-build instance

Builds can run at an EC2 instance:
 * Needs to get a key from Linaro

UI - pgstatus?
or something else?

Launchpad buildd chroots: URL accessible from https://launchpad.net/api/devel/ubuntu/precise/i386 (etc.)
 lool's download script: http://people.linaro.org/~lool/dl-lp-chroot

Provide more information about the build, like toolchain and dependencies:
dhbuildinfo -
dpkg --get-selections
Also provide the resulted package.

mailing list for cross-build results is simple version

Something to check for 'used to work', but now bust. (can pgstatus do this?)
Would be nice for the interface/mail to notify about regressions.

List of packages to cross build to be worked at https://blueprints.launchpad.net/ubuntu/+spec/ubuntu-arm-p-cross-compilable-packages

Script to download Launchpad chroots for various architectures/dists etc.:
http://people.linaro.org/~lool/dl-lp-chroot

#action: Prod colin to merge current multistrap
#action: wookey: file multistrap bas-files bug

How do we do testing?
more lintian tests?
Can we compare against native-built packages?
 * symbols lists?
 * Compare configure status?
 * compare
 * compare disassembly?
  * may not be possible due to host-side optimisation differences

buildd-from-hell was a native tool to compare

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.