Bug 224

Summary:	After compiling liblscp make check errors
Product:	liblscp	Reporter:	janflorijn <janflikweert>
Component:	liblscp	Assignee:	Rui Nuno Capela <rncbc>
Status:	CLOSED WORKSFORME
Severity:	enhancement	CC:	cuse, janflikweert
Priority:	P5
Version:	unspecified
Hardware:	PC
OS:	Linux

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.

Comment 2 Christian Schoenebeck 2019-02-27 15:30:36 CET

I am closing this report now. If you still think this is an issue that should be resolved, then feel free to reopen this report. Thanks!