Open albert-github opened 1 year ago
As an initial sanity check, where is "win_flex" coming from -- that's not a name that the flex project itself uses. I'm wondering if there is an intermediate package/distribution happening that has introduced the problem (but I'm happy to help fix the issue wherever it is).
@westes thanks for the quick response.
Difficult question had to do quite a bit of digging, as far as I can tell it comes from https://sourceforge.net/projects/winflexbison/files/ and has there the name: win_flex_bison-latest.zip (checked the execuable in that package and mine and they had the same md5sum).
I don't know where @tdegeus got his executable from (he found the problem and reported it. I tried with Ninja as well and seemingly had no problems).
It comes from conda-forge:
(i.e. it is build : https://github.com/conda-forge/winflexbison-feedstock/blob/main/recipe/bld.bat )
When we build doxygen with win_flex 2.6.4, build system Ninja and build in parallel we get warnings like:
(doxygen uses a number of lex files that are build).
When looking in the executable I cannot find the
flex_out_main_2
string but I do findflex_out_main_XXXXXX
though I haven't been able to find this in the repository (also not in the sources of the 2.6.4 version).For the time being the build process is ran in serial mode but this is of course far slower.
Relevant issues: