Failed to build "master" branch

[SchweinDeBurg]

I've tried to build from "master" branch and after commit aa55cc88 got the following error:

FAILED: doc/language.dox /home/elijah/.local/rpmbuild/BUILD/doxygen/x86_64-redhat-linux-gnu/doc/language.dox 
cd /home/elijah/.local/rpmbuild/BUILD/doxygen/x86_64-redhat-linux-gnu/doc && /usr/bin/python3.8 translator.py --doc /home/elijah/.local/rpmbuild/BUILD/doxygen

Unexpected token 'id' on the line 31 in '/home/elijah/.local/rpmbuild/BUILD/doxygen/src/translator.h'.
status = 2 in collectPureVirtualPrototypes()
ninja: build stopped: subcommand failed.
error: Bad exit status from /var/tmp/rpm-tmp.57KjKz (%build)

[albert-github]

I saw the same problem with the GitHub Actions.

I've just pushed a proposed patch, pull request #10791

[SchweinDeBurg]

I've tried to use proposed patch and got the following error:

Unexpected token 'lpar' on the line 31 in '/home/elijah/.local/rpmbuild/BUILD/doxygen/src/translator.h'.
status = 1 in collectPureVirtualPrototypes()

[albert-github]

Strange

• I tried it and had no problems
• GitHub actions https://github.com/doxygen/doxygen/actions/runs/8644051197 had no problems
• I see in the new code around line 717:

              elif status == 18:    # start of the ABSTRACT_BASE_CLASS
                if tokenId == 'lpar':
                    pass
                elif tokenId == 'rpar':
                    status = 2
                elif tokenId == 'id':
                    pass
                else:
                    self.__unexpectedToken(status, tokenId, tokenLineNo)
  

  So a lpar test is present as far as I can see.

Can you place a print statement at line 574 (i.e. direct after elif tokenId == 'id' and tokenStr == 'ABSTRACT_BASE_CLASS':):

  print("Found ABSTRACT_BASE_CLASS")

and after (new) line 718 (i.e. directly after elif status == 18: # start of the ABSTRACT_BASE_CLASS):

 print(f'id = {tokenId} Str = {tokenStr} line = tokenLineNo}');

[SchweinDeBurg]

FAILED: doc/language.dox /home/elijah/.local/rpmbuild/BUILD/doxygen/x86_64-redhat-linux-gnu/doc/language.dox 
cd /home/elijah/.local/rpmbuild/BUILD/doxygen/x86_64-redhat-linux-gnu/doc && /usr/bin/python3.8 translator.py --doc /home/elijah/.local/rpmbuild/BUILD/doxygen
  File "translator.py", line 719
    print(f'id = {tokenId" Str = {tokenStr} line = tokenLineNo}');
          ^
SyntaxError: f-string: unterminated string

[SchweinDeBurg]

Previous diff is exactly the same as PR:

diff --git a/doc/translator.py b/doc/translator.py
index e2037ac651..991d4570e6 100755
--- a/doc/translator.py
+++ b/doc/translator.py
@@ -570,6 +570,8 @@ class Transl:
                     pass
                 elif tokenId == 'rcurly':
                     status = 11         # expected end of class
+                elif tokenId == 'id' and tokenStr == 'ABSTRACT_BASE_CLASS':
+                    status = 1
                 else:
                     self.__unexpectedToken(status, tokenId, tokenLineNo)

@@ -712,6 +714,16 @@ class Transl:
                 else:
                     self.__unexpectedToken(status, tokenId, tokenLineNo)

+            elif status == 18:    # start of the ABSTRACT_BASE_CLASS
+                if tokenId == 'lpar':
+                    pass
+                elif tokenId == 'rpar':
+                    status = 2
+                elif tokenId == 'id':
+                    pass
+                else:
+                    self.__unexpectedToken(status, tokenId, tokenLineNo)
+
         # Eat the rest of the source to cause closing the file.
         while tokenId != 'eof':
             tokenId, tokenStr, tokenLineNo = next(tokenIterator)

[SchweinDeBurg]

I am a stupid!!!

+                    status = 1

instead of

+                    status = 18

[albert-github]

I see in your diff:

+                    status = 1

whilst in the patch this is:

+                    status = 18

so 1 (wrong) <-> 18 (correct)

[SchweinDeBurg]

@albert-github I am very sorry for my mistake, with your patch everything is fine. Thank you!

[albert-github]

Code has been integrated in master on GitHub.
Closing issue as the problem was a regression on the current master version and this was not yet released.