**** BEGIN LOGGING AT Mon Dec 23 02:59:59 2013 Dec 23 05:43:47 Hi Dec 23 05:44:20 I'm getting this warning Dec 23 05:44:36 WARNING:: The compile log indicates that host include and/or library paths were used. Dec 23 05:45:00 where do I have change to remove the warning? Dec 23 05:47:44 i checked it is coming from logging.bbclass Dec 23 05:48:34 I want to use the libraries, just want to disable the warning Dec 23 08:57:33 I'm getting this warning Dec 23 08:57:45 WARNING:: The compile log indicates that host include and/or library paths were used. Dec 23 08:57:53 I want to use the libraries, just want to disable the warning Dec 23 12:23:35 Hi all, I have a situation here, where one plugin is enabled in PACKAGECONFIG="abc" but i want to disbale abc in bbappend. how can i do it? Dec 23 12:25:17 where abc is defined like PACKAGECONFIG[abc] = "--enable-abc,--disable-abc,libabc" in bb Dec 23 12:26:13 any one knows how to disable in "abc" in bbappend? Dec 23 12:27:53 PACKAGECONFIG="" Dec 23 12:28:21 or PACKAGECONFIG_remove="abc" if you're using master and don't want to forcibly unset PACKAGECONFIG, but just remove abc Dec 23 12:28:59 (and if the recipe does use PACKAGECONFIG= then send a patch, they PACKAGECONFIG default should always use ??= Dec 23 12:30:24 rburton, I ll try it...what is the significance of "??=" Dec 23 12:32:25 sukesh: default value Dec 23 12:32:32 that is easily overridden Dec 23 12:33:46 PACKAGECONFIG has other modules also... so i have to use PACKAGECONFIG_remove ??="abc" am i right? Dec 23 12:36:44 yes, or reset it to what you want Dec 23 12:36:56 ie PACKAGECONFIG="foo bar", if the default is "foo abc bar" Dec 23 12:44:35 hey rburton, PACKAGECONFIG_remove ??="abc" is not working .. it is including abc.. Dec 23 12:44:43 = Dec 23 12:44:58 only the default value of packageconfig should be ??= Dec 23 12:45:21 PACKAGECONFIG_remove ="abc" als i tried Dec 23 12:46:01 yes PACKAGECONFIG defined has "??=" Dec 23 12:46:37 are you using bitbake master? Dec 23 12:46:44 as i said, you need that for _remove to work Dec 23 12:47:34 what is bitbake master?? I dont it is that or not :(.. how can i check it? Dec 23 12:48:41 if you don't know, you probably are not. :) if you're fetching the bitbake repo directly, or using poky master, then you have _remove. Dec 23 12:48:48 otherwise you probably don't. Dec 23 12:49:54 One more thing i tried is overriding entire PACKAGECONFIG ??="*" in bbappend by removing abc in that.. this is working.. but i dont knw this is right way to use or not? Dec 23 12:50:05 Is there any other way? Dec 23 12:50:07 that's fine Dec 23 12:50:09 use = Dec 23 12:50:22 you can do it in a bbappend, or in your local.conf, or in a distro configuration Dec 23 12:50:30 all are fine. Dec 23 15:22:58 hello! Dec 23 15:23:21 can someone help me bypass a problem with a recipe? Dec 23 15:23:46 here are the details: https://github.com/chrippa/python-librtmp/issues/3 (and recipes) Dec 23 16:37:58 Should i open a bug (request) for the above using https://bugzilla.yoctoproject.org/ or use the mailling list Dec 23 16:38:03 thanks.. Dec 23 16:41:13 well, it's not really a bug in the build system Dec 23 16:42:03 you should check the path setup.py (assuming it is setup.py) is using to find cffi, it's probably looking on the host system Dec 23 16:42:08 athoik: ^ Dec 23 16:45:10 thanks bluelightning Dec 23 16:45:31 try: from librtmp_ffi.verifier import verifier extension = verifier.get_extension() except ImportError: Dec 23 16:45:57 import sys sys.stderr.write("Error: CFFI (required for setup) is not available.\n") sys.stderr.write("Please use 'pip install cffi', or equivalent.\n") sys.exit(1) Dec 23 16:46:25 maybe the cffi recipe hasn't put files in the appropriate place then? Dec 23 16:46:57 here is the setup.py https://github.com/chrippa/python-librtmp/blob/master/setup.py Dec 23 16:48:20 athoik: hmm, that check looks a little loose to me... if there was some other ImportError in that code it would still complain about cffi not being installed Dec 23 16:49:21 How it should be written, in order to inform author to correct setup.py Dec 23 17:03:49 athoik: I don't know for sure that that is the problem, but it looks suspect Dec 23 17:06:10 bluelightning: i think that it tries to find cffi on python-native, but it should search on the host Dec 23 17:06:32 for the host we are targeting Dec 23 17:07:39 athoik: right, actually you might need to patch that check out of the file Dec 23 17:13:53 bluelightning: i used devshell and now the message is different.. Dec 23 17:14:12 cc1: warning: include location "/usr/include/python2.7" is unsafe for cross-compilation [-Wpoison-system-directories] Dec 23 17:14:21 In file included from /usr/include/python2.7/Python.h:58:0, Dec 23 17:14:28 from librtmp_ffi/__pycache__/_binding.c:2: Dec 23 17:14:48 #/usr/include/python2.7/pyport.h:849:2: error: #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)." Dec 23 17:14:52 #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)." Dec 23 17:14:56 error: command 'mipsel-oe-linux-gcc' failed with exit status 1 Dec 23 17:48:38 thanks for the help, i will try to build module under mipsel debian, maybe i will succeed like that. Dec 23 20:45:59 The linux kernel src isn't included when I do "populate_sdk" for my image, so I can't create kerne modules with the SDK. Am I missing something here ? Dec 23 21:43:01 Adding "kernel-dev" to the image helps, but when compiling a module with the SDK I get an error, "/bin/sh: scripts/basic/fixdep: No such file or directory" Dec 23 21:43:27 And yes, I dont have fixdep for running on the host there, just the .c and Makefile Dec 23 23:25:26 running "make scripts" in the kernel src dir built the necessary deps, would be nice if the sdk would be built shipped with that **** ENDING LOGGING AT Tue Dec 24 03:00:00 2013