**** BEGIN LOGGING AT Sat Jan 24 02:59:59 2015 Jan 24 03:27:24 Hmm... bitbake likes hanging at 99% parsing recipies. Is there any way to determine what it's stalled processing? Jan 24 03:27:50 I presume it's some network access that's not timing out as it should Jan 24 09:35:01 I just did an incremental build using master branches, and noticed a couple of changes in buildhistory that stand out: Jan 24 09:35:29 /sbin/halt.sysvinit group changed from "shutdown" to "root" Jan 24 09:35:59 /sbin/shutdown.sysvinit group changed from "shutdown" to "root" Jan 24 09:37:10 I didn't notice any recent changes in busybox recipes Jan 24 09:37:27 seebs, could it be a pseudo thing ? Jan 24 11:46:22 I don't *think* so, but maybe? I know we found some leakage in ... i think it was libgcc and/or glibc, recently. Jan 24 11:46:24 Are they symlinks? Jan 24 12:48:09 seebs, -rwsr-xr-- root root 11072 ./sbin/halt.sysvinit Jan 24 12:48:49 seebs, so not symlinks Jan 24 12:50:10 bah, I also notice a "-rw-r--r-- 1000 1000 0 ./var/lib/opkg/lists/oe" line in there Jan 24 12:50:38 which I guess should be using root,root Jan 24 12:50:56 thats the only one of that kind though Jan 24 13:00:19 seebs, if it makes any difference, there _are_ symlinks halt -> halt.sysvinit and shutdown -> shutdown.sysvinit, both of which are "lrwxrwxrwx root root" Jan 24 13:30:35 kergoth: around? Jan 24 13:31:07 kergoth: got a really odd bug with COW and I don't understand it at all :( Jan 24 18:46:54 So, I make a small change to BlueZ and then it triggers a rebuild of qt4-x11-free. Jan 24 18:47:33 Is there any way to (temporarily) say to bitbake: "Don't rebuild Qt, again. I ain't go time for it." Jan 24 19:25:05 seebs, halt and shutdown have one thing common in that they have the suid bit set Jan 24 19:25:31 seebs, I've tried bitbake -c clean -c cleansstate for sysvinit, busybox, base-passwd Jan 24 19:26:36 rebuilding things, but now, halt and shutdown will never get to be "root.shutdown", although I clearly see in sysvinit_2.88dsf.bb's do_install() that they should be root.shutdown Jan 24 19:31:28 log.do_install doesnt show any warnings of interest :-/ Jan 24 19:45:24 gabrbedd, I think you can "lock" certain hashes, but I'm not sure where it is documented Jan 24 19:49:04 kroon: thanks! Jan 25 00:13:07 bluelightning: hi, i am trying to migrate from dylan to dizzy-12.0.1 to be able to use runtime testing framework Jan 25 00:14:02 bluelightning: there's quite a few differences i am noticing. but first of all zlib has started to give me grief :( Jan 25 00:15:17 bluelightning: ERROR: The recipe zlib is trying to install files into a shared area when those files already exist. Jan 25 00:16:39 bluelightning: the fucntion that fails is do_populate_sysroot Jan 25 00:17:47 bluelightning: any ideas? Jan 25 00:37:45 darkhorse: did you keep the same TMPDIR? if so, you should delete it or move it out of the way Jan 25 00:42:12 bluelightning: i have a new TMPDIR however i am using the same SSTATE_CACHE Jan 25 00:43:39 bluelightning: so SSTATE_DIR is the same. do you think it matters? Jan 25 00:47:01 darkhorse: should not matter Jan 25 01:13:52 bluelightning: in dizzy, default TCLIBC is glibc. can I still use eglibc? Jan 25 01:14:37 darkhorse: not really, no... eglibc as a project merged back into glibc, so it doesn't really exist anymore Jan 25 01:14:58 functionality should be completely equivalent Jan 25 01:35:04 bluelightning: there used to external_sourcery_toolchain.bb in dylan. what happend to it in dizzy? Jan 25 01:35:48 darkhorse: meta-sourcery provides that now Jan 25 01:44:21 bluelightning:meta-sourcery is not included in dizzy and it wasn't included in dylan either. so is this the correct place to get it: https://github.com/MentorEmbedded/meta-sourcery Jan 25 01:44:37 darkhorse: yes Jan 25 01:44:44 bluelightning: secondly, does it support using prebuilt sourcery toolchain? Jan 25 01:44:57 darkhorse: that is what it is intended for yes Jan 25 01:45:54 bluelightning: okay. I will try it. Last time I could get it to work for me with dylan... Jan 25 01:46:10 bluelightning: i meant "could not" Jan 25 01:46:44 I can't say I've ever used it personally Jan 25 02:17:48 bluelightning: thisi s the error I get each time I try to use meta-sourcery:: Could not include required file conf/distro/include/tclibc-external-sourcery-toolchain.inc Jan 25 02:23:54 darkhorse: are you setting TCLIBC to something? Jan 25 02:25:35 bluelightning: it is being set to glibc in the defaultsetup.conf Jan 25 02:42:10 bluelightning: oops! my bad - there was an assignment happening to TCLIBC - Thanks for pointing that out. looks like I have moved forward one inch Jan 25 02:58:10 kergoth: can you help me with using meta-sourcery please? **** ENDING LOGGING AT Sun Jan 25 02:59:59 2015