linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Triplett <josh@freedesktop.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Matt Domsch <Matt_Domsch@dell.com>, linux-sparse@vger.kernel.org
Subject: Re: sparse as a compiler front-end
Date: Tue, 27 Feb 2007 17:36:14 -0800	[thread overview]
Message-ID: <45E4DC8E.9000702@freedesktop.org> (raw)
In-Reply-To: <457A8CD4.8020008@garzik.org>

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

Jeff Garzik wrote:
> Josh Triplett wrote:
>> 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?
> 
> The pkgconfig file describes an architecture-specific library, so it 
> goes into /usr/lib/pkgconfig/$pkg.pc if its 32-bit (or the rare 64-bit 
> arch that uses /usr/lib), and it goes into /usr/lib64/pkgconfig/$pkg.pc 
> if the library is 64-bit.
> 
> /usr/share is not appropriate for architecture-specific data.

Latest sparse from Git now installs sparse.pc to $(LIBDIR)/pkgconfig (default
/usr/lib/pkgconfig).

Thanks,
Josh Triplett


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

  reply	other threads:[~2007-02-28  1:36 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 [this message]
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=45E4DC8E.9000702@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 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).