Bug 481 - ./waf --doxygen gives errors "Error: Could not extract bounding box from .eps!"
./waf --doxygen gives errors "Error: Could not extract bounding box from .e...
Status: RESOLVED INVALID
Product: ns-3
Classification: Unclassified
Component: documentation
ns-3-dev
All All
: P5 minor
Assigned To: ns-bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-01-24 05:04 UTC by Andrey Hippo
Modified: 2009-01-25 15:15 UTC (History)
1 user (show)

See Also:


Attachments
Proposed fix (499 bytes, patch)
2009-01-24 05:04 UTC, Andrey Hippo
Details | Diff
Full ./waf --doxygen log (17.32 KB, text/plain)
2009-01-24 05:05 UTC, Andrey Hippo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey Hippo 2009-01-24 05:04:37 UTC
Created attachment 362 [details]
Proposed fix

Trying to generate documentation:
1) ./waf configure --disable-python -d optimized
2) ./waf build
3) ./waf check
4) ./waf --doxygen

Stages 1), 2), 3) work correctly, but the stage 4) gives many errors like (full log in the attachment):
Error: Could not extract bounding box from .eps!
Error: Could not extract bounding box from .eps!
Error: Could not extract bounding box from .eps!
Error: Could not extract bounding box from .eps!


All required packages like doxygen, graphviz, imagemagick, ghostscript-gpl, texlive are installed.
Though on another system everything works fine.
Both systems are Gentoo Linux on x86, but the first is configured mostly as server while the second is a desktop.

The possible solution is to change doxygen option "SHORT_NAMES" to "YES".
(I can't understand why it helps, because filesystems and kernel configs are equal on both systems)
Comment 1 Andrey Hippo 2009-01-24 05:05:40 UTC
Created attachment 363 [details]
Full ./waf --doxygen  log
Comment 2 Tom Henderson 2009-01-24 11:55:02 UTC
(In reply to comment #0)
> Created an attachment (id=362) [details]
> Proposed fix
> 
> Trying to generate documentation:
> 1) ./waf configure --disable-python -d optimized
> 2) ./waf build
> 3) ./waf check
> 4) ./waf --doxygen
> 
> Stages 1), 2), 3) work correctly, but the stage 4) gives many errors like (full
> log in the attachment):
> Error: Could not extract bounding box from .eps!
> Error: Could not extract bounding box from .eps!
> Error: Could not extract bounding box from .eps!
> Error: Could not extract bounding box from .eps!


I can't reproduce this problem.  It seems to me to be most likely due to missing packages; as you note, on another system, it works fine.

Can you check whether any .eps (there should be about 388 files) are generated in ns-3/doc/latex directory?


Can you make sure you have all of these packages installed?
 sudo apt-get install doxygen graphviz imagemagick
 sudo apt-get install texlive texlive-pdf texlive-latex-extra
Comment 3 Andrey Hippo 2009-01-25 15:15:57 UTC
(In reply to comment #2)
> I can't reproduce this problem.  It seems to me to be most likely due to
> missing packages; as you note, on another system, it works fine.
> 
> Can you check whether any .eps (there should be about 388 files) are generated
> in ns-3/doc/latex directory?
> 
> 
> Can you make sure you have all of these packages installed?
>  sudo apt-get install doxygen graphviz imagemagick
>  sudo apt-get install texlive texlive-pdf texlive-latex-extra
> 

Oops..
I've tried to "rm -rf ./ns-3" and to clone again the repository.
And now everything works fine.
Probably there was some ancient junk because of "./waf distclean" not doing its job well.
I'm really sorry to trouble you!


P.S.
Yes, I've checked, that all packages are installed.
Before removal there were 48 files named "group__*.eps" in "doc/latex".