From fabc40428e5c7283c9f4419c0558b32ddf00dfdb Mon Sep 17 00:00:00 2001 From: Andreas Dilger Date: Fri, 15 Jul 2011 02:48:28 -0600 Subject: [PATCH] LU-278 build: Only warn for tag/version mismatch The configure process should NOT abort just because the most recent tag is not of the form that upstream uses to tag Lustre. Downstream developers may use their own tags, or just add extensions to upsteam's version tags. Change-Id: I43b63e8438cc37588d5a5b91677102ded22917fb Signed-off-by: Andreas Dilger Reviewed-on: http://review.whamcloud.com/1105 Tested-by: Hudson Reviewed-by: Johann Lombardi --- build/autoconf/lustre-build.m4 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/build/autoconf/lustre-build.m4 b/build/autoconf/lustre-build.m4 index caf7f0a..a9bff1c 100644 --- a/build/autoconf/lustre-build.m4 +++ b/build/autoconf/lustre-build.m4 @@ -88,7 +88,7 @@ if git branch >/dev/null 2>&1; then # only do this test for lustre (not ldiskfs) if test "$PACKAGE" = "lustre" -a "$ver" != "$VERSION"; then - AC_MSG_ERROR([most recent tag found: $ver does not match current version $VERSION.]) + AC_MSG_WARN([most recent tag found: $ver does not match current version $VERSION.]) fi if test "$ffw" != "0"; then -- 1.8.3.1