**** BEGIN LOGGING AT Wed Aug 06 02:59:59 2014 Aug 06 06:09:29 JBD1986: do you include xterm in your image by any chance ? Aug 06 06:11:22 JBD1986: and do you enable CONFIG_RESIZE for busybox ? Aug 06 06:12:22 if these conditions are true then this issue can happen since xterm also provides resize binary and busybox will do the same if CONFIG_RESIZE is selected Aug 06 06:13:01 default it to disable CONFIG_RESIZE in oe-core, so I would think if you dont need resize binary then disable it to match oe-core config and you should be good Aug 06 07:13:44 howdy! is there maybe some cli-equivalent to bitbake -g -u depexp? Aug 06 07:21:31 hi Aug 06 07:21:44 there are other ui Aug 06 07:22:26 afaik you cab use -u with depexp,goggle,knotty,ncurses and maybe some more. check lib/bb Aug 06 07:23:06 http://cgit.openembedded.org/bitbake/tree/lib/bb/ui Aug 06 07:24:00 thanks Aug 06 12:39:41 khem, thanks for the tip! I'm going to try that Aug 06 13:38:17 khem, that indeed solved my issue! Thanks! Aug 06 14:21:31 Hi. Is it possible to limite the number of fetcher threads? My problem is that, when some of the variables are expanded at recipe parsing, the triggered “git ls-remote” calls exceeds the allowed number of ssh server connections. Aug 06 14:27:46 zoli_: why are you using many ls-remote calls? AUTOREV or using tags in SRC_URI? Aug 06 14:29:56 JaMa: expand SRCPV using bb.fetch2.get_srcrev Aug 06 15:55:09 LetoThe2nd: drop -u depexp and examine the emitted .dot files with a text editor or grep, that's about your only option other than depexp Aug 06 15:57:19 kergoth: ah ok, thanks for the head up Aug 06 15:57:36 as ant says, there are other uis, but none for exploring dependencies Aug 06 16:19:12 moin Aug 06 17:08:18 bluelightning: ping, mariadb is failing here (when building after world, not with minimal deps): Aug 06 17:08:21 mariadb/5.5.38-r0/build' Aug 06 17:08:23 | make -f dbug/CMakeFiles/t.dir/build.make dbug/CMakeFiles/t.dir/build Aug 06 17:08:26 | ./factorial: 1: ./factorial: Syntax error: word unexpected (expecting ")") Aug 06 17:08:28 | make[2]: *** [dbug/output1.r] Error 2 Aug 06 17:08:33 bluelightning: have you seen something like that before in your builds? Aug 06 17:08:43 I haven't, no Aug 06 17:08:58 I wonder what triggers it... Aug 06 17:09:45 I would compare log.do_configure to see what's new, but both TMPDIRs are already gone so it will take some time Aug 06 17:10:53 hmm, ok... well I'm happy to hold until we figure out where the issue is Aug 06 17:12:09 hi. i hit a weird situation today in a setup with poky + meta-oe. when building a base x11 image the image generation would fail with package_deb, but would work with package_ipk. the failt was a package conlict that happens to be a real conflict. so it was actually rigth to 'fail to build'. doesn't opkg/ipk hangle package conflicts? Aug 06 17:13:54 btw, the conclict is that by default packagegroup-core-x11-utils depens on x11-common, and pulls in xserver-nodm-init. but since i have meta-oe, it was using meta-oe nodm-init which depends on xserver-common.. Aug 06 17:14:13 needless to say that was a fun debug exercize ;-) Aug 06 17:16:58 opkg definitely does support conflicts; but there are certainly differences in how they handle dependency resolution Aug 06 17:17:19 not sure specifically how there would be a difference in behaviour in that situation though... Aug 06 19:17:19 I have a question regarding packaging Python to use with zipimport. For python-core and the modules we use, we'd like to package the corresponding .pyc/.pyo files in /usr/lib/python2.7 in a zip file to go under /usr/lib/python27.zip, in order to save space on our embedded targets. Where would be the best place to do this? In a packagegroup, with some hooks? As a new recipe, which depends on python-core and the desired modules, grabs everything from the s Aug 06 19:17:26 Or somewhere else? Aug 06 20:32:57 beshelto: i'm not sure i understand what you're trying to do Aug 06 20:33:22 are you going to unzip those files when needed? Aug 06 20:34:12 most images are pretty small anyway, depending on what's in the image... Aug 06 20:34:34 how much space do you have? Aug 06 20:42:12 Python automatically searches for /usr/lib/python27.zip, and if it's there, it can pull zipped modules directly out of the zipfile using zipimport. Aug 06 20:42:31 For our Python install, it saves us 3-5 MB in disk space. Aug 06 20:43:00 We've verified that it works properly when we do the OE build and then tweak the image by hand. Aug 06 20:43:07 given the granular packaging, it sounds non-trivial. if you don't intend to add packages to the rootfs at runtime, you could do it as a part of the image creation process. add a new shell function and run it in the rootfs postprocess hook Aug 06 20:43:52 By "new shell function", can we write an arbitrary shell script and call it from that hook? Aug 06 20:46:03 yes Aug 06 20:47:30 Cool, thanks -- I'll give that a shot. Aug 06 20:48:29 you can write the shell fragment in the image recipe Aug 06 22:09:46 hi woglinde wie gehts Aug 06 22:09:59 woglinde: will you attend ELCE this time its in your homeland Aug 06 22:58:45 khem yes I will Aug 06 23:04:49 thanks, rudi is distracting me... **** ENDING LOGGING AT Thu Aug 07 02:59:58 2014