On Wed, 2009-07-15 at 20:53 +0800, Xiaofan Chen wrote:
> On Sat, Jul 11, 2009 at 10:04 PM, Xiaofan Chen<[email protected]> wrote:
> > On Tue, Jul 7, 2009 at 8:08 PM, Øyvind Harboe<[email protected]> 
> > wrote:
> >>> Do you have GraphViz installed?
> >>
> >> I've tried to install it, but same result.
> >>
> >> Do you have another apt-get I can try? :-)
> >>
> >
> > Maybe this will help but I am not a doxygen expert.
> > http://mihirknows.blogspot.com/2008/03/error-opening-map-file-map-for.html
> >
> 
> Today I actually met the same problem under Fedora 10. I did not
> install GraphViz initially so that "make docs" failed. Then I installed
> GraphViz, and then I met the same problem of getting lots of
> errors regarding the .map files.
> 
> Google comes to the rescue again. Comment 3 of the following
> thread helped me to solve the problem. I have to do a
> "make distclean" and then all is working.
> http://bugzilla.gnome.org/show_bug.cgi?id=525273
> 
> There are a few warnings though.
> 
> Warning: ignoring unsupported tag `EXTENSION_MAPPING      =' at line
> 221, file Doxyfile
> Warning: ignoring unsupported tag `QHP_CUST_FILTER_NAME   =' at line
> 917, file Doxyfile
> Warning: ignoring unsupported tag `QHP_CUST_FILTER_ATTRS  =' at line
> 922, file Doxyfile
> Warning: ignoring unsupported tag `QHP_SECT_FILTER_ATTRS  =' at line
> 928, file Doxyfile
> Warning: tag INPUT: input source `../trunk/config.h' does not exist
> .................
> Searching for files in directory
> /home/mcuee/Desktop/build/openocd/trunk/src/target/ecosWarning: source
> ../trunk/config.h is not a readable file or directory... skipping.
> 

Except for the last, these warnings probably come from using an older
version of Doxygen; I have 1.5.8 here.  The warning about config.h is
confusing though; that file should exist, if you have the Makefile.
Perhaps it is created in the $(builddir), not $(srcdir)?

--Z
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to