Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <jkrause@posteo.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 6/8] package/mpd: enable support for libnfs
Date: Thu, 16 Oct 2014 12:57:16 +0200	[thread overview]
Message-ID: <543FA48C.8040601@posteo.de> (raw)
In-Reply-To: <20141016114439.6e09d052@free-electrons.com>

Dear Thomas Petazzoni,

On 10/16/2014 11:44 AM, Thomas Petazzoni wrote:
> Dear J?rg Krause,
>
> On Wed, 15 Oct 2014 15:18:52 +0200, J?rg Krause wrote:
>
>> +ifeq ($(BR2_PACKAGE_MPD_LIBNFS),y)
>> +PKG_CONFIG_PATH = "$(STAGING_DIR)/usr/lib/pkgconfig"
> This looks wrong, for two reasons:
>
>   *) A package is not allowed to change global variables. Remember that
>      the namespace of variables in global, so if one package is changing
>      a global variable, this change is visible to all other packages.

I have seens this at wpa_supplicant which use it if package dbus is 
selected:

    ifeq ($(BR2_PACKAGE_DBUS),y)
         WPA_SUPPLICANT_DEPENDENCIES += host-pkgconf dbus
         WPA_SUPPLICANT_MAKE_ENV = \
             PKG_CONFIG_SYSROOT_DIR="$(STAGING_DIR)"    \
             PKG_CONFIG_PATH="$(STAGING_DIR)/usr/lib/pkgconfig"

I copied the last line here. Okay, I see now the difference: 
wpa_supplicant sets it locally to the make environment and I set it 
globally.

>   *) $(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

Maybe I should do this?:
     MPD_MAKE_ENV = PKG_CONFIG_PATH="$(STAGING_DIR)/usr/lib/pkgconfig"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20141016/81225d83/attachment.html>

  reply	other threads:[~2014-10-16 10:57 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 [this message]
2014-10-17 22:15       ` Arnout Vandecappelle
2014-10-17 23:02         ` Jörg Krause
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=543FA48C.8040601@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