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

[-- Attachment #1: Type: text/plain, Size: 974 bytes --]

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.

From the spec file, I notice that you install the pkg-config file to
/usr/lib/pkgconfig (or equivalent), rather than /usr/share/pkgconfig (or
equivalent) as the Makefile does; any particular reason for that?

- Josh Triplett


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2006-12-09  9:43 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 [this message]
2006-12-09 10:15         ` Jeff Garzik
2007-02-28  1:36           ` Josh Triplett
2006-12-09 10:17       ` Jeff Garzik
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=457A854F.5010602@freedesktop.org \
    --to=josh@freedesktop.org \
    --cc=Matt_Domsch@dell.com \
    --cc=jeff@garzik.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.