[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Autoconf-patches] Re: config.status vs. zsh

From: Pavel Roskin
Subject: [Autoconf-patches] Re: config.status vs. zsh
Date: Mon, 18 Sep 2000 17:09:09 -0400 (EDT)

Hello, Akim!

> Pavel> Or maybe you mean expanding the whole
> Pavel> _AC_INIT_PREPARE_ENVIRONMENT to config.status? 
> Yes.
> Pavel> This is probably an overkill, but I can do it if you are
> Pavel> suggesting it.
> Well, not that much actually.  OK, there is too much because of LC_ALL
> etc., but it's sane to do that in fact.  And I will feel better to
> know that the sanitizing code for shell scripts will really be factored.

Ok, you wanted it, not me :-)

Although I still don't feel comfortable about using Autoconf macros in
config.status, in this particular case the emitted code looks reasonably
and no uninitialized variables are used. And, yes, config.status still
works after that :-)

        * acgeneral.m4 (_AC_OUTPUT_CONFIG_STATUS): use
        _AC_INIT_PREPARE_ENVIRONMENT to make the shell running
        config.status sane and POSIX-compatible.        

--- acgeneral.m4        Mon Sep 18 08:29:44 2000
+++ acgeneral.m4        Mon Sep 18 16:42:32 2000
@@ -4378,6 +4378,7 @@
 # Compiler output produced by configure, useful for debugging
 # configure, is in ./config.log if it exists.
 me=`echo "$[0]" | sed 's,.*/,,'`

Pavel Roskin

reply via email to

[Prev in Thread] Current Thread [Next in Thread]