linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: Josh Triplett <josh@freedesktop.org>, linux-sparse@vger.kernel.org
Subject: Re: sparse as a compiler front-end
Date: Sat, 09 Dec 2006 05:17:46 -0500	[thread overview]
Message-ID: <457A8D4A.5060007@garzik.org> (raw)
In-Reply-To: <20061208193418.GA17790@lists.us.dell.com>

Matt Domsch wrote:
> On Tue, Dec 05, 2006 at 08:53:04AM -0800, Josh Triplett wrote:
>> Josh Triplett wrote:
>>> Jeff Garzik wrote:
>>>> Can libsparse.a and necessary includes be packaged as well?
>>> Sure, assuming you don't mind coding against something potentially fluid.  The
>>> next release will install the library and headers.  (At the moment, "necessary
>>> headers" seems to mean "all of them".)
>> The Sparse 0.2 release installs the library and headers, as well as a
>> pkg-config file.
> 
> I've got a test build of sparse-0.2 posted at
> http://domsch.com/linux/fedora/extras/sparse/0.2/ which I intend to
> put into Fedora Extras for FC5,6,devel.  This puts the libsparse.a and
> headers into a -devel package.
> 
> Jeff, does this suit your needs?

Yep, both sparse and sparse-devel look great, here on FC6!

Thanks,

	Jeff

  parent reply	other threads:[~2006-12-09 10:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-11 21:54 sparse as a compiler front-end Jeff Garzik
2006-11-11 23:50 ` Matt Domsch
2006-11-12  1:45   ` Jeff Garzik
2006-11-12  3:04     ` Matt Domsch
2006-11-12  3:22       ` Jeff Garzik
2006-11-12  1:32 ` Josh Triplett
2006-12-05 16:53   ` Josh Triplett
2006-12-08 19:34     ` Matt Domsch
2006-12-09  9:43       ` Josh Triplett
2006-12-09 10:15         ` Jeff Garzik
2007-02-28  1:36           ` Josh Triplett
2006-12-09 10:17       ` Jeff Garzik [this message]
2006-12-09 16:17         ` Matt Domsch

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=457A8D4A.5060007@garzik.org \
    --to=jeff@garzik.org \
    --cc=Matt_Domsch@dell.com \
    --cc=josh@freedesktop.org \
    --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).