summaryrefslogtreecommitdiffstats
path: root/meta/recipes-support/libgcrypt
diff options
context:
space:
mode:
authorMark Asselstine <mark.asselstine@windriver.com>2018-05-08 15:40:18 -0400
committerRichard Purdie <richard.purdie@linuxfoundation.org>2018-05-11 07:49:38 +0100
commitc6e502bc615c1b9fa16ad8e6a3085948a143e12c (patch)
treeed69d319081650915d57ad48be664f0d91eb7154 /meta/recipes-support/libgcrypt
parent06d7df6fe28485c684e478c1ed2dff32eec7c195 (diff)
downloadpoky-c6e502bc615c1b9fa16ad8e6a3085948a143e12c.tar.gz
libcap: fix -native and usrmerge builds
When attempting to build a -native package which DEPENDS on libcap-native the libcap libraries are not found and the build will fail (for example attempting to build qemu-native with 'PACKAGECONFIG_append = " virtfs"'). It turns out commit 2c9c4a406a0f [libcap: fix (base_)libdir usage] breaks builds of libcap(-native) when $root_prefix is not "". This is because the variables which define $root_prefix are also part of $prefix so you end up with part of the path being used twice, first as part of 'lib=' in do_compile, and secondly as part of 'prefix=' in do_install. When $root_prefix is "" this isn't noticed. By using $baselib we should not re-break the issue which commit 2c9c4a406a0f was fixing but we should avoid doubling down on the paths thus fixing the -native and usrmerge builds. (From OE-Core rev: b46c55c3b9db5d8f2080ae2611294a5b24efe4a4) Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-support/libgcrypt')
0 files changed, 0 insertions, 0 deletions