These tricky targets used "autoreconf -f" (via "make releasetar") and
they changed the VERSION and configure files locally.
If building a release candidate tar archive is needed, it's better to:
Update VERSION with rcX suffix and configure via "autoreconf -f",
commit them, add a tag and build the archive via "make releasetar".
It should display: Archive build from tag tcpdump-...rcX.
Note: the "autoreconf -f" command changes the configure file in an
uncontrolled way (runstatedir, #define LARGE_OFF_T, etc.) depending on
the autoconf version.
It is necessary to choose the parts that will be added in the commit
with "git add -i".
This is a follow-up to
c378c2a04cdb3c8ec35341ca503cf1a2889a77d5.
[skip ci]
Fix an error when cross-compiling.
Fix "make releasetar" on AIX and Solaris.
Use "git archive" for the "make releasetar" process.
+ Remove the release candidate rcX targets.
Mend "make check" on Solaris 9 with Autoconf.
Address assorted compiler warnings.
Fix auto-enabling of Capsicum on FreeBSD with Autoconf.
echo "No $$TAG tag. Archive build from HEAD."; \
fi
-rc1 rc2 rc3 rc4 rc5:
- @VER=`cat $(srcdir)/VERSION`; \
- sed -i "s/$$VER/$${VER}$@/" VERSION ; \
- make releasetar; \
- git checkout VERSION configure
-
testlist:
echo $(TEST_DIST)