summaryrefslogtreecommitdiffstats
path: root/meta-python/recipes-devtools/python/python3-cmake/run-cmake-from-path.patch
diff options
context:
space:
mode:
authorPeter Kjellerstedt <pkj@axis.com>2026-04-08 19:47:32 +0200
committerKhem Raj <khem.raj@oss.qualcomm.com>2026-04-10 07:59:52 -0700
commited33569f822a3a8d41f82f6980a046d17aca37d5 (patch)
tree14952c09a0ea5d6e2e37a5624e183eb94bd7bb6d /meta-python/recipes-devtools/python/python3-cmake/run-cmake-from-path.patch
parenteb16f0631ec656486ca4f003a9547190f497bed3 (diff)
downloadmeta-openembedded-ed33569f822a3a8d41f82f6980a046d17aca37d5.tar.gz
jq: Use Git to fetch the code
There is a bug (see https://github.com/jqlang/jq/issues/434), which results in an empty version being used if autoreconf is run on the jq sources when using a release tar ball. The incorrect assumption is that autoreconf is only used when fetching the code using Git. The empty version results in an incorrect libjq.pc file being created where the version is not set, which results in, e.g., `pkgconf --libs 'libjq > 1.6'` failing even if version 1.8.1 of jq is actually installed. Switch to fetching the code using Git to workaround the bug. Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Diffstat (limited to 'meta-python/recipes-devtools/python/python3-cmake/run-cmake-from-path.patch')
0 files changed, 0 insertions, 0 deletions