Re: autoconf 2.13 -> 2.50 for libiberty in gcc-2.95.3

[Tim Van Holder]

> Has anybody adjusted configure.in in the libiberty directory for 
> autoconf 2.50 ?
> 
Hmmm...  Checking my disk at home, I find I handled this for my
test build of gcc3.  Note that this was for a native (DJGPP) build;
it may not work properly if cross-compiling.
IIRC, there were a few other dirs using their own AC_PROG_CC; often,
you will want to use the regular macro instead.

Index: configure.in
===================================================================
RCS file: /cvs/gcc/gcc/libiberty/configure.in,v
retrieving revision 1.31
diff -u -u -r1.31 configure.in
--- configure.in        2000/12/26 22:16:22     1.31
+++ configure.in        2001/06/06 16:35:24
@@ -36,8 +36,15 @@
 AC_CHECK_TOOL(AR, ar)
 AC_CHECK_TOOL(RANLIB, ranlib, :)
 
-LIB_AC_PROG_CC
+AC_PROG_CC
 
+if test $ac_cv_c_compiler_gnu = yes; then
+  ac_libiberty_warn_cflags='-W -Wall -Wtraditional -pedantic'
+else
+  ac_libiberty_warn_cflags=
+fi
+AC_SUBST(ac_libiberty_warn_cflags)
+
 AC_ISC_POSIX
 AC_C_CONST
 AC_C_INLINE
@@ -274,8 +281,7 @@
   esac
 
   # We haven't set the list of objects yet.  Use the standard autoconf
-  # tests.  This will only work if the compiler works.
-  AC_PROG_CC_WORKS
+  # tests.
   AC_REPLACE_FUNCS($funcs)
 
   case "${host}" in