summaryrefslogtreecommitdiff
path: root/top
diff options
context:
space:
mode:
authorJim Meyering <meyering@fb.com>2013-10-26 19:26:13 -0700
committerJim Meyering <meyering@fb.com>2013-10-26 19:26:35 -0700
commit4c2f17d2a671eb6fc6ae318647040598f67705cc (patch)
tree794225969f3eccbfc3d1cc48e60fa924adf7f08e /top
parent6b24f60dad0f97704ae07d9688de7f31c1923bf7 (diff)
downloadgnulib-4c2f17d2a671eb6fc6ae318647040598f67705cc.tar.gz
maint.mk: fix "release" target to build _version
This fixes a bug in README-release whereby following the outlined steps, one would publish a tarball whose programs would report --version output not consistent with the package version number. This bug caused grep-2.15 to produce a grep program whose --version option made it print 2.14.56-1e3d rather than 2.15. * top/maint.mk (release): Making this target build "_version" ensures that the new version number is reflected in configure.
Diffstat (limited to 'top')
-rw-r--r--top/maint.mk1
1 files changed, 1 insertions, 0 deletions
diff --git a/top/maint.mk b/top/maint.mk
index c9f8cc8531..bf8f53a368 100644
--- a/top/maint.mk
+++ b/top/maint.mk
@@ -1424,6 +1424,7 @@ alpha beta stable: $(local-check) writable-files $(submodule-checks)
$(AM_V_at)$(MAKE) -s emit_upload_commands RELEASE_TYPE=$@
release:
+ $(AM_V_GEN)$(MAKE) _version
$(AM_V_GEN)$(MAKE) $(release-type)
# Override this in cfg.mk if you follow different procedures.