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

2000-10-12 Thread Morten Eriksen

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



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

2000-10-12 Thread Alexandre Oliva

On Oct 12, 2000, Akim Demaille [EMAIL PROTECTED] wrote:

 This is s heavy :( As I proposed to Pavel, I'm OK with moving this
 warning from `syntax' to `obsolete' for 2.50, and move it back to
 `syntax' in 2.51 or later.

Probably later :-)

 This way, every body is happy.  ?

I'm definitely in favor of this change.

-- 
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



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

2000-10-12 Thread Akim Demaille

 "Alexandre" == Alexandre Oliva [EMAIL PROTECTED] writes:

Alexandre I'm definitely in favor of this change.

OK I consider this an OK and will apply the change directly.

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



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

2000-10-12 Thread Gary V. Vaughan

On Thu, Oct 12, 2000 at 12:38:11PM +0200, Morten Eriksen wrote:
 
 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?

It's all part of a big here document that writes the results of the
tests run by libtool.m4 to the start of the generated libtool script.

For example libtool.m4 contains tests which discover that on the host
system, MAGIC_CMD needs to be /usr/bin/file, so it writes the
following snippet into the libtool script:

# Used to examine libraries when file_magic_cmd begins "file"
MAGIC_CMD="/usr/bin/file"

And that, in turn is generated by the here document you quoted above.

Cheers,
Gary.
-- 
  ___  _   ___   __  _ mailto: [EMAIL PROTECTED]
 / __|__ _ _ ___ _| | / / | / /_ _ _  _ __ _| |_  __ _ ___   [EMAIL PROTECTED] 
| (_ / _` | '_|// / |/ /| |/ / _` | || / _` | ' \/ _` | _ \
 \___\__,_|_|\_, /|___(_)___/\__,_|\_,_\__, |_||_\__,_|//_/
home page:  /___/  /___/  gpg public key:
http://www.oranda.demon.co.uk   http://www.oranda.demon.co.uk/key.asc

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



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

2000-10-11 Thread 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