[splint-discuss] splint-3.1.2/install/running split on itself

[Bill Pringlemeir]

On 20 May 2010, mikereape at onetel.com wrote:

> I am just getting started with splint.  When I did './configure' in the
> 'splint-3.1.2' dir it produced three errors in 'config.log'.  One on:
>> | #ifndef __cplusplus
>> |   choke me
>> | #endif
> and two on tests using 'mode_t' as a declaration in programs doing 
> '#include <stdio.h>'.

> The actual install was fine.  'make check' and 'make install' produced
> no errors, warnings or failed checks.

If 'make check' did not produce any errors, I think you have built it
properly.  Looking through the config.log is a little paranoid.
System headers often have 'magic' in them that is not ANSI 'C' or at
least it is difficult for splint (or any source analyzer) to
understand every system file on the planet.  Hence you can have
libraries with annotation in splint.

> To get started I thought I'd run splint on itself. 

Try 'make lintnew' or one of the others.

> Can somebody tell me what is up with the three config errors ...

You didn't post the full output.  Why do you think they are errors?
Splint might try to use a system file and if it is not parsable
substitute something else (some other annotated header, etc) and you
might not get all of the symbols in your system headers [which
shouldn't matter depending on your perspective].

> and what combination of flags and +H includes I should specify to
> get splint to run all the way through on itself?

Error! Redundant text. Aborting!!!

-- 
Yow!  Legally-imposed CULTURE-reduction is CABBAGE-BRAINED!