doxygen v1.9.8

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

• Dependencies have been updated if changed: see upstream
• Tests have passed
• Updated license if changed and license_file is packaged

Information about this PR:

1. Feel free to push to the bot's branch to update this PR if needed.
2. The bot will almost always only open one PR per version.
3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
4. If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
5. If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

Dependency Analysis

We couldn't run dependency analysis due to an internal error in the bot, depfinder, or grayskull. :/ Help is very welcome!

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/5978716903, please use this URL for debugging.}

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[tdegeus]

debugging on doxygen/doxygen#10262

[tdegeus]

Does this level of verbosity help @albert-github ?

[albert-github]

@tdegeus investigating ... one thing I saw it looks like a general problem as now the problem occurs with a different .l file.

[albert-github]

I still get the impression that there is a parallel run (even though I see the change: 4c9524e).
I base my suspicion on the fact that that there are a number of blocks of 2 occurrences with scan_states.py followed by a block with pre_lex.py (see 100/267 ff) and also that at once in the middle there is a compilation of trace.cpp (see 106/267).

Used log file https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=771691&view=logs&j=a70f640f-cc53-5cd3-6cdc-236a1aa90802&t=f5d15007-a01c-5ad8-c9ce-4d519d3b275f in raw form https://dev.azure.com/conda-forge/84710dde-1620-425b-80d0-4cf5baca359d/_apis/build/builds/771691/logs/25

In Cygwin I see, when running wit 1 process) each time a sequence of:

• running pre_lex.py
• running flex
• running post_lex.py
• running scan_states.py

The parallel suspicion is also fed due to the error line:

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

looks a bit like a temporary file is created and that this file already has been deleted.
I didn't find an option with win_flex (I use under Windows also the 2.6.4 version) to change the temporary file.
On GitHub Actions and I myself have no problem as here nmake is used and this cannot run parallel.

[tdegeus]

I see... Should we:

• Force the number of cpus to 1?
• Use nmake here too?

[albert-github]

It depends a bit on how easy it is to switch to nmake but seen the constructs so far:

• I would first try to force number of cpus to 1

[albert-github]

Looks like the windows version finished.

[tdegeus]

Nice!! The error remains mysterious to me. But for here that is of no concern. I will clean-up and merge. I think it is best if you decide to summarise on doxygen/doxygen#10262 and/or close.

[tdegeus]

Note for here, actually I think it is fine to leave some verbosity.

[albert-github]

Filed an issue with flex: westes/flex#580