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
problem
- 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>
/dev/null`
- the output of `cc -print-search-dirs`
Thanks in advance for your help.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?110312>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
