[Top][All Lists]

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

[sr #110312] 2.69b: broken AC_PROG_LEX macro

From: Zack Weinberg
Subject: [sr #110312] 2.69b: broken AC_PROG_LEX macro
Date: Tue, 3 Nov 2020 10:23:14 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

Follow-up Comment #9, sr #110312 (project autoconf):

I've gone ahead and applied Jannick's suggested change (commit
15ada9d3a0e46c28c0a3af2357b64bbd14d818a8), since I don't see any way it could
_hurt_, but I do not understand why it makes a difference, and I still can't
reproduce the original problem on my computer.  Before I call this bug "fixed"
I want to understand what the original problem was and why the changes we've
made actually fix it.

@Jannick Can you reproduce the original problem?  If so, can you go into
detail about the conditions where it happens?  Information that might be
relevant includes:

 - a minimal configure.ac that reproduces the problem, if that's different
from the one that I said didn't reproduce it for me
 - the config.log from a run that reproduces the problem
 - the git commit hash for the version of autoconf used to reproduce the
 - whether the problem can still be reproduced with autoconf built from git
commit 15ada9d3a0e46c28c0a3af2357b64bbd14d818a8
 - whether you have flex or classic lex, its exact version number, and whether
redistributors have applied their own patches
 - the config.guess triplet for the OS where you could reproduce the problem
 - the "distribution" of the OS, if there is such a thing and it's not named
in the config.guess triplet
 - the output of `find /lib /usr \( -name libl.* -o -name libfl.* \) -ls 2>
 - the output of `cc -print-search-dirs`

Thanks in advance for your help.


Reply to this item at:


  Message sent via Savannah

reply via email to

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