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 | 19f9ecc3e624caad58a788be8c150f2c871823ef (patch) | |
| tree | 10fe56be0b06e8e2a55addb88fc4281e8cd695e6 /browser-layer/recipes-browser/chromium/chromium-imx.inc | |
| parent | a99370b1d84b357479eb8b82124bb346ac37de4c (diff) | |
| download | meta-fsl-arm-19f9ecc3e624caad58a788be8c150f2c871823ef.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 'browser-layer/recipes-browser/chromium/chromium-imx.inc')
0 files changed, 0 insertions, 0 deletions