Alexandre Oliva <[EMAIL PROTECTED]> writes:

> The only way to do it so that it works with both autoconf 2.13 and
> CVS autoconf, without triggering the warning in CVS autoconf, is
> this (from CVS automake's missing.m4):
> 
>   am_backtick='`'
>   AC_MSG_WARN([${am_backtick}$VAR' ...])

Ok, I see. New (untested) patch attached.

BTW, I noticed something which looks a bit strange to me. Beginning at
approximately line 2180 of libtool.m4 (from the head CVS branch),
there are a lot of shell variables which are set up. But some of them
are just set to their current value, for instance like this:

[...]
# The host system.
host_alias=$host_alias
host=$host
[...]
# A symbol stripping program
STRIP=$STRIP

# Used to examine libraries when file_magic_cmd begins "file"
MAGIC_CMD=$MAGIC_CMD

# Used on cygwin: DLL creation program.
DLLTOOL="$DLLTOOL"

# Used on cygwin: object dumper.
OBJDUMP="$OBJDUMP"

# Used on cygwin: assembler.
AS="$AS"
[...]

..etc, etc. What is the point in doing this?

Regards,
Morten

Index: ChangeLog
===================================================================
RCS file: /home/cvs/libtool/ChangeLog,v
retrieving revision 1.809
diff -u -r1.809 ChangeLog
--- ChangeLog   2000/10/02 01:18:16     1.809
+++ ChangeLog   2000/10/11 14:48:12
@@ -1,3 +1,8 @@
+2000-10-12  Morten Eriksen <[EMAIL PROTECTED]>
+
+       * libtool.m4 (_LT_AC_LTCONFIG_HACK): Fix invalid backslash
+       quoting.
+
 2000-10-02  Gary V. Vaughan  <[EMAIL PROTECTED]>
 
        From Bruce Korb <[EMAIL PROTECTED]>
Index: libtool.m4
===================================================================
RCS file: /home/cvs/libtool/libtool.m4,v
retrieving revision 1.118
diff -u -r1.118 libtool.m4
--- libtool.m4  2000/09/30 05:28:23     1.118
+++ libtool.m4  2000/10/12 10:32:42
@@ -775,10 +775,11 @@
 
 # Check for any special shared library compilation flags.
 if test -n "$ac_cv_prog_cc_shlib"; then
-  AC_MSG_WARN([\`$CC' requires \`$ac_cv_prog_cc_shlib' to build shared libraries])
+  lt_backtick='`' # workaround for "quoted backtick" warning from Autoconf.
+  AC_MSG_WARN([${lt_backtick}$CC' requires ${lt_backtick}$ac_cv_prog_cc_shlib' to 
+build shared libraries])
   if echo "$old_CC $old_CFLAGS " | [egrep -e "[        ]$ac_cv_prog_cc_shlib[  ]"] 
>/dev/null; then :
   else
-   AC_MSG_WARN([add \`$ac_cv_prog_cc_shlib' to the CC or CFLAGS env variable and 
reconfigure])
+   AC_MSG_WARN([add ${lt_backtick}$ac_cv_prog_cc_shlib' to the CC or CFLAGS env 
+variable and reconfigure])
     ac_cv_prog_cc_can_build_shared=no
   fi
 fi
@@ -886,7 +887,8 @@
   ln conftest.a conftest.b 2>/dev/null && hard_links=no
   AC_MSG_RESULT([$hard_links])
   if test "$hard_links" = no; then
-    AC_MSG_WARN([\`$CC' does not support \`-c -o', so \`make -j' may be unsafe])
+    lt_backtick='`' # workaround for "quoted backtick" warning from Autoconf.
+    AC_MSG_WARN([${lt_backtick}$CC' does not support ${lt_backtick}-c -o', so 
+${lt_backtick}make -j' may be unsafe])
     need_locks=warn
   fi
 else

Reply via email to