PERFORCE change 151780 for review

[Peter Wemm]

http://perforce.freebsd.org/chv.cgi?CH=151780

Change 151780 by peter at peter_cheese on 2008/10/23 05:55:53

	Don't insist on gnu sed.  'sed -E' works fine.

Affected files ...

.. //depot/projects/valgrind/configure.in#6 edit

Differences ...

==== //depot/projects/valgrind/configure.in#6 (text+ko) ====

@@ -95,20 +95,20 @@
 # on some pretty fancy sed expressions, and AIX sed doesn't produce the
 # same results, causing install to fail
 
-AC_MSG_CHECKING([for GNU sed])
-
-[sed_firstline=`sed --version | head -n 1`]
-
-case "${sed_firstline}" in
-    GNU*)
-	AC_MSG_RESULT([ok, looks like GNU sed])
-	;;
-    *)
-	AC_MSG_RESULT([please ensure first 'sed' in your path is GNU sed])
-	AC_MSG_RESULT([note: GNU sed is only required at build/install time])
-	AC_MSG_ERROR([build/install requires that 'sed' is GNU sed])
-	;;
-esac
+#AC_MSG_CHECKING([for GNU sed])
+#
+#[sed_firstline=`sed --version | head -n 1`]
+#
+#case "${sed_firstline}" in
+#    GNU*)
+#	AC_MSG_RESULT([ok, looks like GNU sed])
+#	;;
+#    *)
+#	AC_MSG_RESULT([please ensure first 'sed' in your path is GNU sed])
+#	AC_MSG_RESULT([note: GNU sed is only required at build/install time])
+#	AC_MSG_ERROR([build/install requires that 'sed' is GNU sed])
+#	;;
+#esac
 
 
 # We don't want gcc < 3.0