diff options
| author | Tom Zanussi <tom.zanussi@intel.com> | 2011-01-14 16:33:05 -0600 |
|---|---|---|
| committer | Saul Wold <sgw@linux.intel.com> | 2011-01-14 15:18:10 -0800 |
| commit | d38ad3271829b2d282c973e69edd265ef52174c8 (patch) | |
| tree | 845ec061bf400088ae6e8cbc97bbce480a245779 /meta/recipes-kernel/latencytop/latencytop-0.5 | |
| parent | 9c6b313acb500095fa80a8c57e27a55d3c34797f (diff) | |
| download | openembedded-core-d38ad3271829b2d282c973e69edd265ef52174c8.tar.gz openembedded-core-d38ad3271829b2d282c973e69edd265ef52174c8.tar.bz2 openembedded-core-d38ad3271829b2d282c973e69edd265ef52174c8.tar.xz openembedded-core-d38ad3271829b2d282c973e69edd265ef52174c8.zip | |
linux-yocto: hard-code NO_LIBPERL/NO_LIBPYTHON
ExtUtils::Embed ccopts is getting the host's -I/usr/local/include and
using it to compile perf, which results in a compilation error that
started appearing just recently.
This turns the code that makes use of ExtUtils::Embed off and simply
hard-codes NO_LIBPERL.
It does the same for LIBPYTHON while we're at it, since it probably
suffers from a similar underlying problem and just by chance hasn't
broken anything yet.
This will be re-enabled after I familiarize myself with the perf
recipe and am able to create a proper fix.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Diffstat (limited to 'meta/recipes-kernel/latencytop/latencytop-0.5')
0 files changed, 0 insertions, 0 deletions