* acgeneral.m4 (AC_SHELL_UNSETENV, AC_SHELL_UNSET): Add the

missing quotes.
This commit is contained in:
Akim Demaille 2000-05-19 12:21:55 +00:00
parent 31dae2791f
commit 4126eddf68
3 changed files with 22 additions and 5 deletions

View File

@ -1,3 +1,8 @@
2000-05-19 Akim Demaille <akim@epita.fr>
* acgeneral.m4 (AC_SHELL_UNSETENV, AC_SHELL_UNSET): Add the
missing quotes.
2000-05-19 Akim Demaille <akim@epita.fr> 2000-05-19 Akim Demaille <akim@epita.fr>
* acgeneral.m4 (_AC_INIT_PARSE_ARGS): Prefer * acgeneral.m4 (_AC_INIT_PARSE_ARGS): Prefer

10
configure vendored
View File

@ -548,10 +548,10 @@ else
fi fi
# NLS nuisances. # NLS nuisances.
$ac_unset LANG || test ${LANG+set} != set || LANG=C && export LANG $ac_unset LANG || test "${LANG+set}" != set || LANG=C && export LANG
$ac_unset LC_ALL || test ${LC_ALL+set} != set || LC_ALL=C && export LC_ALL $ac_unset LC_ALL || test "${LC_ALL+set}" != set || LC_ALL=C && export LC_ALL
$ac_unset LC_CTYPE || test ${LC_CTYPE+set} != set || LC_CTYPE=C && export LC_CTYPE $ac_unset LC_CTYPE || test "${LC_CTYPE+set}" != set || LC_CTYPE=C && export LC_CTYPE
$ac_unset LC_MESSAGES || test ${LC_MESSAGES+set} != set || LC_MESSAGES=C && export LC_MESSAGES $ac_unset LC_MESSAGES || test "${LC_MESSAGES+set}" != set || LC_MESSAGES=C && export LC_MESSAGES
# IFS # IFS
# We need space, tab and new line, in precisely that order. # We need space, tab and new line, in precisely that order.
@ -560,7 +560,7 @@ ac_nl='
IFS=" $ac_nl" IFS=" $ac_nl"
# CDPATH. # CDPATH.
$ac_unset CDPATH || test ${CDPATH+set} != set || CDPATH=: && export CDPATH $ac_unset CDPATH || test "${CDPATH+set}" != set || CDPATH=: && export CDPATH
trap 'rm -fr conftest* confdefs* core core.* *.core $ac_clean_files; exit 1' 1 2 15 trap 'rm -fr conftest* confdefs* core core.* *.core $ac_clean_files; exit 1' 1 2 15

View File

@ -6808,6 +6808,7 @@ adaptations of their explanations here.
The following answer is based on one written by Richard Pixley: The following answer is based on one written by Richard Pixley:
@quotation
Autoconf generated scripts frequently work on machines which it has Autoconf generated scripts frequently work on machines which it has
never been set up to handle before. That is, it does a good job of never been set up to handle before. That is, it does a good job of
inferring a configuration for a new system. Imake cannot do this. inferring a configuration for a new system. Imake cannot do this.
@ -6832,9 +6833,12 @@ address these issues.
Imake templates are a form of standardization. The @sc{gnu} coding Imake templates are a form of standardization. The @sc{gnu} coding
standards address the same issues without necessarily imposing the same standards address the same issues without necessarily imposing the same
restrictions. restrictions.
@end quotation
Here is some further explanation, written by Per Bothner: Here is some further explanation, written by Per Bothner:
@quotation
One of the advantages of Imake is that it easy to generate large One of the advantages of Imake is that it easy to generate large
Makefiles using @code{cpp}'s @samp{#include} and macro mechanisms. Makefiles using @code{cpp}'s @samp{#include} and macro mechanisms.
However, @code{cpp} is not programmable: it has limited conditional However, @code{cpp} is not programmable: it has limited conditional
@ -6845,9 +6849,12 @@ All of these problems are solved by using @code{sh} instead of
@code{cpp}. The shell is fully programmable, has macro substitution, @code{cpp}. The shell is fully programmable, has macro substitution,
can execute (or source) other shell scripts, and can inspect its can execute (or source) other shell scripts, and can inspect its
environment. environment.
@end quotation
Paul Eggert elaborates more: Paul Eggert elaborates more:
@quotation
With Autoconf, installers need not assume that Imake itself is already With Autoconf, installers need not assume that Imake itself is already
installed and working well. This may not seem like much of an advantage installed and working well. This may not seem like much of an advantage
to people who are accustomed to Imake. But on many hosts Imake is not to people who are accustomed to Imake. But on many hosts Imake is not
@ -6870,9 +6877,12 @@ not @file{Makefile}s. This is much less of a problem with Autoconf,
which uses the general-purpose preprocessor @code{m4}, and where the which uses the general-purpose preprocessor @code{m4}, and where the
package's author (rather than the installer) does the preprocessing in a package's author (rather than the installer) does the preprocessing in a
standard way. standard way.
@end quotation
Finally, Mark Eichin notes: Finally, Mark Eichin notes:
@quotation
Imake isn't all that extensible, either. In order to add new features to Imake isn't all that extensible, either. In order to add new features to
Imake, you need to provide your own project template, and duplicate most Imake, you need to provide your own project template, and duplicate most
of the features of the existing one. This means that for a sophisticated of the features of the existing one. This means that for a sophisticated
@ -6889,6 +6899,8 @@ for the Kerberos V5 tree, we've modified things to call in common
@file{post.in} and @file{pre.in} @file{Makefile} fragments for the @file{post.in} and @file{pre.in} @file{Makefile} fragments for the
entire tree. This means that a lot of common things don't have to be entire tree. This means that a lot of common things don't have to be
duplicated, even though they normally are in @code{configure} setups. duplicated, even though they normally are in @code{configure} setups.
@end quotation
@c ================================================= Upgrading From Version 1. @c ================================================= Upgrading From Version 1.