Bug 13720 - Should look at COMPATIBLE_HOST when picking machine
Summary: Should look at COMPATIBLE_HOST when picking machine
Status: RESOLVED FIXED
Alias: None
Product: Automated Update Handler
Classification: Yocto Project Subprojects
Component: Automatic Update Handler (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 3.1
Assignee: Alexander Kanavin
QA Contact: apoorv sangal
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2019-12-20 13:14 UTC by Ross Burton
Modified: 2020-03-28 20:24 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ross Burton 2019-12-20 13:14:45 UTC 
AUH sent me a mail saying that the acpica auto-upgrade failed.  This failed because it decided to do the upgrade on qemumips, but acpica isn't compatible with that machine.

ERROR: Nothing PROVIDES 'acpica'
acpica was skipped: incompatible with host mips-poky-linux (not in COMPATIBLE_HOST)

The recipe has:

COMPATIBLE_HOST = "(i.86|x86_64|arm|aarch64).*-linux"
Comment 1 Alexander Kanavin 2019-12-20 13:28:17 UTC 
I guess AUH could look at bitbake output here; using 'bitbake -e' to actually look into COMPATIBLE_HOST/MACHINE values vs. target is not possible as 'bitbake -e' fails similarly.