incorrect use of 'echo' in AC_LIBTOOL_PROG_CC_C_O test

[Charles Wilson]

The use of 'echo' is wrong; with it, the AC_LIBTOOL_PROG_CC_C_O test 
always fails with an 'extraneous \' error (because of the '\n' at the 
end of $lt_simple_compile_test_code).  So, use printf like
AC_LIBTOOL_COMPILER_OPTION does.


2002-10-27  Charles Wilson  <address@hidden>

        * libtool.m4 (AC_LIBTOOL_PROG_CC_C_O): use printf,
        not echo.

--Chuck

--- /usr/autotool/devel/share/aclocal/libtool.m4        2002-10-16 
14:23:14.000000000 -0400
+++ config/libtool.m4   2002-10-27 01:06:21.000000000 -0400
@@ -881,7 +881,7 @@
                   FFLAGS="$FFLAGS -o out/conftest2.$ac_objext"],
          [$1],[GCJ],[save_GCJFLAGS="$CFLAGS"
                   CFLAGS="$GCJFLAGS -o out/conftest2.$ac_objext"])
-   echo "$lt_simple_compile_test_code" > conftest.$ac_ext
+   printf "$lt_simple_compile_test_code" > conftest.$ac_ext
 
    # According to Tom Tromey, Ian Lance Taylor reported there are C compilers
    # that will create temporary files in the current directory regardless of