summaryrefslogtreecommitdiffstats
path: root/package/python-json-schema-validator/python-json-schema-validator.mk
diff options
context:
space:
mode:
authorYann E. MORIN <yann.morin.1998@free.fr>2015-04-21 18:55:52 +0200
committerThomas Petazzoni <thomas.petazzoni@free-electrons.com>2015-04-22 22:30:34 +0200
commitfb5cbf3198c9af20f7440b66c070873bb2207797 (patch)
tree67e8980e0d3cd3e5ddd3e5138ca5b352c13273e5 /package/python-json-schema-validator/python-json-schema-validator.mk
parent7c1db80c1d8854e5155f114c685b27451e5723eb (diff)
downloadbuildroot-fb5cbf3198c9af20f7440b66c070873bb2207797.tar.gz
buildroot-fb5cbf3198c9af20f7440b66c070873bb2207797.zip
toolchain: fix installing gconv libs with multi-arch toolchain
For a multi-arch toolchain, gconv modules are in a sub-directory named after the machine gcc targets. This is the case, for example, for the Linaro ARM 2014.09 toolchain, which has the gconv modules in (relative to the sysroot): /usr/lib/arm-linux-gnueabihf/gconv while the Sourcery CodeBench ARM 2014.05 (non-multi-arch) has them in: /usr/lib/gconv So, to catter for both cases, search both paths. We want to favour the machine-specific gconv modules over potentially existing "generic" ones, so we first search that (if it exists) and fallback to looking in the generic location. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Diffstat (limited to 'package/python-json-schema-validator/python-json-schema-validator.mk')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud