On May 21, 2001, Akim Demaille <[EMAIL PROTECTED]> wrote:
> but in order to keep backward compatibility, 2.50 should probably just
> stick to what 2.13 said.
> Pavel, Alexandre, what shall we do?
I've been trying for days to find something useful to say about this.
I'm afraid I couldn't come up
"Lars J. Aas" wrote:
>
> On Tue, May 22, 2001 at 02:37:33PM +0200, Akim Demaille wrote:
> : > "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
> : Lars> Since this error message always uses the line-number of the
> : Lars> first macro and not the failed macro, couldn't we change scheme
> : La
On Tue, May 22, 2001 at 02:37:33PM +0200, Akim Demaille wrote:
: But, maybe there is something to do with traces. Trying to define the
: `undefined' symbols and trace there expansion. Hm. Nah, way too hard
: (since it means you have to disable quotation etc.), and in addition
: running traces d
On Tue, May 22, 2001 at 02:37:33PM +0200, Akim Demaille wrote:
: > "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
: Lars> Since this error message always uses the line-number of the
: Lars> first macro and not the failed macro, couldn't we change scheme
: Lars> to insert a line like the foll
> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
Lars> Since this error message always uses the line-number of the
Lars> first macro and not the failed macro, couldn't we change scheme
Lars> to insert a line like the following in `configure' for each
Lars> top-level macro invocation (hopefu
On Mon, May 21, 2001 at 08:45:32PM +0200, Akim Demaille wrote:
: | + After cleaning up the autoupdate warnings, I got the following warning
: | from autoconf:
: |
: | configure.in:1: error: possibly undefined macro: dnl
:
: Be aware that this message is definitely the sign that somethi
| In my configure.in file, I was doing:
|
| dnl Check for ANSI C exit success/failure values.
| AC_EGREP_CPP(yes, [dnl
| #include
| #ifdef EXIT_SUCCESS
| yes
| #endif], AC_DEFINE(HAVE_EXIT_SUCCESS))
|
| and the resulting output in
> Be aware that this message is definitely the sign that something is
> going wrong. If I were you, I'd restore the dnl, and would look for
> it in `configure' itself. It means that somewhere you were relying on
> the broken quotation of 2.13, or maybe that it is 2.50, trying to fix
> these issu
> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
Akim> It means that somewhere you were relying on the broken quotation
Akim> of 2.13, or maybe that it is 2.50, trying to fix these issues,
Akim> that broke your sources.
It can very well be a real bug in 2.50, your feedback is essential.