From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: [PATCH] farsight: fix implicit pkgconfig dependency causing configure fail
Date: Mon, 20 Feb 2017 13:24:52 -0500 [thread overview]
Message-ID: <1487615092-14989-1-git-send-email-paul.gortmaker@windriver.com> (raw)
In-Reply-To: <CA+chaQdDMYNGa7KC2-Rgoz-+DXh0v7cfUZRx5W1FcP4rcSdbFQ@mail.gmail.com>
In the config log we see:
configure:12277: checking whether to build static libraries
configure:12281: result: yes
configure:12419: checking for x86_64-overc-linux-pkg-config
configure:12452: result: no
configure:12462: checking for pkg-config
configure:12495: result: no
configure:12801: Using Farsight2 source release as package name
configure:12825: Using Unknown package origin as package origin
configure:12879: Using /usr/libexec/gst-install-plugins-helper as plugin install helper
configure:12953: checking for NICE
configure:13022: error: Need libnice >= 0.0.9
While it libnice that fails configure, it is the absence of pkg-config
several lines above that causes the failure, as libnice is in the sysroot.
For most build hosts, you'll have to remove the default binary that
lives in /usr/bin/pkg-config in order to see this failure.
Cc: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
diff --git a/meta-oe/recipes-support/farsight/farsight2_0.0.22.bb b/meta-oe/recipes-support/farsight/farsight2_0.0.22.bb
index 2989850e9875..7d88b5405e16 100644
--- a/meta-oe/recipes-support/farsight/farsight2_0.0.22.bb
+++ b/meta-oe/recipes-support/farsight/farsight2_0.0.22.bb
@@ -9,7 +9,7 @@ PR = "r3"
DEPENDS = "libnice glib-2.0 libxml2 zlib dbus gstreamer gst-plugins-base"
-inherit autotools
+inherit autotools pkgconfig
PACKAGECONFIG ??= ""
PACKAGECONFIG[gupnp] = "--enable-gupnp,--disable-gupnp,gupnp-igd"
--
2.7.4
prev parent reply other threads:[~2017-02-20 18:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 18:03 [PATCH 0/3] fix gstreamer and its assoc. fallout Paul Gortmaker
2017-02-15 18:03 ` [PATCH 1/3] gstreamer: fix dependency issue and un-blacklist it Paul Gortmaker
2017-02-15 18:03 ` [PATCH 2/3] remove blacklist entries against blacklisted gstreamer Paul Gortmaker
2017-02-19 19:59 ` Martin Jansa
2017-02-20 19:16 ` [PATCH] florence: add explicit dependency on gconf-native to fix install error Paul Gortmaker
2017-02-20 19:17 ` [PATCH] gthumb: fix implict dependency on gconf causing configure fail Paul Gortmaker
2017-02-15 18:03 ` [PATCH 3/3] farsight/xfce4-mixer: unblacklist recipes Paul Gortmaker
2017-02-19 19:58 ` Martin Jansa
2017-02-20 18:24 ` Paul Gortmaker [this message]
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=1487615092-14989-1-git-send-email-paul.gortmaker@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.