From: "Jörg Krause" <jkrause@posteo.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 6/8] package/mpd: enable support for libnfs
Date: Sat, 18 Oct 2014 01:02:52 +0200 [thread overview]
Message-ID: <5441A01C.8080004@posteo.de> (raw)
In-Reply-To: <544194F5.3090001@mind.be>
On 10/18/2014 12:15 AM, Arnout Vandecappelle wrote:
> On 16/10/14 12:57, J?rg Krause wrote:
>> Dear Thomas Petazzoni,
>>
>> On 10/16/2014 11:44 AM, Thomas Petazzoni wrote:
>>> Dear J?rg Krause,
> [snip]
>>> *) $(STAGING_DIR)/usr/lib/pkgconfig is already the default search path
>>> for our pkg-config, so there should be no need to make this tuning.
>>> Which problem have you seen?
>> Without this mpd configuration check does not find libnfs although it is build
>> successfully.
>>
>> checking for NFS... no
>> configure: error: NFS input plugin: libnfs not found
> Actually, we set PKG_CONFIG_LIBDIR to this directory, and PKG_CONFIG_PATH takes
> precedence over PKG_CONFIG_LIBDIR. I have no idea why we do it that way... But
> it means that if the package sets PKG_CONFIG_PATH to /usr/lib/pkg-config, it
> will override our setting.
You're right! The problem is that in version 1.8.0 of libnfs the
following is set in libnfs.pc.in:
-Requires.private: @LIBNFS_PC_REQ_PRIVATE@
This is fixed by an upstream patch after the release 1.8.0:
https://github.com/sahlberg/libnfs/commit/d47c989d886e5398143d43d3b6d25fdf7210cb11
>> Maybe I should do this?:
>> MPD_MAKE_ENV = PKG_CONFIG_PATH="$(STAGING_DIR)/usr/lib/pkgconfig"
> That looks better, indeed. Except, it should probably be MPD_CONF_ENV.
>
Not necessary anymore, bumping to version 1.9.5 solved this issue:
http://git.buildroot.net/buildroot/commit/?id=28b163f3162c91afaed1e5c5c59d10d18cfa7dbc
Best regards
J?rg Krause
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20141018/e2f9e97a/attachment.html>
next prev parent reply other threads:[~2014-10-17 23:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 13:18 [Buildroot] [PATCH v2 1/8] package/mpd: bump to version 0.19 Jörg Krause
2014-10-15 13:18 ` [Buildroot] [PATCH v2 2/8] package/mpd: sort plugins by type in Config.in Jörg Krause
2014-10-15 13:18 ` [Buildroot] [PATCH v2 3/8] package/mpd: sort plugins alphabetically in mpd.mk Jörg Krause
2014-10-15 13:18 ` [Buildroot] [PATCH v2 4/8] package/mpd: enable support for libsoxr Jörg Krause
2014-10-16 9:33 ` Thomas Petazzoni
2014-10-16 10:29 ` Jörg Krause
2014-10-15 13:18 ` [Buildroot] [PATCH v2 5/8] package/mpd: enable support for libsmbclient Jörg Krause
2014-10-15 13:18 ` [Buildroot] [PATCH v2 6/8] package/mpd: enable support for libnfs Jörg Krause
2014-10-16 9:44 ` Thomas Petazzoni
2014-10-16 10:57 ` Jörg Krause
2014-10-17 22:15 ` Arnout Vandecappelle
2014-10-17 23:02 ` Jörg Krause [this message]
2014-10-15 13:18 ` [Buildroot] [PATCH v2 7/8] package/mpd: enable support for dsd Jörg Krause
2014-10-15 13:18 ` [Buildroot] [PATCH v2 8/8] package/mpd: fix zeroconf support Jörg Krause
2014-10-16 9:50 ` Thomas Petazzoni
2014-10-16 10:57 ` Jörg Krause
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=5441A01C.8080004@posteo.de \
--to=jkrause@posteo.de \
--cc=buildroot@busybox.net \
/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