diff options
| author | Otavio Salvador <otavio@ossystems.com.br> | 2014-09-02 15:54:45 -0300 |
|---|---|---|
| committer | Otavio Salvador <otavio@ossystems.com.br> | 2014-09-02 16:23:37 -0300 |
| commit | 9378ffa7c49ce71c1089f1987a980cbcc919a279 (patch) | |
| tree | c2fa0d153ed13aed0308bdf2f1d8d446bddb1ec3 /meta-fsl-arm/browser-layer/recipes-browser/chromium | |
| parent | 21eab88a14d84801fcd532e20130ad7fec07b4a7 (diff) | |
| download | meta-freescale-9378ffa7c49ce71c1089f1987a980cbcc919a279.tar.gz | |
linux-mfgtool.inc: Fix dynamic packages handling
In case we have kernel modules, a runtime dependency or recommendation
can break the dependency resolution algorithm of BitBake resulting on
a conflict like:
,----[ Provider conflict error ]
| ERROR: Trying to resolve runtime dependency kernel-module-nfs resulted
| in conflicting PREFERRED_PROVIDER entries being found.
| The providers found were:
| ['.../meta-customer/recipes-kernel/linux/linux-customer-mfgtool_3.10.17.bb',
| '.../meta-customer/recipes-kernel/linux/linux-customer_3.10.17.bb']
| The PREFERRED_PROVIDER entries resulting in this conflict were:
| ['PREFERRED_PROVIDER_linux-mfgtool = mfgtool-linux-customer',
| 'PREFERRED_PROVIDER_virtual/kernel = linux-customer']
`----
To fix this, we need to rename the dynamic packages and hence change
the built binaries, solving the conflict.
Change-Id: I8becb8a4a839494720711f60f51515aba0140c68
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Diffstat (limited to 'meta-fsl-arm/browser-layer/recipes-browser/chromium')
0 files changed, 0 insertions, 0 deletions