[OE-core] [PATCH] gcc-sanitizers: allow empty for lsan and tsan packages

[Kang Kai]

On 2016年10月12日 17:26, Burton, Ross wrote:
>
> On 12 October 2016 at 03:37, <kai.kang at windriver.com 
> <mailto:kai.kang at windriver.com>> wrote:
>
>     gcc checks threads and leak sanitizers support when do configure.
>     If not
>     supported, packages of tsan and lsan are empty. If add such package to
>     image it fails to build:
>
>     | ERROR: core-image-minimal-1.0-r0 do_rootfs: libtsan-dev not
>     found in the feeds
>     | ERROR: core-image-minimal-1.0-r0 do_rootfs: This is often caused
>     by an empty
>     | package declared in a recipe's PACKAGES variable. (Empty
>     packages are not
>     | constructed unless ALLOW_EMPTY_<pkg> = '1' is used.)
>
>
> Not sure I'm understand where those dependencies are coming from, how 
> would I replicate this?

gcc checks tsan and lsan support in source file 
gcc/libsanitizer/configure.tgt, it seems only support x86_64. Then tsan 
and lsan related packages will be empty for other target.
For qemuarm project, add in local.conf:

IMAGE_INSTALL_append = " libtsan"

Then run 'bitbake core-image-minimal", it shows errors:

ERROR: core-image-minimal-1.0-r0 do_rootfs: libtsan not found in the 
feeds (qemuarm armv5te armv5e armv5t armv5 armv4t armv4 arm noarch any 
all) in /buildarea3/kkang/poky-20141111/builds/qemuarm-Aug05/tmp/deploy/rpm.
ERROR: core-image-minimal-1.0-r0 do_rootfs: This is often caused by an 
empty package declared in a recipe's PACKAGES variable. (Empty packages 
are not constructed unless ALLOW_EMPTY_<pkg> = '1' is used.)
ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: 
/buildarea3/kkang/poky-20141111/builds/qemuarm-Aug05/tmp/work/qemuarm-poky-linux-gnueabi/core-image-minimal/1.0-r0/temp/log.do_rootfs.24600
ERROR: Task 
(/buildarea3/kkang/poky-20141111/poky/meta/recipes-core/images/core-image-minimal.bb:do_rootfs) 
failed with exit code '1'


Regards,
Kai



>
> Ross


-- 
Regards,
Neil | Kai Kang

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20161013/67dd7c2e/attachment-0002.html>