From cb235453a9276c371085e40ea1c87d9b641e511e Mon Sep 17 00:00:00 2001
From: Dana Robinson <derobins@hdfgroup.org>
Date: Wed, 15 Nov 2017 14:24:59 -0800
Subject: Changed ar to always use -cr instead of the autotools default of cru.

---
 config/linux-gnulibc1 | 5 -----
 configure.ac          | 7 ++++++-
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/config/linux-gnulibc1 b/config/linux-gnulibc1
index c32f64e..39225e7 100644
--- a/config/linux-gnulibc1
+++ b/config/linux-gnulibc1
@@ -30,11 +30,6 @@ if test -z "$CC"; then
     fi
 fi
 
-# Set flags for gnu ar (apparently via libtool, so AR_FLAGS, not ARFLAGS)
-# If you don't do this, you will get warnings about the 'u' in
-# automake's default 'cru' args.
-AR_FLAGS=crD
-
 # Figure out GNU C compiler flags
 . $srcdir/config/gnu-flags
 
diff --git a/configure.ac b/configure.ac
index 50893f7..5562d5c 100644
--- a/configure.ac
+++ b/configure.ac
@@ -759,12 +759,17 @@ fi
 ## Check which archiving tool to use. This needs to be done before
 ## the AM_PROG_LIBTOOL macro.
 ##
-
 if test -z "$AR"; then
   AC_CHECK_PROGS([AR], [ar xar], [:], [$PATH])
 fi
 AC_SUBST([AR])
 
+# Set the default ar flags to cr
+# The Automake default is to use cru and the 'u' causes ar
+# to emit warnings on some platforms.
+AR_FLAGS=cr
+
+
 ## Export the AR macro so that it will be placed in the libtool file
 ## correctly.
 export AR
-- 
cgit v0.12