threads / discuss / 15813

proper flags for make check ?

Subject: proper flags for make check ?

## tl;dr

One message between Oct 7, 2008 and Oct 7, 2008.

replies: 0people: 1as markdown or json

David Bryson· Oct 7, 2008, 15:46 UTC · lore

After the recent discussion about make check I decided to give it a try and see what happens.

I installed sparse, took a look at the source and it appears to want something along the following lines for a intel processor:

-D__LITTLE_ENDIAN__ -D__i386__=1

I then type 'make check' and get about 30 seconds of errors printing out for kerberos headers.

The errors look a lot like this:

/usr/include/krb5/krb5.h:1166:18: error: got * /usr/include/krb5/krb5.h:1167:18: error: Expected ; at end of declaration /usr/include/krb5/krb5.h:1167:18: error: got * /usr/include/krb5/krb5.h:1168:20: error: Expected ; at end of declaration /usr/include/krb5/krb5.h:1168:20: error: got * /usr/include/krb5/krb5.h:1169:1: error: Expected ; end of type declaration /usr/include/krb5/krb5.h:1169:1: error: got } /usr/include/krb5/krb5.h:1173:17: error: expected ; at end of declaration /usr/include/krb5/krb5.h:1173:17: error: Expected } at end of struct-union-enum-specifier

What is the proper way to run sparse on the git sources ?
Dave

← back to recent threads