From: David Bryson <david@statichacks.org>
To: git@vger.kernel.org
Subject: proper flags for make check ?
Date: Tue, 7 Oct 2008 08:46:43 -0700 [thread overview]
Message-ID: <20081007154643.GA5774@eratosthenes.cryptobackpack.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]
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
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
reply other threads:[~2008-10-07 15:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081007154643.GA5774@eratosthenes.cryptobackpack.org \
--to=david@statichacks.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).