jq: Use Git to fetch the code
PATCH 1/1 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.
--- meta-oe/recipes-devtools/jq/jq_1.8.1.bb | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-)
meta-oe/recipes-devtools/jq/jq_1.8.1.bb +7 -6
@@ -8,15 +8,16 @@ SECTION = "utils" LICENSE = "MIT & BSD-2-Clause" LIC_FILES_CHKSUM = "file://COPYING;md5=cf7fcb0a1def4a7ad62c028f7d0dca47" -GITHUB_BASE_URI = "https://github.com/jqlang/${BPN}/releases/" -SRC_URI = "${GITHUB_BASE_URI}/download/${BPN}-${PV}/${BPN}-${PV}.tar.gz \ +SRCREV = "4467af7068b1bcd7f882defff6e7ea674c5357f4" + +SRC_URI = " \ + git://github.com/jqlang/jq.git;protocol=https;branch=master;tag=jq-${PV} \ file://run-ptest \ - " -SRC_URI[sha256sum] = "2be64e7129cecb11d5906290eba10af694fb9e3e7f9fc208a311dc33ca837eb0" +" -inherit autotools github-releases ptest +inherit autotools ptest -UPSTREAM_CHECK_REGEX = "releases/tag/${BPN}-(?P<pver>\d+(\.\d+)+)" +UPSTREAM_CHECK_GITTAGREGEX = "${BPN}-(?P<pver>\d+(\.\d+)+)" PACKAGECONFIG ?= "oniguruma"
Quoted 1 line · Peter Kjellerstedt via lists.openembedded.org
jq
I see this failure in jq:
| cc1: fatal error: src/lexer.c: No such file or directory
'inherit autotools-brokensep' fixed the issue for me
Quoted 4 lines · Markus Volk via lists.openembedded.org
On Sat, Mar 14 2026 at 00:23:57 +01:00:00, Peter Kjellerstedt via lists.openembedded.org <[email protected]> wrote:
Quoted 9 lines
jq
I see this failure in jq:
| cc1: fatal error:src/lexer.c: No such file or directory'inherit autotools-brokensep' fixed the issue for me
IMO this should be fixed in source to use path to generated lexec.c file, I think its pregenerated in archives
but needs to be regenerated when building from git sources.
Quoted 12 lines
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#125330):
https://lists.openembedded.org/g/openembedded-devel/message/125330
Mute This Topic: https://lists.openembedded.org/mt/118307165/1997914
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-