[PATCH] Fix for bootstrapping with latest CVS Autoconf

[Morten Eriksen]

Hi,

Autoconf straight out of CVS will complain about "backquotes and
doublequotes should not be backslashed" when expanding the macro code
of _LT_AC_LTCONFIG_HACK libtool.m4.

This is against the head branch -- I haven't checked if the 1.3 branch
and/or the multi-language branch should be fixed in the same manner.

BTW, there seems to be many minor problems when bootstrapping libtool
from the head CVS branch with the latest Autoconf and Automake
(i.e. from CVS). Is that supposed to work? If yes, I'll probably give
it a look-over and possibly send a bunch of patches to fix the issues
which pops up.

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-11  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/11 14:48:13
@@ -775,10 +775,10 @@
 
 # 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])
+  AC_MSG_WARN(['$CC' requires '$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 '$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 +886,7 @@
   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])
+AC_MSG_WARN(['$CC' does not support '-c -o', so 'make -j' may be unsafe])
 need_locks=warn
   fi
 else

Re: [PATCH] Fix for bootstrapping with latest CVS Autoconf

[Alexandre Oliva]

On Oct 11, 2000, Morten Eriksen <[EMAIL PROTECTED]> wrote:

> Autoconf straight out of CVS will complain about "backquotes and
> doublequotes should not be backslashed" when expanding the macro code
> of _LT_AC_LTCONFIG_HACK libtool.m4.

The problem is that CVS autoconf changes the way backquotes are
interpreted, and issues a warning (even though it works correctly) in
case they're written the way it used to work with autoconf 2.13.

Replacing \` with ' is even worse, because then the shell won't
expand the variable within `', as we want it.

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' ...])

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me

___
Libtool mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/libtool