Paul Gortmaker 0d77dcf5c8 farsight: fix implicit pkgconfig dependency causing configure fail
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>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2017-02-22 13:16:54 +01:00
..
2016-05-10 20:18:57 +02:00
…
…

This layer depends on:

URI: git://github.com/openembedded/oe-core.git
branch: master
revision: HEAD

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'

When sending single patches, please use something like:
'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-oe][PATCH'

You are encouraged to fork the mirror on github https://github.com/openembedded/meta-oe/ to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like gitorious, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI.

Main layer maintainer: Koen Kooi <koen@dominion.thruhere.net>
                       Martin Jansa <martin.jansa@gmail.com>