**** BEGIN LOGGING AT Fri Jun 05 02:59:59 2015 Jun 05 06:20:16 hey I am wondering if its possible via recipe, that the local changes gets picked from my local repo or directory Jun 05 06:20:33 what I have read so far I think bbappend is the solution Jun 05 06:20:42 which is used for similar thing Jun 05 06:20:50 any reference would be helpful Jun 05 07:54:47 What is the recommended way of setting layer priorities? Is it OK to modify them in the last layer config file? Jun 05 08:01:24 I am using beagle board C3 and I built the images for it using this link http://android.serverbox.ch/?p=1273 and http://www.embarcados.com.br/beaglebone-black-yocto-dizzy-versao-1-7/ Jun 05 08:01:26 but during boot up I stuck at Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24) Reading boot sector Jun 05 08:01:30 any clues? Jun 05 08:03:50 morning all Jun 05 08:04:11 bluelightning: hello Jun 05 08:06:08 hi kanupatar_ Jun 05 08:06:30 I am using beagle board C3 and I built the images for it using this link http://android.serverbox.ch/?p=1273 and http://www.embarcados.com.br/beaglebone-black-yocto-dizzy-versao-1-7/ Jun 05 08:06:34 but during boot up I stuck at Texas Instruments X-Loader 1.4.2 (Feb 19 2009 - 12:01:24) Reading boot sector Jun 05 08:06:40 bluelightning: ^^ Jun 05 08:07:04 I'm afraid I don't know much about the beagleboard Jun 05 08:21:05 bluelightning: it is okay Jun 05 09:27:14 I wish to override the following file from my layer: http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx-community/tree/conf/machine/boards/zx3-pm3/zx3-pm3-zynq7.dts?h=daisy Jun 05 09:27:26 How can I do that when it is in the conf folder? Jun 05 09:27:49 in my layer* Jun 05 09:36:45 skfax: it kind of looks like meta-xilinx(-community) use a custom way of pointing to these files Jun 05 09:37:23 hmm, nrossi's not around, or he'd probably be able to point you in the right direction Jun 05 09:38:37 Is MACHINE_DEVICETREE likely a meta-xilinx specific thing? Jun 05 09:41:01 Hmm there seems to be some logic on the bottom here which explains the use: https://github.com/Xilinx/meta-xilinx/blob/daisy/recipes-kernel/linux/linux-machine-config.inc Jun 05 09:41:46 skfax: I believe it is yes Jun 05 09:42:32 I'll try adding a new device tree using FILESEXTRAPATHS from my layer Jun 05 09:47:07 Hmm that change didn't seem to trigger any change in the build. "2488/2488 tasks didn't need to be rerun". Do I need to clean something for it to take effect? Jun 05 09:47:35 Perhaps I'm not allowed to set FILESEXTRAPATHS from a layer config file Jun 05 09:57:38 FILESEXTRAPATHS is typically set from bbappends or recipes Jun 05 10:01:55 does/should overlaying classes work? Jun 05 10:05:29 joshuagl: no Jun 05 10:07:01 abelloni: thanks, that confirms my investigation this morning Jun 05 10:07:13 * joshuagl tries to work out why it *appears* to work in one of his build dirs Jun 05 10:08:03 it does work Jun 05 10:08:18 *but* the thing to remember is it doesn't work like overlaying recipes does Jun 05 10:09:27 bluelightning: Yeah, prepending to FILESEXTRAPATHS in a bbappend file worked Jun 05 10:09:45 classes are found using BBPATH, and the order in which paths appear in BBPATH depends on the order in which layers are listed in BBLAYERS in bblayers.conf (as well as whether the layer.conf prepends or appends to BBPATH) Jun 05 10:10:54 joshuagl: to be honest I usually recommend against overlaying classes... best to get the functionality into the original class upstream, or use your own extension class in the recipes you need it in Jun 05 10:11:27 joshuagl: would you be able to expand on what you're attempting to do? Jun 05 10:12:06 bluelightning: ahhh, so I'd need to have my layer be before meta in BBLAYERS Jun 05 10:12:30 joshuagl: or, make your layer's layer.conf prepend to BBPATH rather than appending Jun 05 10:12:41 bluelightning: or that, canny! Jun 05 10:13:11 bluelightning: I need cmake 3 for one of the recipes in my layer, so have a change kind of like the one recently proposed to cmake.bbclass Jun 05 10:14:22 ah right... so conceivably you could have a cmake3.bbclass which inherits the original one and makes the appropriate changes Jun 05 10:14:33 at least until OE-Core supports cmake 3 Jun 05 10:14:57 bluelightning: right, that's what I was contemplating if overlaying wasn't an option Jun 05 10:15:12 or, keep a temporary "fork" of OE-Core with such a patch applied Jun 05 10:15:41 * joshuagl nods Jun 05 10:15:52 or overlay the class ... Jun 05 10:17:21 sure; the downside with overlaying class files though is that it can be silently not applied due to ordering in bblayers.conf Jun 05 10:17:51 granted, if it's set up appropriately you probably won't hit that Jun 05 10:18:34 indeed, there are certainly pros and cons for each option Jun 05 10:30:40 urg cmake 3 isn't compatible with 2 Jun 05 10:34:54 Crofton|work: another item on my "reasons why i hate cmake" list Jun 05 10:35:05 heh Jun 05 10:37:41 hello Jun 05 10:38:06 * Crofton|work wonders if he should submit a wic class to build the tools it needs to run Jun 05 10:40:24 Crofton|work: yeah, we probably need a way for wic to require native tools Jun 05 10:40:47 I was thinking we could use a wic class that images that want to use would inherit Jun 05 10:40:59 and could add to it to actually run wic at some point Jun 05 10:41:03 bluelightning: I'm usually inheriting the class from another one and then expanding it from here Jun 05 10:41:32 exactly for that "overlaying may or may not work" reason Jun 05 10:41:55 Crofton|work: there's some ongoing discussion about that atm I believe Jun 05 10:42:06 yeah, I'm not sure it was going anywhere Jun 05 10:42:32 there is a bug open Jun 05 10:42:50 I suspect I need to poke people to have that discussion on-list or in the bug Jun 05 10:43:00 the message coml;aining it can't find something isn't clear how to fix Jun 05 10:43:17 so I ahve a class that I use to store the names of what needs builindg :) Jun 05 10:46:37 or I'll just submit a patch to prod them along Jun 05 10:47:06 just having the message tell you the recipe names to build would be helpful :) Jun 05 10:57:08 sorry for being slow :) http://wklejto.org/w/f4e648ac here is how looks my toolchain; I want to use it with `bitbake -c populate_sdk', how to do it? Jun 05 10:57:47 it's already in binary format, cross toolchain x86_64/Linux -> armv8 Jun 05 11:00:05 * ryoshu is studying the docs Jun 05 11:01:11 ryoshu: in order to support an external toolchain you need to create some adaptation recipes for it - meta-sourcery is an example Jun 05 11:01:29 we don't have built-in support for arbitrary external toolchains Jun 05 11:01:56 bluelightning: thank you, looking at it Jun 05 11:13:08 http://elinux.org/images/c/c8/ExternalToolchainsInYocto.pdf interesting resource Jun 05 11:22:56 I don't understand how this works: http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx-community/tree/recipes-kernel/linux/linux-xlnx_3.14.bbappend?h=daisy references file://defconfig and adds "${THISDIR}/${PN}:" to FILESEXTRAPATHS. However the defconfig file is located under "${THISDIR}/${PN}/zx3-pm3-zynq/defconfig". How can the file be found? Jun 05 11:36:48 hi I need to packagee a conf file in my rootfs for libraries and binaries I use {libdir} & {bindir} so to access /var/log Jun 05 11:37:03 is there something like {vardir} which I need to create via install -m Jun 05 11:37:13 although I tried but didn't succeed Jun 05 11:43:06 bluelightning: Running a 'bibake linux' is generating two copies of uImage binary. What could be the reason ? Jun 05 11:45:00 skfax: the file search path also handles subdirectories for anything in OVERRIDES (which includes the machine name) Jun 05 11:45:15 skfax: files in machine-specific dirs should be picked up first Jun 05 11:46:08 niteshnarayanlal: /var is ${localstatedir} Jun 05 11:46:30 niteshnarayanlal: you can see the defaults for these kinds of things at the top of meta/conf/bitbake.conf Jun 05 11:46:47 milan: er, not off the top of my head, no Jun 05 11:47:02 milan: well, I mean I don't know why that would be off the top of my head Jun 05 11:47:18 -rw-r--r-- 2 build build 14377060 Jun 5 15:37 uImage--3.10-r1505041741-apm-p0c-20150506130616.bin Jun 05 11:47:19 -rw-r--r-- 2 build build 10473572 Jun 5 15:37 uImage--3.10-r1505041741-apm-p0c-20150509110318.bin Jun 05 11:47:57 well, even I saw it happen for the first time :( Jun 05 11:49:38 milan: at a guess, it could be that the code is calculating its own timestamp and doing so twice, hence writing out two files Jun 05 11:50:26 (that would of course be a bug) Jun 05 11:53:55 ok Jun 05 11:55:21 joshuagl: FYI I'm assembling some devtool backports for fido, should be able to send them out today hopefully Jun 05 12:01:36 mckoan|away: hello Jun 05 12:02:29 bluelightning: cool! Jun 05 12:02:36 * joshuagl needs to try and schedule an autobuilder run Jun 05 12:12:31 When I make changes in my machine.conf "PACKAGECONFIG_append_pn-qtbase" for Qt5, how do I force a rebuild? It just reports that there is nothing to be done Jun 05 12:15:08 Ah, had to do a cleansstate instead of just a clean Jun 05 13:01:13 hi. i have a problem installing linux-firmware. i have a wifi device with ralink chipset that requires a bin-file, so i added linux-firmware-ralink to my image. but it fails: * opkg_install_cmd: Cannot install package kernel-firmware-ralink. Jun 05 13:01:21 how do i debug that? Jun 05 13:04:20 is there more to the error than that? Jun 05 13:05:08 uh... i'm blind... found the log file... Jun 05 13:05:26 also, you said you added linux-firmware-ralink, but the error is about kernel-firmware-ralink , which did you add? Jun 05 13:06:49 the wrong one, of course ... happy it's friday... Jun 05 13:44:11 May I get a yocto st up procedure for C3 board? Jun 05 14:55:49 bluelightning: ok cool. thank you! Jun 05 15:47:48 any clues how I build sato-minimal with linux-yocto-dev.git ? Jun 05 15:53:44 raykinsella781: you'd set PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-dev" in conf/local.conf Jun 05 15:54:15 cool thats makes sense ... Jun 05 16:58:57 hello all, where should i start with an error like this? Jun 05 16:59:00 ERROR: ExpansionError during parsing /opt/fsl-community-bsp/sources/meta-fsl-arm/recipes-kernel/linux/linux-fslc_4.0.bb: Failure expanding variable S: ExpansionError: Failure expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError: Fetcher failure: SRCREV was used yet no valid SCM was found in SRC_URI Jun 05 17:00:17 jc___: your PV value probably includes ${SRCPV} which is not valid if you aren't fetching from git/svn/etc. in SRC_URI Jun 05 17:03:35 I guess the next question would be: Am i not fetching from git? I did have to change the SRC_URI in 'linux-imx.inc" Jun 05 17:03:50 I just changed it from git:// to http:// Jun 05 17:04:06 I am behind a hhtp proxy Jun 05 17:04:46 I think rather than changing git:// to http:// you should be adding ;protocol=http instead Jun 05 17:05:25 oh, I see. that is a git -global setting? Jun 05 17:05:43 no, it's something our git fetcher understands Jun 05 17:06:03 the prefix must stay the same so that bitbake knows it needs to use the git fetcher Jun 05 17:06:13 bbl Jun 05 17:06:44 isn't it the opposite ? Jun 05 17:06:54 SRC_URI = "git://github.com/Freescale/linux-fslc.git;branch=${SRCBRANCH} ; protocol=http ? Jun 05 17:06:58 http://...;protocol=git Jun 05 17:07:12 i remember seeing this once befor, must look at my notes Jun 05 17:16:01 thank you my fix is: git://...;protocol=http Jun 05 17:22:46 Is it possible to distribute the generated SDK using something like Debian packages instead of a single shell script installed? Specifically I'd like a better way of distributing minor updates to a specific library in a cleaner way then shipping out a new .sh file or sending out replacement files. **** ENDING LOGGING AT Sat Jun 06 02:59:58 2015