Re: [skimo@kotnet.org] libc/2030: [50 character or so descriptive subject here (for reference)]

[Andreas Jaeger <aj at suse dot de>]

Andreas Schwab <schwab@suse.de> writes:

> Andreas Jaeger <aj@suse.de> writes:
> 
> |> Hi,
> |> 
> |> we received the following bug report about problems with binutils.
> |> 
> |> Should we demand newer binutils?  Is this really a bug - and how can
> |> we check for recent enough binutils?
> |> 
> |> Will the following work for configure?  And is a test for 2.10.1 or
> |> newer sufficient?
> 
> That would be wrong for ia64, where the latest version is 2.9-ia64-000717.

Here's a tested patch that allows 2.9-ia64-*.  I've tested it with
2.10.91 on i686 and 2.9-ia64-000717 on ia64.

Ok to commit?

Andreas

2001-01-22  Andreas Jaeger  <aj@suse.de>

	* configure.in: Add test for new enough binutils version, move
	compiler/binutils test up.

============================================================
Index: configure.in
--- configure.in	2001/01/06 17:33:47	1.300
+++ configure.in	2001/01/22 10:44:37
@@ -567,6 +567,21 @@
   [GNU sed version \([0-9]*\.[0-9.]*\)],
   [3.0[2-9]*|3.[1-9]*|[4-9]*], SED=: aux_missing=t)
 
+AC_PROG_CC_LOCAL
+AC_CANONICAL_BUILD
+if test $host != $build; then
+  AC_CHECK_PROGS(BUILD_CC, gcc cc)
+fi
+AC_SUBST(cross_compiling)
+AC_PROG_CPP
+LIBC_PROG_BINUTILS
+AC_CHECK_TOOL(MIG, mig)
+
+# Accept binutils 2.10.1 or newer (and also any ia64 2.9 version)
+AC_CHECK_PROG_VER(AS, $AS, --version,
+  [GNU assembler.* \([0-9]*\.[0-9.]*\(-ia64-[0-9]*\)*\)],
+  [2.10.[1-9]* | 2.1[1-9]* | 2.9-ia64-*], AS=: critic_missing=t)
+
 if test -n "$critic_missing"; then
 AC_MSG_ERROR([
 *** Some critical program is missing or too old.
@@ -581,16 +596,6 @@
 # glibcbug.in wants to know the compiler version.
 CCVERSION=`$CC -v 2>&1 | sed -n 's/gcc version //p'`
 AC_SUBST(CCVERSION)
-
-AC_PROG_CC_LOCAL
-AC_CANONICAL_BUILD
-if test $host != $build; then
-  AC_CHECK_PROGS(BUILD_CC, gcc cc)
-fi
-AC_SUBST(cross_compiling)
-AC_PROG_CPP
-LIBC_PROG_BINUTILS
-AC_CHECK_TOOL(MIG, mig)
 
 # if using special system headers, find out the compiler's sekrit
 # header directory and add that to the list.  NOTE: Only does the right


-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj