don't run autoreconf for jq 1.7.1, as a release tarball is used as source#24275
Conversation
Problem: As per the jq build instructions "If you're not using the latest git version but instead building a released tarball (available on the release page), skip the autoreconf step, and flex or bison won't be needed." Remove the preconfigopts and Bison and flex builddependencies; otherwise, the built binary doesn't actually know what version it is, i.e. jq --version just outputs jq- instead of jq-1.7.1. Also switch to using SOURCELOWER_TAR_GZ template constant for readability/maintainability
|
@boegelbot please test @ jsc-zen3 |
|
@Thyre: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 3410674413 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
|
Test report by @PhoenixEmik |
autoreconf for jq 1.7.1, as a release tarball is used as source
Bug fix for jq/1.7.1 on GCCcore/13.2.0
Problem: As per the
jqbuild instructions "If you're not using the latest git version but instead building a released tarball (available on the release page), skip the autoreconf step, and flex or bison won't be needed."Remove the
preconfigoptsline andBisonandflexfrom thebuilddependencies; otherwise, the built binary doesn't actually know what version it is, i.e.jq --versionjust outputsjq-instead ofjq-1.7.1.Also switch to using
SOURCELOWER_TAR_GZtemplate constant for readability/maintainability