**** BEGIN LOGGING AT Tue Apr 21 02:59:58 2015 Apr 21 08:18:59 morning all Apr 21 09:24:28 morning bluelightning Apr 21 09:24:37 hi diego_r Apr 21 10:56:47 is there a simple way to turn make VERBOSE=1 on for some software built by Yocto, e.g. the kernel, or would I need to create a do_compile function for achieving this? Apr 21 10:57:32 lpapp: wouldn't you just pass that via EXTRA_OEMAKE ? Apr 21 10:58:34 faor enough, thanks. Apr 21 10:58:37 fair* Apr 21 11:31:18 bluelightning: something went really wrong... https://paste.kde.org/p9i3d7mgc Can no longer clean. Apr 21 11:32:33 and I have not changed anything as far as I am aware. Git diff does not show any output either. Apr 21 11:44:48 bluelightning: and I am getting that now for any package that I am just trying. Apr 21 12:25:00 lpapp: something must have changed... Apr 21 12:27:11 yeah, but how can I fix this and what exactly is it about? Apr 21 12:40:18 erm, that suck : http://mirror.stshosting.co.uk/mariadb/mariadb-5.5.39/ Apr 21 12:40:25 404 not found :| Apr 21 12:43:14 lpapp: not sure, haven't seen an error like this before Apr 21 12:43:44 I can see that something is going very wrong with event handling Apr 21 13:53:13 bluelightning: ok, btw, what is the reason why I cannot find config.gz under the ./tmp/work hierarchy? I thought it was supposed to be part of the generated filesystem? I would like to double check whether my kernel configuration got in with bitbake -c menuconfig virtual/kernel. Apr 21 13:53:35 /home/stefan/yocto/poky/build/tmp/work/armv6-vfp-poky-linux-gnueabi/domoticz/2365-r0/trunk Apr 21 13:53:40 how can i make a directory use right folder for compile, in my case /yocto/poky/build/tmp/work/armv6-vfp-poky-linux-gnueabi/domoticz/2365-r0/domoticz-2365 is used while source is located in Apr 21 13:58:36 lpapp: IIRC config.gz generation is a kernel config option, I assume you don't have that turned on Apr 21 13:59:06 lpapp: but if you want to look at the final .config you can see that in the build directory for the kernel recipe Apr 21 13:59:41 bitbake -e virtual/kernel | grep ^B= will show that Apr 21 14:00:49 mrsan_: set S = "${WORKDIR}/trunk" in the recipe Apr 21 14:01:14 bluelightning: as its own row? Apr 21 14:01:22 mrsan_: yes Apr 21 14:01:27 bluelightning: thx:) Apr 21 14:04:25 bluelightning: yes, IKCONFIG_PROC, but it is enabled Apr 21 14:04:30 yet, I cannot find config.gz Apr 21 14:04:40 perhaps it is automatically created on boot as it is in /proc? Apr 21 14:04:52 oh, right.. yes that's only in /proc at runtime Apr 21 14:04:57 and so it should not be part of the Yocto directory hierarchy? Apr 21 14:05:01 so I wouldn't expect a config.gz no Apr 21 14:05:06 the thing is that my kernel still does not boot Apr 21 14:05:10 but .config, you will find that Apr 21 14:05:13 I tried to enable some debug options, but I am not getting more Apr 21 14:05:29 and I would like to validate somehow that my flashed image comes with those enabled options. Apr 21 14:06:59 1 more question. can i from my bb file set EXTRACONFIG for boost package,so it includes PACKAGECONFIG_pn-boost = "python" Apr 21 14:08:02 mrsan_: you cannot set a variable in one recipe from another if that's what you are asking, no Apr 21 14:08:16 mrsan_: you'll need to set that at the configuration level, i.e. local.conf or a custom distro config Apr 21 14:08:42 bluelightning: thx Apr 21 14:10:00 bluelightning: hmm, thanks. Apr 21 14:12:38 bluelightning: what am I supposed to run after bitbake -c menuconfig virtual/kernel? Apr 21 14:12:44 is it ok to run bitbake linux-foo? Apr 21 14:12:47 yes Apr 21 14:12:51 strange Apr 21 14:17:28 bluelightning: hmm, probably I should remove rm_work Apr 21 14:17:37 to see that it actually remained the same after bitbake linux-foo? Apr 21 14:18:22 yes, or set RM_WORK_EXCLUDE to exclude that recipe Apr 21 14:22:04 bluelightning: doesnt HOB read the local.con? Apr 21 14:22:09 or is this line wrong? Apr 21 14:22:11 PACKAGECONFIG_pn-boost = "python" Apr 21 14:22:19 *conf Apr 21 14:24:56 mrsan_: it should be reading it yes Apr 21 14:25:37 mrsan_: is "python" the only value you want in there, or do you want to add python to the default value? because at the moment that line would be setting it, not adding to it Apr 21 14:26:32 i want to add it Apr 21 14:26:35 but it still doesnt get set Apr 21 14:26:41 i know it should be += Apr 21 14:28:30 mrsan_: To append it, you need to use PACKAGECONFIG_append_pn-boos. The += only appends a space before the string. Apr 21 14:29:06 DatGizmo: Doh. thx Apr 21 14:29:23 mrsan_: np Apr 21 14:56:17 YPTM: Ready-Access Number: 8007302996 Access Code: 2705751 Apr 21 14:56:24 YPTM: Stephen Joined Apr 21 14:58:17 YPTM: Sona joined, hi Apr 21 15:00:32 YPTM: Paul Eggleton joined Apr 21 15:02:24 YPTM: Michael here. Apr 21 15:07:41 YPTM: cristian joined Apr 21 15:08:02 YPTM: We decided in the OEDAM meeting to create a CVE list to have track of CVE addressed in different branches, I said I could do this ,I have just started, I am still working on it. please have a look at this and let me know what you think. https://docs.google.com/spreadsheets/d/13o4IPsCQ42aR2CCGzYOHdmpIEHkHUwDWlF4QqgI6emQ/edit#gid=0 Apr 21 15:15:27 YPTM is done. Apr 21 16:39:26 hey there Apr 21 16:40:19 got any idea why pulling meta-oe into a poky yocto build gets me this: "ERROR: ParseError at /home/panto/winstron/poky/layers/meta-oe/recipes-core/packagegroups/packagegroup-basic.bb:12: Could not inherit file classes/bluetooth.bbclass" Apr 21 16:41:37 you're mixing incompatible branches Apr 21 16:42:44 ok, how to figure out which branches are compatible and what not? Apr 21 16:48:29 the ones that are exactly the same. Apr 21 16:48:34 master with master, daisy with daisy, etc Apr 21 16:50:32 ok, let me rephrase that Apr 21 16:50:50 how do I use recipes from meta-oe in my poky build? Apr 21 16:51:06 panto: what version of poky are you building with? Apr 21 16:51:25 dizzy Apr 21 16:51:36 ok, then you want the dizzy branch of meta-oe to match up with that Apr 21 16:51:50 hmm, ok, let me try that Apr 21 16:52:54 that did the trick Apr 21 16:52:58 thanks Apr 21 16:53:14 see, it's the easy stuff that throw you off Apr 21 16:54:10 it's a common mistake and one I can certainly understand Apr 21 16:54:37 FWIW, as of the upcoming release we do have a mechanism that should be able to be used to produce a more obvious error when you're in that situation Apr 21 16:54:50 I would throw a big fat warning at layers.openembedded.org Apr 21 16:55:36 hmm, that might be a good idea yes Apr 21 16:55:55 or even a warning in the parse step about mismatching branches Apr 21 16:56:07 dunno, it could help another poor slob that runs into it Apr 21 16:56:16 the latter is what the mechanism I'm alluding to should enable Apr 21 16:59:04 the problem is detecting missmathed branches Apr 21 16:59:11 *mismatched Apr 21 18:06:58 has anything changed in daisy with regards to the ubifs creation? Apr 21 18:37:39 if I remove a package from an image's packagegroup, should bitbake myimage recreate the reduced the image? Apr 21 18:37:44 or I need to do a bit more cleanup? Apr 21 18:42:21 should rebuild the packagegruop and then rebuild the image Apr 21 18:42:29 it will, that is, you shoudlnt have to do anything else Apr 21 18:47:47 thanks **** ENDING LOGGING AT Wed Apr 22 02:59:58 2015