ti-omap: unable to build due to abi-check failures
Bug #576274 reported by
Andy Whitcroft
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-ti-omap (Ubuntu) |
Fix Released
|
High
|
Andy Whitcroft |
Bug Description
Builds are failing as below:
Missing module name in is_ignored() at debian/
II: Checking ABI for omap...
II: Different ABI's, running in no-fail mode
Reading symbols/modules to ignore...read 0 symbols/modules.
Reading new symbols (501)...read 7175 symbols.
Reading old symbols (500)...read 7175 symbols.
II: Checking for missing symbols in new ABI...
make: *** [abi-check-omap] Error 255
NOTE: This report seems to get referenced by updates to the build environment which are done to get a common build environment amongst the more recent releases.
Changed in linux-ti-omap (Ubuntu): | |
assignee: | nobody → Andy Whitcroft (apw) |
importance: | Undecided → High |
milestone: | none → lucid-updates |
status: | New → In Progress |
Changed in linux-ti-omap (Ubuntu): | |
status: | In Progress → Fix Committed |
description: | updated |
To post a comment you must log in.
Ok this turns out to be an issue triggered by CONFIG_ UNUSED_ SYMBOLS not being set in the configuration for ti-omap. Turns out this is required for properly formed ABI files. There is no obvious reason however we cannot cope with the form when this is not set. So will:
1) fix the abi-check parser to cope with the dodgy lines, UNUSED_ SYMBOLS for ti-omap, and UNUSED_ SYMBOLS into the enforcer configuration.
2) enable CONFIG_
3) get CONFIG_