Bug 224 - After compiling liblscp make check errors
Summary: After compiling liblscp make check errors
Status: RESOLVED WORKSFORME
Alias: None
Product: liblscp
Classification: Unclassified
Component: liblscp (show other bugs)
Version: unspecified
Hardware: PC Linux
: P5 enhancement
Assignee: Rui Nuno Capela
URL:
Depends on:
Blocks:
 
Reported: 2014-06-26 21:58 CEST by janflorijn
Modified: 2017-01-03 13:27 CET (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description janflorijn 2014-06-26 21:58:52 CEST
After ./configure en make check I got the nect output on screen:
Generating index page...
/home/janflorijn/Installatie/LS/liblscp/doc/reference.dox:54: warning: explicit link request to 'include' could not be resolved
/home/janflorijn/Installatie/LS/liblscp/doc/reference.dox:54: warning: expected whitespace after : command
/home/janflorijn/Installatie/LS/liblscp/doc/reference.dox:77: warning: unable to resolve reference to `lscp_client_get_result(client)' for \ref command
/home/janflorijn/Installatie/LS/liblscp/doc/reference.dox:83: warning: unable to resolve reference to `lscp_client_get_errno(client)' for \ref command
/home/janflorijn/Installatie/LS/liblscp/doc/reference.dox:115: warning: expected whitespace after : command
/home/janflorijn/Installatie/LS/liblscp/doc/reference.dox:180: warning: expected whitespace after : command
/home/janflorijn/Installatie/LS/liblscp/doc/reference.dox:223: warning: explicit link request to 'include' could not be resolved
/home/janflorijn/Installatie/LS/liblscp/doc/reference.dox:223: warning: expected whitespace after : command
Generating page index...
Generating module index...
Generating namespace index...
Generating namespace member index...
Generating annotated compound index...
Generating alphabetical compound index...
Generating hierarchical class index...
Generating member index...
Generating file index...
Generating file member index...
Generating example index...
finalizing index lists...
lookup cache used 672/65536 hits=10009 misses=713
finished...

How to solve this?
Comment 1 Christian Schoenebeck 2017-01-03 13:27:53 CET
These are just Doxygen warnings, not errors, and they only concern the automatic generation of the API documentation, not any aspect of the software.