Peter Eisentraut writes:
> > 1) autoconf is not C. autoconf's input is processed through *m4*, and
> > results in *sh* output. ...
>
> The fact is that the space-separated lists are not
> "native" to the m4 language.
But space-separated lists are "native" to the sh language. So they
occur
This section of the automatically generated configure script
# NLS nuisances.
for as_var in LANG LANGUAGE LC_ALL LC_COLLATE LC_CTYPE
LC_NUMERIC LC_MESSAGES LC_TIME
do
if (set +x; test -n "`(eval $as_var=C; export $as_var)
2>&1`"); then
I have a few "antique" computers. The first Compaq, A very early
Sun SPARC 1. a Mac before they offered a hard drive and others
Had a VAX too, but no place to store it and some guy offered me
$1,500 for the tape drive...
These machines are only worth keeping if you still have the old
software t
Bruce Korb <[EMAIL PROTECTED]> writes:
> Eric Siegerman wrote:
>
> > Hmmm, that brings up GCC. I know they have their own reasons for
> > sticking with 2.13 (or had, last time I checked), but AC's
> > dropping old-box support might be one more, given that GCC is
> > seen as (among other things)
We're pleased to announce the release of Automake 1.7.3
This is a bug fix release. The list of bug fixes is appended.
You can find the new release here:
ftp://ftp.gnu.org/gnu/automake/automake-1.7.3.tar.bz2
ftp://ftp.gnu.org/gnu/automake/automake-1.7.3.tar.gz
ftp://sources.redhat.com
