Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failure to build packages with win_flex due to reuse of temporary file in parallel processing #580

Open
albert-github opened this issue Sep 5, 2023 · 3 comments

Comments

@albert-github
Copy link

When we build doxygen with win_flex 2.6.4, build system Ninja and build in parallel we get warnings like:

win_flex.exe: error deleting file C:\Users\VSSADM~1\AppData\Local\Temp\~flex_out_main_2

(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 find flex_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).

  • looks like winflex creates a temporary file and removes it but that this filename is not unique when running in parallel and thus causing problems.

For the time being the build process is ran in serial mode but this is of course far slower.

Relevant issues:

@westes
Copy link
Owner

westes commented Sep 5, 2023

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).

@albert-github
Copy link
Author

albert-github commented Sep 5, 2023

@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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants