From: Damien Le Moal <dlemoal@kernel.org>
To: Daniel Wagner <dwagner@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>, linux-nvme@lists.infradead.org
Subject: Re: WTF is going on with the nvme-cli build
Date: Mon, 17 Apr 2023 18:02:24 +0900 [thread overview]
Message-ID: <c70e194b-ed19-7d0e-5976-477cfa74a716@kernel.org> (raw)
In-Reply-To: <sqrbip3dafgf4cnmmdziect6vem2msocsxqcqmnvyrlkartomj@ilwk43vyl53s>
On 4/17/23 17:44, Daniel Wagner wrote:
> On Thu, Apr 13, 2023 at 07:49:42PM +0900, Damien Le Moal wrote:
> All the time... And I do have the json development headers installed:
>>
>> /usr/include/json-c/json.h
>>
>> But the compile command does not add -I/usr/include/json-c: it uses the broken
>> default /usr/local/include/json-c. No normal distro install anything in
>> /usr/local...
>>
>> And that is despite the fact that meson setup says:
>>
>> Run-time dependency json-c found: YES 0.15
>>
>> Something is not right.
>
> meson uses pkg-config (and cmake) to find all the dependency. I suspect the
> PKG_CONFIG_PATH contains /usr/local/lib/pkgconfig. Can you check the
> pkg-config configuration?
Yeah. The problem is there. pkgconf gives the correct path:
$ pkgconf --cflags json-c
-I/usr/include/json-c
But pkg-config is broken:
$ pkg-config --cflags json-c
-I/usr/local/include/json-c
Not sure why as in Fedora, pkg-config is a shim layer on top of pkgconf provided
by pkgconf-pkg-config package. But I cannot uninstall pkgconf-pkg-config as it
is used by gnome-shell.
Looks like something is broken in Fedora Not sure what as
/usr/lib64/pkgconfig/json-c.pc is perfectly fine, pointing at /usr/include/json-c.
But I would still say that it is probably time to update to pkgconf :)
next prev parent reply other threads:[~2023-04-17 9:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 6:52 WTF is going on with the nvme-cli build Christoph Hellwig
2023-04-13 7:07 ` Daniel Wagner
2023-04-13 7:25 ` Christoph Hellwig
2023-04-17 8:40 ` Daniel Wagner
2023-04-13 10:49 ` Damien Le Moal
2023-04-17 8:44 ` Daniel Wagner
2023-04-17 9:02 ` Damien Le Moal [this message]
2023-04-17 9:14 ` Daniel Wagner
2023-04-17 11:06 ` Damien Le Moal
2023-04-17 14:32 ` Daniel Wagner
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=c70e194b-ed19-7d0e-5976-477cfa74a716@kernel.org \
--to=dlemoal@kernel.org \
--cc=dwagner@suse.de \
--cc=hch@infradead.org \
--cc=linux-nvme@lists.infradead.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