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 681209 - Reference list generation fails for LaTeX if a space is in the path name
Reference list generation fails for LaTeX if a space is in the path name
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.1.1
Other Mac OS
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2012-08-04 19:54 UTC by Thomas Guymer
Modified: 2013-01-14 18:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Self contained example (22.65 KB, application/zip)
2012-08-07 16:52 UTC, Thomas Guymer
Details

Description Thomas Guymer 2012-08-04 19:54:38 UTC
The reference list for LaTeX documentation fails to be generated if the path contains a space. The following output is given by doxygen:

Can't open perl script "/Users/guymer1/Work/Data/2011-06": No such file or directory
make -f documentation/latex/Makefile
rm -f *.ps *.dvi *.aux *.toc *.idx *.ind *.ilg *.log *.out *.brf *.blg *.bbl refman.pdf
make[1]: *** No rule to make target `refman.tex', needed by `refman.pdf'.  Stop.
make: *** [documentation] Error 2

The correct folder path is "/Users/guymer1/Work/Data/2011-06 TGS/make_streaked_fake_data/documentation" not "/Users/guymer1/Work/Data/2011-06". Note that it truncates the path at the exact place that a space exists.
Comment 1 Dimitri van Heesch 2012-08-05 20:28:59 UTC
Hi Thomas,

This error doesn't seem like something doxygen produces, but rather a script that (amongst others) runs doxygen. If you think it really is a doxygen issue, then please attach a self-contained example (source+config file in a tar or zip) that allows me to reproduce the problem.
Comment 2 Thomas Guymer 2012-08-07 16:52:03 UTC
Created attachment 220585 [details]
Self contained example

Self contained example
Comment 3 Thomas Guymer 2012-08-07 16:54:05 UTC
So, if I run "doxygen" on the attached files in "/Users/guymer1/Documents/doxygen_test" I get the following output:

citelist:3: warning: expected <dt> tag but found <dl> instead!
citelist:4: warning: unexpected end of comment while looking for a html description title

If I rename the directory to "/Users/guymer1/Documents/doxygen test" and update the doxygen configuration file with the new paths then I get the following output instead:

Can't open perl script "/Users/guymer1/Documents/doxygen": No such file or directory

Thanks
Comment 4 Thomas Guymer 2012-09-11 18:52:00 UTC
(In reply to comment #1)
> Hi Thomas,
> 
> This error doesn't seem like something doxygen produces, but rather a script
> that (amongst others) runs doxygen. If you think it really is a doxygen issue,
> then please attach a self-contained example (source+config file in a tar or
> zip) that allows me to reproduce the problem.

So, I have uploaded a self contained example for you, thanks.
Comment 5 Dimitri van Heesch 2012-09-16 13:15:53 UTC
Turns out that bibtex itself does not seem to be able to handle spaces.
The only solution I see is to (temporarily) copy the .bib files to the directory from which bibtex is run, so bibtex can find the files without path. 

I'll include this approach in the next subversion update.
Comment 6 Thomas Guymer 2012-09-21 08:40:58 UTC
(In reply to comment #5)
> Turns out that bibtex itself does not seem to be able to handle spaces.
> The only solution I see is to (temporarily) copy the .bib files to the
> directory from which bibtex is run, so bibtex can find the files without path. 
> 
> I'll include this approach in the next subversion update.

Thank you for looking into this for me!

I'll look forward to the next subversion update, :)
Comment 7 Dimitri van Heesch 2012-12-26 16:09:23 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.3. 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.
Comment 8 Thomas Guymer 2013-01-14 18:04:25 UTC
I can confirm that this bug is resolved in version 1.8.3, thank you very much for the bug fix.