**** BEGIN LOGGING AT Thu Jul 16 02:59:59 2015 Jul 16 07:11:09 hey Jul 16 07:12:15 is it a bug or a feature that example image recipes use IMAGE_INSTALL = ... (a hard assignment) instead of eg. +=? Jul 16 07:12:51 it is kind of implied in the documentation that IMAGE_INSTALL may not be the best variable to modify in local.conf Jul 16 07:13:45 but if the image recipes used += instead, the behaviour would seem to me much more expected Jul 16 07:14:18 in other words, world wouldn't fall apart from using IMAGE_INSTALL += in local.conf Jul 16 07:19:59 good morning Jul 16 07:47:38 Hello, Could you confirm my understanding : lighttpd does not provide itself the PHP support, right ? is there one that provide PHP in the folowing list ? http://recipes.yoctoproject.org/rrs/recipes/1.9/M2/ Jul 16 07:53:15 good morning Jul 16 07:56:08 vincenet: I usually use lighttpd + php php-cgi php-cli Jul 16 07:56:28 good morning Jul 16 07:56:40 someone here ever used meta-virtualization and lxc? Jul 16 07:57:42 vincenet: perhaps you can check in #php? Jul 16 07:58:26 basic question is how to use it, i read that that you will use it like: lxc-create -n mycontainer -t debian --> are there templates for the yocto poky ditribution then? Jul 16 08:00:08 any detail on that would be perfect ;) Jul 16 08:01:20 Ok, thank you mckoan : more widely about recipe, how to know a package exist ? up to there, I used http://recipes.yoctoproject.org/rrs/recipes/ but it is not the first time a library name is not explicitely listed. (I will have training about yocto... in october) Jul 16 08:09:01 package or recipe? Can you give a concrete example? Jul 16 08:13:09 there is nothing about php php-cgi php-cli in http://recipes.yoctoproject.org/rrs/recipes/ also I remenber something similar when adding mp3 support from gst library. I am may be confused with the difference between package and recipe... To add new feature, I add in recipe of my embedded board something like IMAGE_INSTALL += new_feature Jul 16 08:26:48 morning guys Jul 16 08:27:00 kernel modules part 2 :) Jul 16 08:27:09 nice nick name :) Jul 16 08:27:17 thank you Jul 16 08:28:26 http://dpaste.com/3B5BD24 Jul 16 08:28:36 here is bb file for the kernel modules Jul 16 08:29:15 and here is the error: http://dpaste.com/0J119ZB Jul 16 08:29:20 I need your help guys Jul 16 08:49:06 sadly :-( Jul 16 09:04:23 Hi ! Jul 16 09:04:46 How can I list all the installed rpms for a given image ? Jul 16 09:05:08 I have tried to use bitbake -g image and use pn-buildlist to get the rpms, but seems a bit weird Jul 16 09:09:58 jmleo: look at the manifest file for the image Jul 16 09:22:38 jmleo: hmm, cannot you use rpm on the platform itself? Jul 16 09:25:10 morning all Jul 16 09:26:25 jmleo: right, we really only know the full list of packages in the image after it's built, so the manifest file is the place to look - you can also enable buildhistory if you want package dependency graphs to figure out how the various packages got in there Jul 16 09:31:27 bluelightning: Ox4 thx, manifest file is the correct one :) Jul 16 09:31:45 I have scripted a bit to list file sizes, and sort it to get the biggest packages Jul 16 09:35:13 hi guys Jul 16 09:35:55 jmleo: FYI buildhistory already does that for you, so you might want to take a look at it ;) Jul 16 09:36:09 i have an x86_64 machine Jul 16 09:36:10 i am running linux-yocto on it Jul 16 09:36:10 I tried the system with the standard kernel type but now I would like to give preempt-rt a try Jul 16 09:36:10 i thought it would just be a matter of changing the -standard.scc to -preempt-rt.scc Jul 16 09:36:10 but that did not suffice Jul 16 09:36:10 bluelightning: ok, let's try that :D Jul 16 09:36:10 I then updated the KBRANCH from standard/common-pc-64/base to standard/preempt-rt/base Jul 16 09:36:10 but now I am getting patch time failures Jul 16 09:36:11 any pointers will be really helpful Jul 16 09:36:59 precisely i get "SRCREV baad552ea168dc31db31f0be188edefaa28a4aec was specified, but is not reachable" Jul 16 09:37:43 i was using the standard 3.14.24 kernel earlier so i picked the commit where the same tag is merged into standard/preempt-rt/base Jul 16 09:39:12 bluelightning: nice :) Jul 16 09:43:28 anyone? Jul 16 09:45:49 and what about the kernel module of mine? :) Jul 16 09:52:03 abelal: I don't know anything about that stuff, but are the linux-yocto-rt recipes useful as a reference perhaps? Jul 16 09:53:13 bluelightning: thanks for the reply, i will look at that Jul 16 09:58:32 Does this really works for setting root password? http://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#ref-classes-extrausers Jul 16 09:58:44 I am getting warnings saying that the root user already exists. Jul 16 10:01:36 ftonello: yeah, it's wrong - it should say usermod not useradd Jul 16 10:01:51 we should really get that fixed Jul 16 10:02:53 ftonello: look at this https://git.yoctoproject.org/cgit/cgit.cgi/meta-ivi/tree/meta-ivi/recipes-yocto-ivi/images/ivi-image.inc Jul 16 10:06:51 Thanks Jul 16 10:07:55 Ox4: Do I have to pass an encrypted password or not? Jul 16 10:10:57 ftonello: with -P no, with -p yes Jul 16 10:11:25 (-P is an option that we have patched into the native version of useradd/usermod that we build) Jul 16 10:13:14 bluelightning: Oh, ok. Thanks. Jul 16 10:13:28 bluelightning: i was not setting the LINUX_KERNEL_TYPE in the recipe but it fails the same way still Jul 16 10:13:49 bluelightning: to send a patch for the documentation, just change the xml under documentation? Jul 16 10:18:10 ftonello: I just sent a patch for the usermod/useradd thing FYI Jul 16 10:18:44 ftonello: but to answer your question, the docs actually live in a separate yocto-docs repo and then they get pulled automatically into poky Jul 16 10:19:34 bluelightning: Ok, I see. Jul 16 10:19:51 If you can, add a note too explaining the -P option. Jul 16 10:20:06 I was doing that, but I noticed that I don't have the yocto-docs repo here :( Jul 16 10:22:28 ftonello: http://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/ Jul 16 10:23:15 hm Jul 16 10:23:21 I am using meta-sourcery Jul 16 10:23:40 and always receive the message WARNING: QA Issue: /usr/lib/glibc-external/getconf/POSIX@underscore@V7@underscore@ILP32@underscore@OFF32_glibc-external contained in package glibc-external requires libgcc_s.so.1, but no providers found in its RDEPENDS [file-rdeps] Jul 16 10:23:57 abelal: well, linux-yocto-rt should be working, so there must be a difference somewhere Jul 16 10:24:08 without this library the kernel panics Jul 16 10:24:09 abelal: what if you actually build linux-yocto-rt, does that work? Jul 16 10:24:17 but if I copy that library manualy it works Jul 16 10:24:30 bluelightning: that's the next thing i'll be doing :) Jul 16 10:24:58 Ox4: you'll have to speak to the meta-sourcery folks if nobody has an answer here, I certainly don't know what's going wrong there Jul 16 10:26:35 bluelightning: I looked through this https://github.com/MentorEmbedded/meta-sourcery/blob/master/recipes-external/glibc/glibc-external.bb but I don't see the problem Jul 16 10:27:05 anyway I've created an issue here: https://github.com/MentorEmbedded/meta-sourcery/issues/81 Jul 16 10:36:00 ok, what about backports? Jul 16 11:17:07 bluelightning: using linux-yocto-rt did the trick and things are working although I am unable to point out a difference between bitbake env for linux-yocto with rt settings and linux-yocto-rt Jul 16 11:17:20 bluelightning: anyhow it does what's needed :) Jul 16 12:07:13 I have a compilation error on fido I don't understand, any clue ? http://pastebin.com/EZuXhQAf Jul 16 13:19:28 jmleo: ca-certificates? Jul 16 13:19:55 Ox4: What do you mean ? Jul 16 13:20:15 jmleo: do you have ca-certificates installed? Jul 16 13:24:43 Ox4: yes Jul 16 13:26:45 I don't know then Jul 16 13:31:05 can I write my own function in a bb file? Jul 16 13:31:20 not rewrite but write from the scratch Jul 16 13:52:50 Ox4: yes Jul 16 13:53:25 Ox4: seems to be fido related, as master seems (still compiling) to pass this step Jul 16 13:53:43 bluelightning: and it will be called during compilation? Jul 16 13:54:35 Ox4: if you mean adding your own task, you have to specify when you want it to be executed Jul 16 13:55:22 Ox4: see http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#tasks Jul 16 13:56:58 bluelightning: is there a convention how to write functions? Jul 16 13:57:51 and as I understood I can write bash function also, right? Jul 16 13:58:10 Ox4: shell or python, yes Jul 16 13:59:17 Ox4: nop, same error on master Jul 16 14:02:39 jmleo: well, I think it is python related issue. Try to do the same in devshell and debug Jul 16 14:02:59 bluelightning: shell or bash? Jul 16 14:03:27 Ox4: bash is shell ;) but we don't assume bash, if that's your question Jul 16 14:07:44 bluelightning: thanks :) Jul 16 14:08:22 we do assume a posix-compliant shell as /bin/sh, I guess Jul 16 14:08:33 understood Jul 16 14:09:03 and where yocto locates kernel sources fetched from the git? Jul 16 14:09:16 tmp/work/powerbeacon-poky-linux-gnueabi/linux-yocto-custom/2.6.37+gitAUTOINC+meta_machine-r0 correct path? Jul 16 14:09:52 and I see linux-powerbeacon-standard-build with the kernel sources Jul 16 14:11:15 Ox4: it depends on the version of the build system, in fido (1.8) and later things have changed in the way the kernel gets built Jul 16 14:11:38 bluelightning: I am using master branch Jul 16 14:11:51 AIUI, STAGING_KERNEL_DIR is where you can find the kernel source, STAGING_KERNEL_BUILDDIR will give you the build artifacts Jul 16 14:20:55 any idea how to disable LTO in Yocto? Jul 16 14:22:25 bluelightning: can I enumerate several function in the addtask? Jul 16 14:24:24 Ox4: you mean specify multiple dependencies ? Jul 16 14:24:54 yes Jul 16 14:25:06 addtask printdate after do_fetch before do_build Jul 16 14:25:24 but I want addtask foo bar baz printdate after do_fetch before do_build Jul 16 14:26:33 that looks like adding more than one task in a single addtask command - that won't work Jul 16 14:26:34 as I see I cannot Jul 16 14:26:53 so I have to write multiple tasks, right? Jul 16 14:27:13 if you want them to be separate tasks - note that functions can call other functions... Jul 16 14:27:35 I know, but don't want that approach Jul 16 14:27:44 I want to call my functions independently Jul 16 14:27:46 ok so what is it exactly that you are trying to do? Jul 16 14:28:33 just want to call several functions, written by me Jul 16 14:28:59 if those functions are truly independent tasks, then separate tasks make sense Jul 16 14:29:01 if not, not... Jul 16 14:29:12 currently only this works for me: Jul 16 14:29:14 addtask idiocy_output after do_fetch before do_build Jul 16 14:29:14 addtask make_backport after do_fetch before do_build Jul 16 14:29:39 yep, each task you want to add needs its own addtask command Jul 16 14:29:48 understood, thank you Jul 16 14:34:39 bluelightning: this is correct one? http://dpaste.com/17W165X Jul 16 14:43:45 bluelightning: maybe do you have an idea on this error ? http://pastebin.com/EZuXhQAf Jul 16 14:46:28 jmleo: I don't I'm afraid Jul 16 15:03:57 how do I run configure from devshell ? Jul 16 15:09:56 first run configure once outside it, which will emit a run.do_configure script in the temp dir, then run devshell and run ../temp/run.do_configure* Jul 16 15:09:56 bluelightning: why STAGING_KERNEL_BUILDDIR points to work-share/../../ but WORKDIR points to work/../../? Jul 16 15:12:06 JaMa: hi, I reported a problem using qtwebengine. It took me some time to build qtwebengine and the included blink with debugging symbols. In the end the problem was caused by missing fonts Jul 16 15:12:23 I installed ttf-bitstream-vera and now it works Jul 16 15:13:44 perhaps this or another font which satisfies blink was included in the image that you build for testing and so this did not happen. Jul 16 15:26:40 Hi! Howto get a plain bash in devshell? I'm ssh'ing into remote build server, and into a container which doesn't run X or gnome. Jul 16 15:28:34 mcfrisk: https://www.yoctoproject.org/docs/1.8/mega-manual/mega-manual.html#platdev-appdev-devshell Jul 16 15:28:46 which links to https://www.yoctoproject.org/docs/1.8/mega-manual/mega-manual.html#var-OE_TERMINAL Jul 16 15:36:38 hello everyone Jul 16 15:36:49 I got a problem with a cmake recipe Jul 16 15:38:12 After the configuartion step, I receive a toolchain.cmake, which has 2 entries in set( CMAKE_FIND_ROOT_PATH *** ***) Jul 16 15:38:53 1. is the location of the cross compiler, so x86 and 2 ist the destination archtiecture(arm) Jul 16 15:39:47 now 2 libraries files are found Jul 16 15:40:02 *.so in x86 archtiecture and arm archtiecture Jul 16 15:40:25 because x86 is primary, it takes this one and during compiling stage i get assembler command errors Jul 16 15:40:59 I can get rid of thtat path, but then the pkg_config is missing, since there isnt one for arm? Jul 16 15:43:10 i have a so there is the folder /yocto/openembedded-core/build/tmp-glibc/sysroots/zedboard-zynq7/pkgdata Jul 16 15:43:24 but not a file, which can be found by cmake Jul 16 15:43:29 anyone got an idea? Jul 16 15:47:31 em|fb: heh, one would expect missing fonts to cause some reasonable error message .. :/ Jul 16 15:47:57 ~blame software developers Jul 16 15:53:25 guys Jul 16 15:53:28 once again Jul 16 15:54:27 * nerdboy waves at JaMa Jul 16 15:55:03 here is the recipe of the wireless module backport: http://dpaste.com/0PSRSYW Jul 16 15:55:16 and here is compilation error: http://dpaste.com/3FW28ZV Jul 16 15:55:38 could somebody help me with this issue? I am fighting with it two days already :-( Jul 16 15:58:23 * JaMa waves back Jul 16 15:59:45 0x4: you are building a ARM conf file, and then attempting to execute on your host. Jul 16 16:00:22 I don't know much about what exactly you are trying to do, but if you are building modules against a kernel that you have in your DEPENDS, you shouldn't need to build any defconfig, or configuration pieces. Jul 16 16:00:55 if for some reason the package itself has that requirement, and doesn't separate TARGET and host toolchains, you'll need to fix the package, it isn't a build system thing at that point. Jul 16 16:02:20 * zedd has to go get lunch Jul 16 16:02:54 zedd: http://dpaste.com/19ATBRP here is instructions from kernel dev of mine Jul 16 16:06:25 Ox4: those are manual instructions Jul 16 16:09:30 nerdboy: I know, that is the problem Jul 16 16:09:45 conf is built for arm Jul 16 16:10:47 how to build it by system toolchain? Jul 16 16:16:36 one sec, wife talking... Jul 16 16:19:04 nerdboy: I will ping you in hour ok? Jul 16 16:19:31 shouldn't take her that long... Jul 16 16:20:57 Ox4: you should probably just copy an existing recipe Jul 16 16:21:36 i assume you have the kernel package already, so your module package should build against that Jul 16 16:29:33 look at one of the TI module recipes like meta-ti/recipes-bsp/powervr-drivers/omapdrm-pvr_1.9.2253347.bb Jul 16 16:30:28 notice how it points to KERNELDIR="${STAGING_KERNEL_DIR} Jul 16 16:35:45 you should also inherit module Jul 16 16:55:14 "ain't nuthin' with that..." Jul 16 16:55:20 *worng Jul 16 16:55:33 too damn early apparently Jul 16 17:27:03 nerdboy: hey, it's me - Ox4 Jul 16 17:27:18 nerdboy: so, what about my problem? Jul 16 17:28:02 use the proper recipe variables and it should work Jul 16 17:28:16 nerdboy: which variable? Jul 16 17:28:25 look at one of the TI module recipes like meta-ti/recipes-bsp/powervr-drivers/omapdrm-pvr_1.9.2253347.bb Jul 16 17:28:37 notice how it points to KERNELDIR="${STAGING_KERNEL_DIR} Jul 16 17:28:37 ok, thanks Jul 16 17:30:32 nerdboy: I saw it, but I should compile drivers before Jul 16 17:30:56 there are a bunch of drvier recipes Jul 16 17:31:38 inherit module and point stuff to the right places as needed Jul 16 17:32:36 minimal EXTRA_OEMAKE options might do it, or you might need to add a manual make and/or make modules_install Jul 16 17:33:46 nerdboy: hold on, I will show you something Jul 16 17:35:17 nerdboy: when I perform make defconfig-PowerBeacon CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm KLIB_BUILD=[kernel code folder] KLIB=[rootfs folder] Jul 16 17:35:31 it compiles c sources from the kconf directory Jul 16 17:35:50 end then binary file conf is launched Jul 16 17:36:12 don't make defconfig Jul 16 17:36:25 that's part of the kernel recipe Jul 16 17:36:45 your package should assume it's already there since it depends one it Jul 16 17:36:55 *on it even Jul 16 17:37:28 so I need set the options from the backport to kernel and then just compile, right? Jul 16 17:38:31 anyway without defconf it still compiles the kconf sources :-( Jul 16 17:40:01 nerdboy: if I set compiler in a Makefile will it be proper approach? Jul 16 17:40:15 it should be doing out-of-tree build Jul 16 17:40:37 don't hardcode stuff like that Jul 16 17:40:51 there are toolchain variables, etc Jul 16 17:42:24 nerdboy: but I can patch it in runtime for example Jul 16 18:08:54 kergoth: thanks, will try those Jul 16 19:05:11 Hey, a heads up for anyone curious about it, the lxsetattr bug and the performance issue with fifos that were recently reported to me are now fixed in pseudo 1.6.6, available from fine Yocto git servers everywhere. Jul 16 19:05:27 I haven't done the oe-core integration and am not sure I'll be able to soon. Jul 16 19:47:32 nerdboy: are you here? Jul 16 19:48:34 nerdboy: http://dpaste.com/2WSRBD7 Jul 16 19:49:07 I have to run make defconfig :-( Jul 16 21:41:42 no, no you need to run that offline and use the (new) config as your custom defconfig Jul 16 21:42:49 once you can run "make foo_defconfig" cleanly in a terminal it should work in the recipe Jul 16 21:43:02 assuming the recipe is close enough... **** ENDING LOGGING AT Fri Jul 17 02:59:58 2015