From: Andreas Dilger Date: Thu, 14 Jul 2011 19:07:29 +0000 (-0600) Subject: LU-278 build: Only warn for tag/version mismatch X-Git-Tag: 2.1.0-RC0~46 X-Git-Url: https://git.whamcloud.com/?p=fs%2Flustre-release.git;a=commitdiff_plain;h=c487014a39a6e37dc22a957aad9ad9b739e3c8cf;ds=sidebyside 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: I9a98bfd4475d3df2694f536ba0352779a62650c7 Signed-off-by: Andreas Dilger Reviewed-on: http://review.whamcloud.com/510 Tested-by: Hudson Reviewed-by: Brian J. Murrell Tested-by: Maloo --- diff --git a/build/autoconf/lustre-build.m4 b/build/autoconf/lustre-build.m4 index 800925d..20e3d0d 100644 --- a/build/autoconf/lustre-build.m4 +++ b/build/autoconf/lustre-build.m4 @@ -91,7 +91,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