| Summary: | PAM is not enforced as a needed distro feature for any image | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Bogdan Alexandru Voiculescu <bogdanx.a.voiculescu> |
| Component: | core | Assignee: | Joshua Lock <joshuagloe> |
| Status: | VERIFIED FIXED | QA Contact: | Bogdan Alexandru Voiculescu <bogdanx.a.voiculescu> |
| Severity: | normal | ||
| Priority: | Medium | CC: | meta.mr.watcher, meta.watcher |
| Version: | 2.1 | ||
| Target Milestone: | 2.1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | Regression (Used to work) |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Bogdan Alexandru Voiculescu
2016-01-14 08:51:32 UTC
The bug here is not that pam isn't enforced as a distro feature, but that something is including pam as a DEPENDS (either implicit or explicit) without first checking whether pam is in DISTRO_FEATURES. I'll take a look and see if I can figure out what component that is. Adding exact steps: 1) git clone a fresh master repo 2) source environment 3) (optionally - set SSTATE) 4) bitbake core-image-minimal - Results: at some time, "WARNING: Building libpam but 'pam' isn't in DISTRO_FEATURES, PAM won't work correctly" is displayed; this is not immediate (but is before compiling gcc) - Expected: image build without this warning There's a patch to fix this issue from Ioan-Adrian Ratiu <adrian.ratiu@ni.com> queued in the master-next branch: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=master-next&id=c1720b71bf194f6dcae44672752039f0d779d40f Original submission is: http://lists.openembedded.org/pipermail/openembedded-core/2016-January/115301.html This fix was merged: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=764c9279eaebe2774ec344f722dfec9911b45691 Verified on master: 60100884d4d6a20aaf499d7afcf7fc91faabd22e |