linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
To: Robert Schwebel <r.schwebel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: Karel Zak <kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	util-linux-ng-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] fix blkid.h include
Date: Wed, 6 May 2009 08:06:15 -0400	[thread overview]
Message-ID: <200905060806.16600.vapier@gentoo.org> (raw)
In-Reply-To: <20090506113550.GQ15802-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>

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

On Wednesday 06 May 2009 07:35:50 Robert Schwebel wrote:
> The reason is that blkid.h comes from e2fsutils, which install the header
> file into /usr/include/blkid/blkid.h; /usr/include is also what the .pc
> file specifies for the include path for the CFLAGS. So IMHO the patch below
> must be applied to make it work.

sounds like the .pc file is broken and you need to report this to your 
distributor.  works fine on Gentoo:
$ pkg-config blkid --cflags
-I/usr/include/blkid -I/usr/include/uuid
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2009-05-06 12:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-05 21:42 [ANNOUNCE] util-linux-ng v2.15 (stable) Karel Zak
     [not found] ` <20090505214214.GC4460-sHeGUpI7y9L/9pzu0YdTqQ@public.gmane.org>
2009-05-06 11:35   ` [PATCH] fix blkid.h include Robert Schwebel
2009-05-06 11:43     ` Peter Breitenlohner
     [not found]     ` <20090506113550.GQ15802-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-05-06 12:06       ` Mike Frysinger [this message]
2009-05-06 12:13     ` Matthias König
2009-05-11 14:43   ` [ANNOUNCE] util-linux-ng v2.15 (stable) Américo Wang

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=200905060806.16600.vapier@gentoo.org \
    --to=vapier-abrp7r+bbdudnm+yrofe0a@public.gmane.org \
    --cc=kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=r.schwebel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
    --cc=util-linux-ng-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).