**** BEGIN LOGGING AT Wed May 27 02:59:59 2015 May 27 07:07:15 hi all!! May 27 07:07:26 hi Valentin_ May 27 07:07:29 brb May 27 07:08:32 i cross-compiled Qt for yocto, but when i'm trying to qmake my project i get error "Could not find qmake configuration file i586-poky-linux-g++", but config for i586-poky-linux-g++ exists in mkspecs folder May 27 07:31:37 also, if i'm trying cross-compile from ubuntu, i get this error "error: iostream: No such file or directory", I created in Qt Creator new kit, set right sysroot and compiler from this sysroot May 27 07:31:56 i mean my project May 27 07:34:23 try to add §CXXFLAGS to $CXX command May 27 07:34:57 $CXXFLAGS i meant May 27 07:35:23 but that should be used anyway.. May 27 07:39:13 I don't think this is a reason May 27 07:41:30 okay.. try to do: "which qmake" to be sure you use the right one, then do "qmake -query" to see settings.. May 27 07:43:24 you can modify qt.conf to match the paths.. May 27 07:53:47 I solved this! in qmake step in project configuration I override argument "-spec i586-poky-linux-g++" May 27 07:54:37 but now i have another problem, when trying launch my executable, i get error "error while loading shared libraries: libQt5Bluetooth.so.5: cannot open shared object file: No such file or directory" May 27 07:55:05 in Qt folder in lib folder exists libQt5Bluetooth.so.5.5.0 May 27 07:55:17 it seems like version conflict May 27 07:57:41 export qt=/where/qt5/is then export LD_LIBRARY_PATH=$qt/lib:$LD_LIBRARY_PATH -- export PATH=$qt/libexec:$PATH -- export QML2_IMPORT_PATH=$qt/qml -- export QT_PLUGIN_PATH=$qt/plugins May 27 07:59:36 ok! i have another question: how can i get permanent export effect? after reboot all environment variable no longer exists May 27 08:00:16 add them to your .bashrc May 27 08:02:28 in the yocto /etc/skel/.bashrc, is this a right file? May 27 08:05:15 your solution with variables now working :( as i sad earlier it seems like a miss filename May 27 08:05:24 not* May 27 08:07:10 so you are able to compile and link your executable right? but the executable does not find the libraries, so LD_LIBRARY_PATH has be set. May 27 08:07:34 *has to be set May 27 08:13:56 i duplicated and renamed this files and it worked!! May 27 08:14:04 i have another question) May 27 08:14:24 how can I enable bluetooth on system start? May 27 08:15:36 without manual command input: rfkill unblock bluetooth May 27 08:21:13 after Edison reboot i get this "Could not chdir to home directory /home/root: No such device" what does it mean? May 27 08:21:29 "-sh: /home/root/.profile: No such device" May 27 08:24:26 what does PACKAGECONFIG variable do? May 27 08:24:52 the example I have here PACKAGECONFIG[uxa] = "--enable-uxa,--disable-uxa" ...what does it mean really? May 27 08:28:55 I read this http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-PACKAGECONFIG which is good enough. But then how do I enable a feature (let's take uxa as example)? May 27 08:33:22 parrot: in PACKAGECONFIG May 27 08:34:01 u mean setting the PACKAGECONFIG variable? May 27 08:34:07 yes May 27 08:35:17 you could add configuration options depending on distro features, for instance May 27 08:36:14 ok...I think I'm starting the get the drill now...thanks joseppc May 27 08:36:26 parrot: you're welcome! May 27 08:56:36 morning all May 27 09:04:13 bluelightning: morning May 27 09:05:27 hi likewise May 27 09:09:32 does autotools support autogen.sh? May 27 09:10:14 parrot: if you mean autotools.bbclass, not really, it does all of the work that autogen.sh usually does May 27 09:10:44 the thing is my package only has configure.ac which autotools doesn't seem to recognise May 27 09:11:04 parrot: it should, it definitely does for other recipes May 27 09:11:20 parrot: would you be able to pastebin your recipe? May 27 09:12:29 bluelightning: with pleasure http://pastebin.com/PvAYB3n3 May 27 09:13:06 I assume I don't even need to define do configure, compile and install if I dont specify anything special? May 27 09:13:57 parrot: right, you should remove those definitions - it's the do_configure one that is getting in the way of autotools.bbclass doing what it needs to May 27 09:14:39 parrot: oe_runconf effectively only does the part where ./configure is executed with the appropriate arguments May 27 09:16:44 bluelightning: ok..I removed the definition of do_configure and now I got error: must install xorg-macros 1.8 or later before running autoconf/autogen . AFAIK, we do have xorg-macro don't we? May 27 09:22:39 parrot: we do indeed - took me a second to find it, you need to add util-macros to DEPENDS May 27 09:22:58 somewhat poorly named but at least it's there... May 27 09:23:37 heh I thought the same thing too. now it compiles, I just fiddling with files installed but not shipped thingy May 27 09:23:44 but I think I'm good from here May 27 09:25:05 bluelightning: thanks for your helping hands May 27 09:25:17 np May 27 11:49:26 bluelightning: During build of a package, I get this warning "include location "/usr/include" is unsafe for cross-compilation" , followed by build failure May 27 11:50:24 Not sure why it tries to fetch headers from system path, when the same are available in staging May 27 12:18:30 milan: read configure script May 27 12:19:42 ok May 27 12:22:40 milan: which package does that ? May 27 12:23:06 milan: I had this issue with perf, I am gonna post a patch for that once more testing is done here May 27 12:23:33 bluelightning: Hi! Is there any chance the fitImage patches would get applied for Yocto 1.9 please ? May 27 12:24:13 JaMa: sometimes there are hard-coded paths in some pieces of software :( May 27 12:26:00 Marex: It's for samhain-server May 27 12:32:52 Marex: yes or calling some foo-config from host May 27 12:40:51 Marex: I believe they just got merged to master May 27 12:43:21 JaMa: I'm a BFU :) May 27 12:44:21 bluelightning: oh wow, right, I didn't notice, thanks ! May 27 12:44:53 Marex: np, thanks for developing & polishing them :) May 27 12:45:53 bluelightning: nah man, thanks for your help and help from others :) May 27 12:46:13 I found a bug in the Vivante Wayland support in Yocto, what is the best place to report that, Freescale forums? May 27 12:46:20 (there is no freescale IRC channel, right?) May 27 12:46:27 otavio: ^ May 27 12:46:38 otavio: you again released something which is completely broken ? :-) May 27 12:46:46 abelloni: right :) May 27 12:47:37 tmcguire: there's no IRC channel, no May 27 12:49:21 linux-imx? May 27 12:49:56 do you mean me? yes, linux-imx.imx6qsabresd to be precise. May 27 12:50:13 the frame gets corrupted after a client is resized. May 27 12:50:26 got a standalone minimal testcase even. May 27 12:51:09 it would be nice if that testcase could somehow make its way to the Vivante devs. May 27 12:51:17 heh no, i meant maybe there is a #linux-imx channel May 27 12:52:42 ah, #imx6-dev May 27 12:53:14 hmm no, that is for a specific project. May 27 12:56:45 tmcguire: send this to meta-freescale mailing list May 27 12:56:48 tmcguire: http://freescale.github.io/#contributing May 27 12:57:03 tmcguire: I can than add GPU guys in the email afterwards May 27 12:57:28 Marex: me? No way .. I just put the released shit in a less bad form May 27 12:57:37 ah, there is a freescale-specific product on that bugzilla, I see. Thanks octavio! May 27 12:58:08 otavio: waste management :-) May 27 12:58:46 Marex: kkk May 27 13:19:31 otavio: reported as https://bugzilla.yoctoproject.org/show_bug.cgi?id=7811 now, thanks for pointing me to the right place. May 27 13:19:32 Bug 7811: normal, Undecided, ---, otavio, NEW , Buffer corruption after resizing wayland client May 27 13:19:40 CCing the GPU guys would be fantastic. May 27 13:24:32 tmcguire: I did this privately May 27 13:24:41 tmcguire: they are not in bugzilla May 27 13:24:57 thanks, that's more than I had hoped before coming here :) May 27 13:30:27 is there any way to make toaster build specific layer fsimages? May 27 13:31:12 since i cant add more than those on the IMAGE_FSTYPES May 27 13:31:52 running bitbake after toast build is kinda not cool May 27 13:34:47 if the extra types are available in the command line, they should be available in Toaster May 27 13:35:06 if not, that would be a bug... May 27 13:35:33 it builds, but it doesnt create the imagefs May 27 13:35:49 creates all fs but not the specific appended one May 27 13:35:56 bluelightning: they might not be. I am not sure how the list we currently provide is generated May 27 13:37:10 http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/tree/conf/machine/include/rpi-base.inc?h=fido May 27 13:37:14 rpi-sdimg May 27 13:37:58 sorry May 27 13:37:59 this one May 27 13:38:00 http://git.yoctoproject.org/cgit/cgit.cgi/meta-raspberrypi/tree/classes/sdcard_image-rpi.bbclass?h=fido May 27 13:44:12 leowt: this looks like a bug. Could I ask you to open a Bugzila entry? May 27 13:44:43 belen, shure May 27 13:44:51 leowt: a Bugzilla one, I mean … having typing problems today :/ May 27 13:45:02 leowt: thanks! May 27 13:47:33 leowt: can you tell through the variable history in Toaster whether the value you set actually applied? May 27 13:47:47 leowt: this sounds like it's not getting applied rather than that it isn't understood May 27 13:49:56 hmm, maybe I missed that we're actually prescribing the allowed values in the interface May 27 13:59:59 bluelightning https://dl.dropboxusercontent.com/u/8258532/Screen%20Shot%202015-05-27%20at%2014.59.42.png May 27 14:00:01 ? May 27 14:26:52 Hello, I have a bitbake recipe ( http://pastebin.com/68k6BGfe ) where I'm trying to add the ast.py file to /usr/lib/python2.7/ dir for my image May 27 14:27:17 However, when I build my recipe I'm getting the error: The recipe python-ast is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /home/gardarh/yocto-toradex/build/out-glibc/sysroots/qemuarm/usr/lib/python2.7/ast.py May 27 14:27:46 However that file is never installed into my image May 27 14:28:28 does anyone know how to bypass this error or how to install that existing ast.py file into the image? May 27 14:32:40 this line from the error might be relevant as well: Matched in manifest-qemuarm-python.populate_sysroot May 27 14:33:02 gardarh: do you actually need that as a separate recipe? the python recipe already provides ast.py May 27 14:33:12 that's basically what it's telling you May 27 14:34:08 my original problem is that it doesn't appear in my image May 27 14:34:39 bluelightning: This is really what is confusing to me, it seems like this file is listed in some manifest but never ends up on the system May 27 14:35:08 gardarh: whether or not it ends up in your image depends on which package you install into the image May 27 14:35:18 python is split up into a number of different packages May 27 14:36:27 Yeah, I tried running 'grep -rI "ast.py"' on my root meta directory May 27 14:36:30 without any luck May 27 14:37:03 ast.py does not appear anywhere in the openembedded-core/scripts/contrib/python/generate-manifest-2.7.py May 27 14:37:42 is there any way to determine what recipe defines this file? May 27 14:37:48 gardarh: based on the output of "oe-pkgdata-util find-path */ast.py" it looks like you need to add python-misc into your image May 27 14:38:20 or "git grep -l ast.py" in the buildhistory directory May 27 14:38:39 mario-goulart: if you have buildhistory enabled, yes May 27 14:39:00 yeah, assuming buildhistory is enabled. :-) May 27 14:39:51 the nice thing with pkgdata is it's always there, so provided you have a recent enough version of the build system, oe-pkgdata-util should be able to answer these kinds of questions May 27 14:40:16 (the recipe does need to have been built first, of course) May 27 14:40:48 hmm, thanks, looking through buildhistory indicates python-misc brings this file May 27 14:41:00 right, that's what I just said ;) May 27 14:41:03 let met try adding it, see how it goes May 27 14:41:15 right, thanks :) May 27 14:48:24 Worked fine when I added python-misc, thanks so much for the advice May 27 14:50:16 one thing, for the oe-pkgdata-util, what should the pkgdatadir point to? May 27 14:52:46 tmp/sysroots//pkgdata May 27 14:52:59 in newer versions it figures out the directory for you May 27 15:20:52 leowt: can you get a screenshot of what you get when you click on IMAGE_FSTYPES on that page? May 27 15:59:57 belen ive started a new yocto env and i am building a clean rpi image, will post as soon as it concludes May 27 16:01:10 leowt: Thanks! May 27 16:50:23 tmcguire: the gpu guy has reproduced it May 27 16:50:30 tmcguire: is on fix queue May 27 16:50:33 it is May 27 17:01:35 hi #yocto gurus! I have a question for you regarding populating the LICENSE_DIRECTORY . I have a recipe to build a initramfs. When I build the initramfs LICENSE_DIRECTORY gets populated correctly. Howerever, when I try to build a live image, the directory is not populated. May 27 17:01:53 my live image recipe depends on my initramfs:do_rootfs task May 27 17:03:08 how do I get to populate the LICENSE_DIRECTORY from my live image recipe? I tried to make it depend on do_build in such a case it only runs do_populate_lic on the components but not all the other tasks (unpack, patch, compile, etc) May 27 17:12:11 Hi! I'm doing an append to a uboot recipe. This append should build something that depends on the finished kernel image (in case you're wondering, it should build a FIT). What is the best way to proceed with that? The biggest problem is that the final image is an initramfs, which already has to run the kernel recipe twice. May 27 17:14:34 belen https://dl.dropboxusercontent.com/u/8258532/Screen%20Shot%202015-05-27%20at%2018.14.08.png May 27 17:31:00 kergoth: I've updated http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=rpurdie/noupdatedata4 quite a bit. The commit messages are right now (ignoring the debug junk one and the keys tweak/revert) May 27 17:37:14 Hi May 27 17:38:11 There is something I can use in the case of SD-CARD, Compact Flash. analyzing the provided datasheet and use in Linux Embedded? To estimate useful life of the flash device? May 27 17:39:01 cleiton_: automotive-grade emmc should have some guarantees on lifespan May 27 17:39:34 RP: hey, is it normal that Yocto SDK toolchain puts compiler option into $CC variable when I source the environment-setup... script ? May 27 17:39:49 RP: I was always under the impression that CC holds just the name of the compiler, nothing else May 27 17:39:50 Marex, some commnad Linux to this analyse? May 27 17:41:25 cleiton_: I don't know of any, try googling 'sd card torture test' or 'sd card stress test' or 'sd card life expectancy' May 27 17:42:11 Marex, I go googling hehe... May 27 17:46:36 Marex: its very normal, this is how OE compiles most things too May 27 17:51:06 RP: yeah, but I cannot use the SDK toolchain to compile U-Boot tools outside of Yocto anymore, since U-Boot picks $CROSS_COMPILE and from that generates it's own internal $CC by setting it to ${CROSS_COMPILE}-gcc May 27 17:51:32 RP: thus, the --with-sysroot and all other options which are coming from the Yocto's "$CC" are omitted and the build fails May 27 17:51:43 RP: can you give me a hint which part of this chain shall I fix please ? May 27 17:51:51 just pass CC into the u-boot build instead May 27 17:51:54 problem solved May 27 17:52:43 kergoth: I'm using the Yocto SDK toolchain, I build U-Boot outside of Yocto May 27 17:52:49 and? May 27 17:52:59 kergoth: I have $CC set, but the U-Boot Makefile overrides the CC May 27 17:53:01 make "CC=${CC}" would probably d May 27 17:53:07 let me try May 27 17:53:12 most buildssytems don't obey the environment variables in preference to their own definitions. May 27 17:53:14 that's typical May 27 17:53:21 but variables set on the make commandline override what's in the makefiles May 27 17:53:57 kergoth: oh, this works, thanks ! May 27 17:54:38 np May 27 18:04:30 kergoth: thanks a lot :) May 27 18:06:18 :) May 27 18:32:47 What is the best way to get "debug" information from a recipe? I want to echo some variables and check that everything is as it's supposed to be, however when baking stuff I don't see the output anywhere May 27 18:36:32 bitbake -e to examine global configuration metadata, bitbake -e recipename to examine recipe metadata May 27 18:42:04 That was helpful kergoth. Thanks! May 27 18:45:55 np May 27 18:47:10 OT, but for any other zsh users in the crowd, in case it's of use: https://gist.github.com/kergoth/ab858d8bfd37a4770592 May 27 20:03:07 j #beagle May 27 20:10:01 btw is there a Yocto support for NIOS2 ? (Altera softcore) ? May 27 21:32:12 Crofton|work: got a minute? May 27 22:30:04 bluelightning: any thoughts on future devtool sub-commands? we're mulling over adding the functionality for for 1) injecting random files into ${S}, e.g. copying dts files into an appropriate place for compilation, and 2) easier overridding of file:// URIs, e.g. defconfig May 28 00:10:16 kergoth: both of those sound useful... the latter might be better placed in recipetool perhaps May 28 00:10:42 I really have to get some sleep but we ought to talk more about this May 28 00:10:48 'night May 28 00:57:22 k, night **** ENDING LOGGING AT Thu May 28 02:59:58 2015