Re: Release candidate

On May 14, 2001, "Steve M. Robbins" <[EMAIL PROTECTED]> wrote: > Is it common to use a macro that expands to an lvalue? We've been using this to rename variables but keep them working for backward compatibility. -- Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/ Red Hat

Re: Release candidate

On Mon, May 14, 2001 at 05:50:50PM +0200, Akim Demaille wrote: > > | On Mon, May 14, 2001 at 04:57:57PM +0200, Peter Eisentraut wrote: > | > Akim Demaille writes: > | > > | > > | There is still the problem that autoconf mixes up variable assignments > | > > | and macros. This is up-to-the-minut

Re: Release candidate

| On Mon, May 14, 2001 at 04:57:57PM +0200, Peter Eisentraut wrote: | > Akim Demaille writes: | > | > > | There is still the problem that autoconf mixes up variable assignments | > > | and macros. This is up-to-the-minute CVS autoconf: | > > | | > > | steve@riemann{tmp}cat configure.in

Re: Release candidate

On Mon, May 14, 2001 at 04:57:57PM +0200, Peter Eisentraut wrote: > Akim Demaille writes: > > > | There is still the problem that autoconf mixes up variable assignments > > | and macros. This is up-to-the-minute CVS autoconf: > > | > > | steve@riemann{tmp}cat configure.in > > | A

Re: Release candidate

Akim Demaille writes: > | There is still the problem that autoconf mixes up variable assignments > | and macros. This is up-to-the-minute CVS autoconf: > | > | steve@riemann{tmp}cat configure.in > | AC_INIT > | > | AM_CFLAGS=foo > | steve@riemann{tmp}autoconf > |

Re: Release candidate

On Mon, May 14, 2001 at 02:32:13PM +0200, Akim Demaille wrote: > > | There is still the problem that autoconf mixes up variable assignments > | and macros. This is up-to-the-minute CVS autoconf: > | > | steve@riemann{tmp}cat configure.in > | AC_INIT > | > | AM_CFLAGS=fo

Re: Release candidate

| There is still the problem that autoconf mixes up variable assignments | and macros. This is up-to-the-minute CVS autoconf: | | steve@riemann{tmp}cat configure.in | AC_INIT | | AM_CFLAGS=foo | steve@riemann{tmp}autoconf | configure.in:3: error: undefi

Re: Release candidate

> "Harlan" == Harlan Stenn <[EMAIL PROTECTED]> writes: Harlan> What version(s) of automake should be used with this Harlan> candidate? I'm unsure I understand what you mean. Autoconf is independent from Automake, so any Automake should work properly. If 1.4 breaks with it, it's a show stop

Re: Release candidate

On Sun, May 13, 2001 at 07:54:31PM +0200, Akim Demaille wrote: > > Please people, test it: the current state of Autoconf is our release > candidate. There is one issue that must be fixed before releasing, > namely the test `compile.at:AC_PROG_CPP via CC' is not robust to > broken cc for not usin

Re: Release candidate

> From: Harlan Stenn <[EMAIL PROTECTED]> > Date: Sun, 13 May 2001 16:14:26 -0400 > > :pserver:[EMAIL PROTECTED]:/cvs/automake Ah, so you're an old fogy too. (:-) > What, if any, is the difference between this repository and the one at > > None. "sour

Re: Release candidate

Thanks! I have been using :pserver:[EMAIL PROTECTED]:/cvs/automake to get automake. What, if any, is the difference between this repository and the one at ??? H

Re: Release candidate

> From: Harlan Stenn <[EMAIL PROTECTED]> > Date: Sun, 13 May 2001 14:05:36 -0400 > > What version(s) of automake should be used with this candidate? I have been using recent CVS snapshots of automake which I got from . Currently I'm using a snapshot that I t

Re: Release candidate

What version(s) of automake should be used with this candidate? H