After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 755786 - fatal: Cannot open 'graph_legend': No such file or directory
fatal: Cannot open 'graph_legend': No such file or directory
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.9.1
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2015-09-29 12:52 UTC by Frank HJ Cuypers
Modified: 2015-12-30 10:20 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Example project (85.89 KB, application/x-7z-compressed)
2015-09-29 12:52 UTC, Frank HJ Cuypers 		Details

Description Frank HJ Cuypers 2015-09-29 12:52:12 UTC 
Created attachment 312358 [details]
Example project

I get a "fatal: Cannot open 'graph_legend': No such file or directory" error when I run doxygen. Output however seems to be generated OK.

I work in a Git workspace and have set
FILE_VERSION_FILTER    = "git hash-object"
Whithout FILE_VERSION_FILTER there is no problem.
When I set QUIET = NO, it becomes clear that the error occurs when trying to get the version of 'graph_legend'.

For reproducing; unzip the attachment and run 'doxygen' in a bash script in the examples directory (with Git installed)
Comment 1 albert 2015-09-29 18:02:03 UTC 
Problem occurs with all commands used for FILE_VERSION_FILTER, graph_legend is a generated files and should be excluded from the filter process.

I've just pushed a proposed solution to github (pull request 399)
Comment 2 Dimitri van Heesch 2015-10-04 14:22:07 UTC 
Thanks, I've merged the pull request
Comment 3 Dimitri van Heesch 2015-12-30 10:20:05 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.11. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information 
that you think can be relevant (preferably in the form of a self-contained example).