Go to file
Kai Kang 254ab4a764 target-sdk-provides-dummy: resolve sstate conflict
It exists a situation that there is a common config file includes
multilib.conf but variable MULTILIBS is not set by default:

  require conf/multilib.conf
  MULTILIBS ?= ""

When build target-sdk-provides-dummy in a build project, it fails with
following steps:

1 $ echo 'MACHINE = "qemux86"' >>conf/local.conf
  $ bitbake target-sdk-provides-dummy
2 $ cat <<EOF >>conf/local.conf
    MACHINE = "qemux86-64"
    MULTILIBS = "multilib:lib32"
    DEFAULTTUNE_virtclass-multilib-lib32 = "i586"
    EOF
  $ bitbake target-sdk-provides-dummy
  $ bitbake lib32-target-sdk-provides-dummy

It fails to build lib32-target-sdk-provides-dummy with error messages:

| ERROR: target-sdk-provides-dummy-1.0-r0 do_packagedata: The recipe target-sdk-provides-dummy
|  is trying to install files into a shared area when those files already exist. Those files
|  and their manifest location are:
|   .../tmp/pkgdata/qemux86-64/lib32-target-sdk-provides-dummy
|     (matched in manifest-qemux86_64-lib32-target-sdk-provides-dummy.packagedata)
|   .../tmp/pkgdata/qemux86-64/runtime/lib32-target-sdk-provides-dummy
|     (matched in manifest-qemux86_64-lib32-target-sdk-provides-dummy.packagedata)
|   ... snip ...
| Please verify which recipe should provide the above files.

Add related directories to SSTATE_DUPWHITELIST to avoid the failures.

(From OE-Core rev: 9de9daa3dcbe271b3684f9a6eea1554f377e35fa)

Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2019-05-08 23:00:32 +01:00
bitbake bitbake: HEADER: Drop it 2019-05-04 10:44:49 +01:00
documentation documentation: Cleaned up "plug-in"/"plugin" terminology. 2019-05-07 10:23:42 +01:00
meta target-sdk-provides-dummy: resolve sstate conflict 2019-05-08 23:00:32 +01:00
meta-poky meta-poky: remove obsolete DISTRO_FEATURES_LIBC 2019-05-03 06:11:57 +01:00
meta-selftest layer.conf: Update to warrior release name series 2019-04-02 15:24:11 +01:00
meta-skeleton layer.conf: Update to warrior release name series 2019-04-02 15:24:11 +01:00
meta-yocto-bsp linux-yocto: update genericx86* SRCREV for 4.19 2019-05-07 10:13:13 +01:00
scripts resulttool: Add option to dump all ptest logs 2019-05-08 22:56:45 +01:00
.gitignore gitignore: Ignore repo tool directory 2018-10-29 17:26:47 +00:00
.templateconf meta-yocto: Rename to meta-poky to better match its purpose 2016-02-28 11:31:17 +00:00
LICENSE Fix license notices for OE-Core 2014-01-02 12:58:54 +00:00
oe-init-build-env oe-init-build-env: Error out when failed to locate cwd 2019-03-12 11:57:41 -07:00
README.hardware meta-yocto: Restructure and tidy up READMEs 2017-09-14 13:36:22 +01:00
README.LSB pax: remove the recipe 2018-02-24 10:31:45 +00:00
README.OE-Core README: Rename to README.OE-Core so its clear where its from/belongs/is about 2019-03-06 23:09:10 +00:00
README.poky meta-yocto: Restructure and tidy up READMEs 2017-09-14 13:36:22 +01:00
README.qemu README.qemu: qemuppc64 is not supported 2017-10-16 23:54:31 +01:00

QEMU Emulation Targets
======================

To simplify development, the build system supports building images to
work with the QEMU emulator in system emulation mode. Several architectures
are currently supported in 32 and 64 bit variants:

  * ARM (qemuarm + qemuarm64)
  * x86 (qemux86 + qemux86-64)
  * PowerPC (qemuppc only)
  * MIPS (qemumips + qemumips64)

Use of the QEMU images is covered in the Yocto Project Reference Manual.
The appropriate MACHINE variable value corresponding to the target is given
in brackets.