From: Josh Triplett <josh@joshtriplett.org>
To: bonneta <bonneta@ensimag.fr>
Cc: linux-sparse@vger.kernel.org
Subject: Re: help for using sparse
Date: Wed, 9 Jun 2010 09:10:59 -0700 [thread overview]
Message-ID: <20100609161058.GA4204@feather> (raw)
In-Reply-To: <cd2a19702bb05b6f27255cd697b0ea12@ensimag.fr>
On Wed, Jun 09, 2010 at 05:09:54PM +0200, bonneta wrote:
> I am working on git, and i would like to apply sparse on its source code.
>
> I've downloaded the source of sparse from its git repository, and compiled
> it successfully.
>
> I've read the little documentation furnished with the code, but i didn't
> manage to apply sparse on the sources of git.
>
> I've basically tried "sparse file.c", but it always returns with an error
> like :
> "git-compat-util.h:140:11: error: unable to open 'openssl/ssl.h'"
> or
> "builtin/blame.c:7:10: error: unable to open 'cache.h'"
>
> I don't know how to resolve it...
These errors occur because you haven't supplied the full compiler
command-line that Git supplies in its build process, which includes
flags for include paths.
The script "cgcc", provided with sparse, provides the most convenient
way to integrate Sparse into an existing build system with minimal work.
Once you've done a "make install" of Sparse into a directory on your
$PATH (or just put the Sparse source directory on your $PATH), just do
"make CC=cgcc".
- Josh Triplett
next prev parent reply other threads:[~2010-06-09 16:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 15:09 help for using sparse bonneta
2010-06-09 16:00 ` Christopher Li
2010-06-09 16:01 ` Dan Carpenter
2010-06-09 16:10 ` Josh Triplett [this message]
2010-06-09 16:35 ` bonneta
2010-06-09 16:59 ` Dan Carpenter
2010-06-09 18:48 ` Sam Ravnborg
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=20100609161058.GA4204@feather \
--to=josh@joshtriplett.org \
--cc=bonneta@ensimag.fr \
--cc=linux-sparse@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).