**** BEGIN LOGGING AT Fri May 23 03:00:01 2014 May 23 06:26:55 halstead: ping May 23 07:32:10 morning all May 23 09:58:41 what's the easiest way to see a list of files generated by a recipe? May 23 09:58:53 i mean, files to go in the actual rootfs May 23 09:59:12 trying to debug a makefile that doesn't seem to put libs where it should put libs May 23 10:00:32 BCMM: all packages built by a recipe doesn't even (necessarily) go into the rootfs..... so I think you want to list all files in a particular package.. May 23 10:00:44 andhe: i think that's what i mean May 23 10:01:00 BCMM: tmp/work/[machine]/[recipe]/[version]/packages-split May 23 10:01:07 rburton: thanks May 23 10:01:09 in there is a directory for each package that was generated May 23 10:01:16 BCMM: rpm -qlp if you use rpm format (default) May 23 10:01:25 yeah, or look at the rpm/deb/ipkgs May 23 10:01:46 yeah my question was phrased wrong; i'm a bit confused about multiple packages from a recipe May 23 10:02:57 libraries get automatically split into libfoo and iibfoo-dev as appropriate May 23 10:03:26 headers and compile-time .so into -dev, the actual library and runtime links into libfoo May 23 10:04:32 soooo... there aren't any. i suspect that might be my problem. thanks. May 23 10:20:42 Hello, I'm can't compile binutils on the daisy branch; here is the log: http://pastebin.com/xJW0ekb5 May 23 10:21:20 Can somebody confirm this or should I open a ticket? May 23 10:36:13 hello May 23 10:42:05 Hi guys, I need help. Is there a way to build libXext, libX11 and libXrender in Yocto without setting DISTRO_FEATURES to x11? I created a new recipe and set those 3 packages in DEPENDS, but I can't build it since my image doesn't use X11. May 23 10:43:51 I found a workaround, but I have to do it by hand: 1) set x11 in conf/local.conf, 2) build recipe including those 3 X11 packages, 3) unset x11 in local.conf, 4) remove those 3 packages in a recipe, 5) bitbake core-image-minimal May 23 10:45:08 that's how I managed to build libxext, libx11 and libxrender via my new recipe and after I manually copied build result of those 3 packages, my new package worked on an embedded arm platform May 23 10:46:03 all suggestions are welcome :) I am ready to test it immediately :) May 23 10:48:15 Ivan___: if you want to actually build X11 then the expectation is that you set it in DISTRO_FEATURES, that's pretty much all there is to it May 23 10:49:03 bluelightning: no, I don't need X11, I just need those 3 packages... May 23 10:49:37 Ivan___: why though? what use would any of those libraries be without X? May 23 10:51:58 bluelightning: my package depens on QT4...even though I am using "eglfs" backend with QT4, those dependencies (libXext, libX11, libXrender) are still needed May 23 10:52:04 bluelightning: my package depends on QT4...even though I am using "eglfs" backend with QT4, those dependencies (libXext, libX11, libXrender) are still needed May 23 10:52:51 sounds like something has been built incorrectly May 23 10:53:25 bluelightning: so, no need for X11 as a backend, but "bad" implementation of QT4 needs it for some reason...that's solved in QT5, but my package unfortunately only works with special branch of qt4 May 23 10:53:29 Ivan___: --no-xcb? May 23 10:55:16 ccaione: not sure, let me check May 23 10:59:16 ccaione: I think that "no-xcb" was introduced with QT5. ./configure --help doesn't provide such option, neither http://qt-project.org/doc/qt-4.8/configure-options.html May 23 10:59:36 Ivan___: ups, right, QT5 only May 23 11:13:58 so, no ideas? May 23 11:24:43 Ivan___: are you building qt4 with the -embedded option ? May 23 11:25:07 bluelightning: yes May 23 11:28:13 then it should not need to link with X11 libraries May 23 11:29:57 perhaps it's your GL library that is linked to them? May 23 11:35:55 I know that's might not be much help, but to be honest this is not a situation we handle; either x11 is on or it isn't May 23 11:36:20 supplying x11 libraries that aren't actually going to be used is just hacking around the problem May 23 11:40:39 as far as I can see here: http://www.linuxfromscratch.org/blfs/view/svn/x/qt4.html, Qt4 depends on Xorg libraries May 23 11:41:02 those are going to be used since Qt4 needs those, so it's not for nothing :) May 23 11:41:57 it would be even better for me to use qt5 which doesn't need xorg libraries, but unfortunately the package I want to use depends on qt4 May 23 11:42:10 it's wkhtmltopdf, a tool which converts html to pdf May 23 11:43:21 I can tell you as the maintainer for our Qt4 recipes that with -embedded specified, Qt itself will not use X11 - that's the entire point of that option May 23 11:45:43 I agree, but I am using this qt4: https://github.com/wkhtmltopdf/qt May 23 11:45:49 branch wk_4.8.5 May 23 11:45:59 and that one needs x11 dependencies May 23 11:47:07 Ivan___: how have you determined that it does? May 23 12:11:57 bluelightning: I now can't be 100% sure if wkhtmltopdf or qt4 (I build wkhtmltopdf against statically built qt4) needs those xorg libraries, but here is described the exact problem I have: https://github.com/wkhtmltopdf/wkhtmltopdf/issues/1515 May 23 12:12:46 anyhow, when I try to run wkhtmltopdf (or check with ldd), I got error that those are missing May 23 12:14:19 well that's nuts May 23 12:14:59 in any case, you should just add x11 to your DISTRO_FEATURES and leave it there; that's effectively what's done on Debian (since that was mentioned in the bug) May 23 12:15:24 that does not actually mean X11 will be in your images, just that it'll be enabled at build time May 23 12:26:37 bluelightning: ok, I understand...I already tried that but I saw a lot of different "X11" packages being built, that's why I thought that can't be good approach May 23 12:44:44 bluelightning: I enabled X11 and started build again, but it has 1500 tasks more than before which confuses me a lot May 23 12:49:07 Ivan___: every recipe built has at least 11 tasks May 23 12:50:07 Ivan___: you should not be so concerned, those tasks do not map to individual packages, more a one-to-many mapping, and as long as no extra code is executed during startup, an the rootfs does not explode (you can check/measure/compare) than why bother at this point May 23 12:51:18 right, what gets built is just what is needed at build time; that often does not immediately correspond with what is required at runtime (i.e. in the image) May 23 12:51:54 ok, thanks :) I will run it over the weekend and see the results on Monday May 23 12:52:04 thank you very much for your support and have a nice weekend May 23 12:52:12 welcome May 23 12:52:24 have a nice weekend too May 23 12:52:41 thx May 23 13:04:05 bluelightning: thanks a lot one more time and talk to you... May 23 13:04:15 Ivan___: np May 23 14:24:15 how do I get all defined target images I can build using bitbake? May 23 15:52:57 hi folks May 23 15:53:04 in http://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-core/systemd/systemd/systemd-pam-fix-fallocate.patch May 23 15:53:42 shouldn't that be i#ifdef HAVE_POSIX_FALLOCATE ; instead of #ifdef HAVE_POSIX_ALLOCATE ? May 23 15:53:58 got the impression the #ifdef never gets evaluated May 23 15:56:45 Tarnyko: hm thought i saw a fix for that actually May 23 15:57:27 rburton: hi and thanks, looking around for the latest patches May 23 15:59:18 http://patchwork.openembedded.org/patch/71163/ May 23 16:01:31 thx ! May 23 16:01:55 Tarnyko: i'm wrong - look at the file you referenced. May 23 16:02:22 Tarnyko: presumably you're using a release without the fix in May 23 16:03:11 rburton : I think so, yes ; we'll be fixing locally for now. Thanks for the great input May 23 16:03:39 Tarnyko: the fix is in git so if you're wanting it backported to a stable branch, just tell oe-core@ May 23 16:04:25 looks like its only on master, so thats a good candidate for daisy May 23 16:04:36 Tarnyko: rburton: If you are looking for it in Daisy, I have it pending already! May 23 16:04:48 sgw_: hooray sgw_ May 23 16:05:51 sgw_ : nice ! Yes, we're using Daisy, so your backport would make some people happy ^^ May 23 16:42:27 Hi! I'm new to Yocto and trying to build a custom image and some dependencies fail to configure because they assume some files are in the current directory while they are in the source (${S}) directory. For example the do_compile task of sqlite_2.8.17 refers to Makefile.linux-gcc. Is this an error in the bb file, or am I doing something wrong? May 23 16:43:01 yes, it's a bug in the recipe. the change to split B/S by default was recent, not all the fallout has been fixed May 23 16:43:16 you can fix it yourself, check the lists for patches in case they haven't been merged, or switch to the release branch (daisy) rather than master May 23 16:45:36 ah, okay. Maybe not the best choice to start with the master branch when using a new project :) I'll look into the patches or switch to daisy May 23 16:45:46 thank you May 23 16:49:37 auke-: yeah, probably best to start with a release branch - daisy is the latest May 23 17:01:31 I want to add ssl support to lighttpd (in meta layer). In the recipe, in EXTRA_OECONF there is --without-openssl. How, in a .bbappend can I delete dhe line --without-openssl ? May 23 17:03:36 just use EXTRA_OECONF = "whatever" to overried what is set in the recipe May 23 17:04:18 thank you Crofton May 23 17:04:38 weebet: you can use EXTRA_OECONF_remove to delete fragments. and send a patch to turn that into a PACKAGECONFIG so you can trivially do it in the future May 23 17:06:19 yoru other option.. -append- a '--with-openssl'.. May 23 17:06:27 i recommend against using _remove in bbappends. a later bbappend from a higher priority layer has no way to undo a _remove May 23 17:06:31 if it's standard GNU configure, the system will use the last --with or --without as the override May 23 17:06:34 a later _append won't counteract an earlier _remove May 23 17:06:46 correct.. May 23 17:14:55 * Crofton|work didn't know about remove May 23 17:15:51 we should probably add a PACKAGECONFIG to the lighttpd recipe to make it easier to enable openssl May 23 17:17:17 the --enable-heartbleed option? May 23 17:17:49 :) May 23 17:18:14 signed-off-by: spook@nsa.gov May 23 17:19:58 well, we patched that issue... probably not the umpteen other ones that exist though ;) May 23 17:25:49 hmm, my patch isn't in patchwork May 23 17:26:17 do I need to put [OE-core] in the subject? May 23 17:27:59 nope, thats automatically done May 23 17:28:19 note that if you use gmail, the version of your patch with that in it will never end up back in your email, as gmail does duplicate detection and removal by message id (iirc) May 23 17:28:34 i usually check gmane to see if my mails really hit the list, if i need to check that May 23 17:29:55 Does https://bugzilla.yoctoproject.org/show_bug.cgi?id=6372 seem reasonably sane? May 23 17:29:55 Bug 6372: enhancement, Undecided, ---, saul.wold, NEW , Feature request: recipe hook for source tree preparation May 23 17:30:04 heh, i always forget about yocti May 23 17:34:21 found it May 23 17:58:04 sgw_: your [Daisy - Initial Pull 000/111] Please Review email says sgw/daisy, but then there is URL to sgw/stage May 23 17:58:25 JaMa: fixed it, checkout v2 May 23 17:59:15 http://cgit.openembedded.org/openembedded-core-contrib/log/?h=sgw/daisy doesn't seem to match with the e-mail cover-letter May 23 18:00:26 JaMa: are you looking at the v2? May 23 18:00:30 sgw_: looks better, please drop packages.bbclass change from me (this one isn't in master) May 23 18:01:38 sure thing, done May 23 18:02:42 thanks, I was confused about lttng changes, but now I see that you have backported both (khem's and then mine on top) so it's fine too May 23 18:03:32 sgw_: btw: are you using usually pull-request URLs or do you fetch patches from e-mail (patchwork)? May 23 18:06:18 jama, depends on the size of the patch set honestly, mostly email, for backporting mostly match up and cherry-pick May 23 18:06:52 ok, thanks May 23 18:11:46 hmm, looks like do_package_write_rpm is missing vardeps on the gen_packagevar bits. iterates over the packages and accesses vars without bitbake's knowledge. of course, changes to those should change do_package, which will ripple out to that, so i guess it doesn't matter that bitbake's knowledge of it is incomplete May 23 21:03:48 Anyone happen to know offhand which firmware binaries from linux-firmware are needed for minnow? May 23 21:13:13 kergoth: meta-minnow is not much help, it just installs the entire linux-firmware May 23 21:16:20 yeah, saw that, wasn't sure why / what was needed. will have to check git history and see if that's at all useful **** ENDING LOGGING AT Sat May 24 02:59:58 2014