Thursday, 2014-03-20

*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC00:07
-YoctoAutoBuilder- build #100 of minnow-lsb is complete: Success [build successful] Build details are at
*** ant_home <ant_home!> has quit IRC00:09
-YoctoAutoBuilder- build #98 of nightly-x32 is complete: Success [build successful] Build details are at
*** jwhitmore <jwhitmore!~jwhitmore@> has quit IRC00:16
-YoctoAutoBuilder- build #104 of nightly-ppc is complete: Success [build successful] Build details are at
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has quit IRC00:27
*** Squix <Squix!> has quit IRC00:31
*** Krise <Krise!> has joined #yocto00:34
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has quit IRC00:34
-YoctoAutoBuilder- build #99 of nightly-fsl-ppc is complete: Success [build successful] Build details are at
*** adelcast <adelcast!~adelcast@> has quit IRC00:45
*** rburton <rburton!> has quit IRC00:51
-YoctoAutoBuilder- build #101 of nightly-x86-64-lsb is complete: Success [build successful] Build details are at
*** rburton <rburton!> has joined #yocto00:56
*** Jin^eLD is now known as Jin|away00:58
*** b1gtuna_ <b1gtuna_!~adam@> has quit IRC00:59
*** rec <rec!~bcochran@> has joined #yocto00:59
*** Squix <Squix!> has joined #yocto01:15
*** Krise <Krise!> has left #yocto01:21
*** LCyrin <LCyrin!> has quit IRC01:24
*** michael_e_brown <michael_e_brown!> has quit IRC01:25
*** rec <rec!~bcochran@> has quit IRC01:25
*** michael_e_brown <michael_e_brown!> has joined #yocto01:25
*** seebs <seebs!> has quit IRC01:29
*** seebs <seebs!> has joined #yocto01:32
*** sgw_ <sgw_!> has quit IRC01:39
*** rburton <rburton!> has quit IRC01:40
*** rburton <rburton!> has joined #yocto01:44
*** Jefro <Jefro!> has quit IRC01:45
*** michael_e_brown_ <michael_e_brown_!> has joined #yocto01:46
*** michael_e_brown <michael_e_brown!> has quit IRC01:49
*** michael_e_brown <michael_e_brown!> has joined #yocto01:51
*** michael_e_brown_ <michael_e_brown_!> has quit IRC01:54
*** michael_e_brown <michael_e_brown!> has quit IRC01:55
*** rburton <rburton!> has quit IRC01:56
*** rburton <rburton!~rburton@> has joined #yocto01:57
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC02:04
*** TanviM <TanviM!~tanvimalh@> has joined #yocto02:09
*** nerdboy <nerdboy!> has joined #yocto02:35
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto02:35
*** rburton <rburton!~rburton@> has quit IRC02:40
*** rburton <rburton!> has joined #yocto02:41
-YoctoAutoBuilder- build #98 of nightly-ppc-lsb is complete: Success [build successful] Build details are at
*** halfhalo <halfhalo!halfhalo@nasadmin/webteam/halfhalo> has quit IRC02:48
*** halfhalo <halfhalo!> has joined #yocto02:48
*** halfhalo <halfhalo!halfhalo@nasadmin/webteam/halfhalo> has joined #yocto02:48
*** halfhalo <halfhalo!halfhalo@nasadmin/webteam/halfhalo> has joined #yocto02:51
-YoctoAutoBuilder- build #106 of nightly-arm-lsb is complete: Success [build successful] Build details are at
*** rburton <rburton!> has quit IRC03:14
*** rburton <rburton!> has joined #yocto03:15
*** Jefro <Jefro!> has joined #yocto03:17
*** rburton <rburton!> has quit IRC03:24
*** rburton <rburton!> has joined #yocto03:25
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto03:27
*** lpapp <lpapp!~lpapp@kde/lpapp> has left #yocto03:27
*** rburton <rburton!> has quit IRC03:34
*** rburton <rburton!> has joined #yocto03:38
-YoctoAutoBuilder- build #98 of nightly-mips-lsb is complete: Success [build successful] Build details are at
*** Jefro <Jefro!> has quit IRC03:42
*** Jefro <Jefro!> has joined #yocto03:45
*** sgw_ <sgw_!> has joined #yocto04:03
*** TanviM <TanviM!~tanvimalh@> has quit IRC04:09
*** Jefro <Jefro!> has quit IRC04:11
spec_Bertux_ I hope your're still around or you find this in a log. I've never done it with Yocto, but I know from other Linux experiences that you can run QT stuff directly to the framebuffer device. Some VGA devices on the PC side even have some acceleration. What hardware are you developing on?04:14
*** rburton <rburton!> has quit IRC04:15
*** rburton <rburton!~rburton@> has joined #yocto04:16
*** Jefro <Jefro!> has joined #yocto04:39
*** fp <fp!~Chaudhary@> has joined #yocto04:41
*** TanviM <TanviM!~tanvimalh@> has joined #yocto04:44
*** fp <fp!~Chaudhary@> has quit IRC04:52
*** rburton <rburton!~rburton@> has quit IRC04:57
*** rburton <rburton!> has joined #yocto04:58
*** Jefro <Jefro!> has quit IRC05:20
*** TanviM <TanviM!~tanvimalh@> has quit IRC05:23
*** roric <roric!> has joined #yocto05:26
*** TanviM <TanviM!~tanvimalh@> has joined #yocto05:29
*** rburton <rburton!> has quit IRC05:35
*** rburton <rburton!> has joined #yocto05:35
*** fp <fp!~Chaudhary@> has joined #yocto05:43
-YoctoAutoBuilder- build #102 of nightly-x86 is complete: Success [build successful] Build details are at
*** fp <fp!~Chaudhary@> has quit IRC06:07
-YoctoAutoBuilder- build #102 of nightly-multilib is complete: Success [build successful] Build details are at
*** SorenHolm <SorenHolm!> has joined #yocto06:17
*** SorenHolm <SorenHolm!> has quit IRC06:25
-YoctoAutoBuilder- build #103 of nightly-mips is complete: Success [build successful] Build details are at
*** tobiash <tobiash!> has quit IRC06:35
*** tobiash <tobiash!> has joined #yocto06:36
*** agust <agust!> has joined #yocto06:37
*** kbart <kbart!~KBart@> has joined #yocto06:39
*** RagBal <RagBal!> has joined #yocto06:51
*** Rootert <Rootert!> has joined #yocto06:52
*** rburton <rburton!> has quit IRC06:54
*** TanviM_ <TanviM_!~tanvimalh@> has joined #yocto06:56
*** TanviM <TanviM!~tanvimalh@> has quit IRC06:57
*** TanviM_ is now known as TanviM06:57
*** rburton <rburton!> has joined #yocto06:59
*** rainerschuster <rainerschuster!> has joined #yocto07:00
*** rainerschuster <rainerschuster!> has left #yocto07:02
*** roric <roric!> has quit IRC07:05
*** wfailla <wfailla!~wfailla@2001:6f8:12d9:13:a45c:4a96:22cf:cd4c> has joined #yocto07:05
*** roric <roric!> has joined #yocto07:05
*** wfailla <wfailla!~wfailla@2001:6f8:12d9:13:a45c:4a96:22cf:cd4c> has quit IRC07:06
*** wfailla_ <wfailla_!~wfailla@2001:6f8:12d9:13:a45c:4a96:22cf:cd4c> has joined #yocto07:06
*** wfailla_ <wfailla_!~wfailla@2001:6f8:12d9:13:a45c:4a96:22cf:cd4c> has joined #yocto07:08
*** tasslehoff <tasslehoff!~tasslehof@> has joined #yocto07:08
*** roric <roric!> has quit IRC07:16
*** fp <fp!~Chaudhary@> has joined #yocto07:22
*** Jefro <Jefro!> has joined #yocto07:25
*** SorenHolm <SorenHolm!> has joined #yocto07:25
-YoctoAutoBuilder- build #100 of nightly-fsl-arm is complete: Success [build successful] Build details are at
*** SorenHolm <SorenHolm!> has quit IRC07:32
*** SorenHolm <SorenHolm!~quassel@> has joined #yocto07:32
-YoctoAutoBuilder- build #103 of nightly-x86 is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1 Building Toolchain Images Building Toolchain Images_1 Publishing Artifacts] Build details are at
*** Jin|away is now known as Jin^eLD07:37
*** TanviM <TanviM!~tanvimalh@> has quit IRC07:38
*** TanviM_ <TanviM_!~tanvimalh@> has joined #yocto07:38
*** TanviM <TanviM!~tanvimalh@> has joined #yocto07:41
*** TanviM_ <TanviM_!~tanvimalh@> has quit IRC07:43
*** tobiash <tobiash!> has quit IRC07:47
*** TanviM_ <TanviM_!~tanvimalh@> has joined #yocto07:47
*** TanviM <TanviM!~tanvimalh@> has quit IRC07:48
*** TanviM_ is now known as TanviM07:48
-YoctoAutoBuilder- build #104 of nightly-fsl-arm-lsb is complete: Success [build successful] Build details are at
*** tobiash <tobiash!> has joined #yocto07:51
*** eballetbo <eballetbo!> has joined #yocto07:51
*** TanviM_ <TanviM_!~tanvimalh@> has joined #yocto07:52
*** belen <belen!> has joined #yocto07:52
*** TanviM <TanviM!~tanvimalh@> has quit IRC07:54
*** TanviM_ is now known as TanviM07:54
*** fp <fp!~Chaudhary@> has quit IRC07:54
*** belen <belen!> has quit IRC07:54
*** g1zer0 <g1zer0!> has joined #yocto07:56
*** dany <dany!> has joined #yocto07:58
*** ant_work <ant_work!> has joined #yocto07:59
*** roric <roric!> has joined #yocto08:11
*** elmi82 <elmi82!> has joined #yocto08:12
-YoctoAutoBuilder- build #105 of nightly-fsl-arm-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at
*** fp_ <fp_!~Chaudhary@> has joined #yocto08:16
*** zeeblex <zeeblex!apalalax@nat/intel/x-upyknogfbpqnlyyw> has joined #yocto08:18
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto08:21
*** kalyank <kalyank!> has joined #yocto08:24
*** mago_ <mago_!> has quit IRC08:25
*** TanviM <TanviM!~tanvimalh@> has quit IRC08:26
*** kalyank <kalyank!> has quit IRC08:30
*** TanviM <TanviM!~tanvimalh@> has joined #yocto08:30
*** TanviM_ <TanviM_!~tanvimalh@> has joined #yocto08:34
*** TanviM <TanviM!~tanvimalh@> has quit IRC08:36
*** TanviM_ is now known as TanviM08:36
*** sameo <sameo!~samuel@> has joined #yocto08:40
*** beaver_545 <beaver_545!~stuart@> has joined #yocto08:41
*** florian_kc is now known as florian08:48
*** beaver_545 <beaver_545!~stuart@> has quit IRC08:48
*** mckoan|away is now known as mckoan08:49
mckoangood morning08:49
*** wgao <wgao!~wgao@> has joined #yocto08:50
*** sme <sme!> has left #yocto08:56
*** beaver_545 <beaver_545!~stuart@> has joined #yocto08:59
*** TanviM_ <TanviM_!~tanvimalh@> has joined #yocto09:07
*** TanviM <TanviM!~tanvimalh@> has quit IRC09:08
*** TanviM_ is now known as TanviM09:08
*** fp_ <fp_!~Chaudhary@> has quit IRC09:14
*** Jefro <Jefro!> has quit IRC09:16
*** mihai <mihai!~mihai@> has joined #yocto09:20
*** fp <fp!~Chaudhary@> has joined #yocto09:24
*** fp <fp!~Chaudhary@> has quit IRC09:26
*** rburton <rburton!> has quit IRC09:32
*** rburton <rburton!> has joined #yocto09:37
*** bluelightning <bluelightning!~paul@> has joined #yocto09:37
*** bluelightning <bluelightning!~paul@> has quit IRC09:37
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto09:37
*** belen <belen!~Adium@> has joined #yocto09:38
*** trollixx <trollixx!> has quit IRC09:40
*** trollixx <trollixx!> has joined #yocto09:40
bluelightningmorning all09:43
*** hasselmm <hasselmm!~mathias@> has joined #yocto09:44
*** fp_ <fp_!~Chaudhary@> has joined #yocto09:46
*** anjandeep <anjandeep!3d5fc1ef@gateway/web/freenode/ip.> has joined #yocto09:58
*** mulhern <mulhern!~mulhern@> has joined #yocto10:19
-YoctoAutoBuilder- build #104 of nightly-mips is complete: Failure [failed BuildImages Running Sanity Tests] Build details are at
*** dany <dany!> has quit IRC10:35
*** dany <dany!> has joined #yocto10:35
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto10:36
lpapphi, any reason why a git repository is not refetched if erm... delete the directory manually in the downloads/git2 folder?10:36
lpappand then run bitbake myrecipe10:36
rburtonbecause it didn't need to re-fetch if it already had done a build?10:39
lpappI removed the workdir fwiw.10:40
lpappI also tried -c cleanall10:40
*** mago_ <mago_!> has joined #yocto10:40
lpappsomething is fundamentally fubar'd. :D10:40
-YoctoAutoBuilder- build #102 of minnow is complete: Success [build successful] Build details are at
lpappI do not yet have PV = "${PVBASE}.${SRCPV}" in the recipe.10:41
rburtonlpapp: if you delete the git/ directory in downloads you also need to delete the .done stamp that says its completed teh download10:41
lpappbut I thought that would not be necessary for cloning if there is no clone yet.10:41
*** dany <dany!> has quit IRC10:41
lpapprburton: yeah, I can double check, but I thought -c cleanall would do that.10:41
lpappyeah, find ./sstate-cache/ -name \*foo\* returns nothing.10:42
lpappah, sorry, you meant download .done10:42
lpappyeah, I deleted them, but it is still not cloning.10:43
lpappI am not sure what more I can do for it to get refetched.10:43
lpappI could wipe my build folder out, but it would be a lot of time to rebuild the things. :/10:44
rburtonbitbake recipe -c fetch -f10:46
*** dany <dany!> has joined #yocto10:47
*** rburton <rburton!> has quit IRC10:58
*** rburton <rburton!> has joined #yocto10:59
*** JimBaxter <JimBaxter!> has quit IRC11:01
*** TanviM <TanviM!~tanvimalh@> has quit IRC11:03
*** reanguiano <reanguiano!> has quit IRC11:03
*** reanguiano <reanguiano!> has joined #yocto11:03
lpapprburton: that fetched it, interesting, thanks.11:06
lpappmust be a bug I assume?11:06
lpapp(or some local setup issues)11:06
rburtonlpapp: local setup or it just didn't need to re-fetch11:07
lpappI should add PV = "${PVBASE}.${SRCPV}" to the recipe though, right?11:07
*** JimBaxter <JimBaxter!> has joined #yocto11:09
lpapprburton: ^11:10
rburtonliterally have no idea why you would do that, so don't ask me.11:11
lpapp(based on a mailing list discussion, it would be done for making sure the stuff is refetched)11:12
lpappnot in my previous case, but in general, if you need to do it while the thing is already built, for instance changing SRCREV)11:13
*** mihai <mihai!~mihai@> has quit IRC11:28
*** bboozzoo <bboozzoo!> has joined #yocto11:29
*** diego_r <diego_r!> has joined #yocto11:31
bboozzoohi, any ideas if FILESEXTRAPATHS_prepend takes a distro name at the end? i'm trying building a poky-tiny image for imx6 and hitting some issues with busybox config11:31
rburtonoverrides like that work on all variables11:32
rburtonso FILESEXTRAPATHS_prepend_poky-tiny is fine11:32
*** lpapp <lpapp!~lpapp@kde/lpapp> has left #yocto11:34
*** SnookEE <SnookEE!~msnook@> has joined #yocto11:37
*** mihai <mihai!~mihai@> has joined #yocto11:37
*** diego_r <diego_r!> has quit IRC11:40
*** diego_r <diego_r!> has joined #yocto11:40
*** joeythesaint <joeythesaint!> has joined #yocto11:44
*** fp_ <fp_!~Chaudhary@> has quit IRC11:46
*** diego_r <diego_r!> has quit IRC11:49
*** fp <fp!~Chaudhary@> has joined #yocto11:56
*** rainerschuster <rainerschuster!> has joined #yocto12:04
*** rainerschuster <rainerschuster!> has left #yocto12:06
*** spec_ <spec_!324a35ca@gateway/web/freenode/ip.> has quit IRC12:07
*** Net147 <Net147!> has joined #yocto12:11
*** fp <fp!~Chaudhary@> has quit IRC12:21
*** adelcast <adelcast!~adelcast@> has joined #yocto12:26
*** TanviM <TanviM!~tanvimalh@> has joined #yocto12:33
*** elmi82 <elmi82!> has quit IRC12:44
*** elmi82 <elmi82!> has joined #yocto12:46
*** yzhao2 <yzhao2!~yzhao2@> has quit IRC12:48
*** yzhao2 <yzhao2!~yzhao2@> has joined #yocto12:48
*** yzhao2 <yzhao2!~yzhao2@> has joined #yocto12:49
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has joined #yocto12:55
*** jbrianceau_away is now known as jbrianceau12:55
*** bboozzoo <bboozzoo!> has quit IRC12:59
*** br1_21 <br1_21!~br1@> has joined #yocto13:01
*** bluelightning_ <bluelightning_!~paul@> has joined #yocto13:15
*** bluelightning_ <bluelightning_!~paul@> has quit IRC13:15
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto13:15
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC13:15
*** bluelightning_ is now known as bluelightning13:16
*** ant_work <ant_work!> has quit IRC13:17
*** dany <dany!> has quit IRC13:18
*** elmi82 <elmi82!> has quit IRC13:19
*** sroy_ <sroy_!~sroy@> has joined #yocto13:22
*** dany <dany!> has joined #yocto13:27
*** SorenHolm <SorenHolm!~quassel@> has quit IRC13:27
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-reohtnueuwkzrcec> has joined #yocto13:29
*** adelcast <adelcast!~adelcast@> has quit IRC13:35
*** fp <fp!~Chaudhary@> has joined #yocto13:40
*** sjolley1 <sjolley1!~sjolley@> has quit IRC13:41
*** nitink <nitink!~nitink@> has quit IRC13:47
*** diego_r <diego_r!> has joined #yocto13:51
*** sjolley <sjolley!~sjolley@> has joined #yocto13:54
*** drfu_ <drfu_!40c71302@gateway/web/freenode/ip.> has joined #yocto13:55
*** tasslehoff <tasslehoff!~tasslehof@> has left #yocto13:55
*** sjolley <sjolley!~sjolley@> has quit IRC13:56
*** fp <fp!~Chaudhary@> has quit IRC14:00
*** drfu_ <drfu_!40c71302@gateway/web/freenode/ip.> has quit IRC14:02
*** munch <munch!> has joined #yocto14:05
*** drfu_ <drfu_!40c71302@gateway/web/freenode/ip.> has joined #yocto14:07
*** dvhart <dvhart!~dvhart@> has quit IRC14:08
*** fp <fp!~Chaudhary@> has joined #yocto14:11
*** Net147 <Net147!> has quit IRC14:16
*** seebs <seebs!> has quit IRC14:23
*** sjolley <sjolley!sjolley@nat/intel/x-dutjdobyppjixtnm> has joined #yocto14:25
*** seebs <seebs!> has joined #yocto14:25
*** pidge <pidge!> has quit IRC14:30
*** elmi82 <elmi82!> has joined #yocto14:36
*** dvhart <dvhart!dvhart@nat/intel/x-rjuhupxtxooutrkw> has joined #yocto14:38
*** hasselmm <hasselmm!~mathias@> has quit IRC14:46
*** adelcast <adelcast!~adelcast@> has joined #yocto14:52
*** TanviM <TanviM!~tanvimalh@> has quit IRC14:53
*** hasselmm <hasselmm!~mathias@> has joined #yocto15:01
*** JimBaxter <JimBaxter!> has quit IRC15:16
*** mago_ <mago_!> has quit IRC15:24
*** mago_ <mago_!> has joined #yocto15:25
*** TanviM <TanviM!~tanvimalh@> has joined #yocto15:27
*** dlerner <dlerner!~dlerner@> has joined #yocto15:34
*** weebet <weebet!> has joined #yocto15:36
*** zeddii <zeddii!> has joined #yocto15:36
*** Xz_ <Xz_!~kmsywula@> has joined #yocto15:39
Xz_hi there15:40
*** Xz_ is now known as Xz15:41
bluelightninghi Xz15:41
*** halfhalo <halfhalo!halfhalo@nasadmin/webteam/halfhalo> has quit IRC15:41
*** Jefro <Jefro!> has joined #yocto15:41
weebetHello Guys, how do you manage package update on the target ? I explain using a very simple example, I have an XML file version 1 on my system. The version 2 of this XML add 10 new items. When I update the package, I want the system to add the lines to the xml file, not replacing it. Is this possible to do with yocto?  ( in my usage, it is more to update a database... )15:43
bluelightningweebet: is that XML file packaged as part of the package or not?15:44
*** halfhalo <halfhalo!halfhalo@nasadmin/webteam/halfhalo> has joined #yocto15:44
weebetyes, it is part of the package created in recipe ( ) and now working on
*** elmi82 <elmi82!> has quit IRC15:46
*** TanviM <TanviM!~tanvimalh@> has quit IRC15:46
weebetsorry must read / XML-config_1.0.bb15:47
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC15:48
*** kbart <kbart!~KBart@> has quit IRC15:48
bluelightningweebet: does the file get edited at all after installation or just stays static?15:51
weebetbluelightning: yes the file get edited after installation15:51
bluelightningok, if you haven't already you'll probably need to add the file it to CONFFILES in the recipe (so it isn't just overwritten) and then use a pkg_postinst function to make the appropriate additions if the file is already present15:52
*** g1zer0 <g1zer0!> has quit IRC15:57
*** dvhart_ <dvhart_!~dvhart@> has joined #yocto15:57
*** roric <roric!> has quit IRC15:58
weebetThank you bluelightning15:59
*** belen1 <belen1!~Adium@> has joined #yocto15:59
*** belen <belen!~Adium@> has quit IRC15:59
*** dvhart <dvhart!dvhart@nat/intel/x-rjuhupxtxooutrkw> has quit IRC15:59
weebetbluelightning : one more question. I work with Danny so are using RPM, does RPM will know that it is upgrading from version 1 to 2 ? or it will install both package beside each other ?16:01
*** blitz00 <blitz00!~stefans@> has joined #yocto16:01
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has joined #yocto16:01
weebetSay, I have a custom software called management_1.0 if I rpm -ivh management_2.0 it will install management_2.0 and will not upgrade management_1.016:01
bluelightningweebet: it'll automatically upgrade since the names match16:03
*** Shadow_Shanghai <Shadow_Shanghai!3b4f3795@gateway/web/freenode/ip.> has joined #yocto16:06
Shadow_ShanghaiHey, I've got a problem when I first build yocto porject, can anyone help?16:07
*** JimBaxter <JimBaxter!> has joined #yocto16:07
Shadow_ShanghaiCurrently 1 running tasks (991 of 5707): 0: linux-yocto-3.8.13+gitAUTOINC+14441275c1195a1bd52a6455ecde006c4722d45f_6f3e338aa9496cf68ad03a98f66c2e98975829c7-r4.1 do_fetch (pid 2469)16:07
dvhart_Shadow_Shanghai, yes. Don't ask to ask, just ask and provide enough information for people to review and respond.16:07
Shadow_ShanghaiMy problem is, as you can see16:08
Shadow_Shanghaithe building process stuck on this task16:08
dvhart_linux-yocto is a huge repository, it takes time to download16:08
dvhart_fortunately, you only have to do the big download once so long as you don't do a clean all16:08
dvhart_yes, really :-)16:08
Shadow_Shanghaihow huge is it, then?16:08
dvhart_$ du -hs linux-yocto-3.816:09
dvhart_that includes some of my personal branches/trees, but that will give you an idea16:09
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has quit IRC16:10
dvhart_just watch the download dir and as long as it's growing in size, it isn't stuck16:10
mckoanShadow_Shanghai: are you sure your firewall lets you use git port?16:10
dvhart_watch du -hs downloads/git2/ ... or similar16:10
dvhart_mckoan, it would have broken well before this point16:10
Shadow_ShanghaiI just saw a file named
Shadow_Shanghaino other directory named
dvhart_anything else in that directory?16:12
dvhart_to demonstrate a successful download of other git repos?16:12
*** b1gtuna <b1gtuna!~adam@> has joined #yocto16:12
mckoandvhart_: life is weird, it happened to me that after I installed Yocto at a customer site after some days the sysadmin suddenly blocked git access.16:12
Shadow_Shanghaiyes, I can use git clone to download poky16:12
dvhart_mckoan, valid point16:13
Shadow_Shanghaidoes it mean my git is ok?16:13
dvhart_Shadow_Shanghai, see my question above16:13
dvhart_$ du -hs
dvhart_much smaller if it's a bare clone like in the downloads dir16:14
Shadow_Shanghaidu: cannot access ‘’: No such file or directory16:15
Shadow_Shanghaistill there is no directory16:15
*** fp <fp!~Chaudhary@> has quit IRC16:16
*** TanviM <TanviM!~tanvimalh@> has joined #yocto16:17
Shadow_ShanghaiDoes the directory appears when all the fetching get done?16:17
Shadow_ShanghaiIt's weird16:17
mckoanShadow_Shanghai: please try git clone git://
dvhart_yeah, try the download manually as mckoan suggests.16:20
dvhart_it's possible it's cached somewhere else first, but I thought it did it directly in the downloads dir16:20
Shadow_ShanghaiIt's cloning16:22
Shadow_ShanghaiHope this can help me skip this task and move on building16:23
*** Krise1 <Krise1!~kro@> has joined #yocto16:23
mckoanShadow_Shanghai: try bitbake -c fetch virtual/kernel16:23
*** fp_ <fp_!~Chaudhary@> has joined #yocto16:24
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has joined #yocto16:25
Shadow_Shanghaithanks, I guess I need to take some patients to wait for downloading16:25
Krise1Hi, im trying to create a recipe with a small web application and im running into some problems. I have assigned a local file as source and when bitbake tries to run do_unpack after it has unpacked the file it throws an error: Failed with exit code 1. When i run that command manualy the extration completes without an error. Is there any extended loggin to see more about that error? or any sugestions to what might be wrong. Thanks16:25
*** blitz00 <blitz00!stefans@nat/intel/x-ngjznprfbjncgezl> has joined #yocto16:26
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has joined #yocto16:26
Krise1btw, i don't have a do_unpack in the bb file. i do have a do_install but it seems the problem occures before that16:27
mr_sciencecan you pastebin your recipe?16:28
mr_sciencelocal file as in a tarball or single file?16:29
Krise1it's a zip file with the webfiles inside a folder named application-0.116:30
mr_sciencezip files should unpack fine16:30
mr_sciencethe SRC_URI file:// is relative to the recipe dir16:31
Krise1yes, inside recipe dir -> files -> webroot -> file.zip16:31
mr_scienceso does your recipe layer have a recipes-foo/bar/webroot dir where the zip file sits?16:31
Krise1yes recipes-foo/webadmin/files/webroot16:32
mr_scienceso "bitbake webadmin -c unpack" works but "bitbake webadmin" blows up somewhere?16:33
*** Jin^eLD is now known as Jin|away16:33
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has quit IRC16:33
Krise1no i havent tried the unpack command. but that failed16:34
mr_sciencetry the second one and pastebin the error16:34
*** Shadow_Shanghai <Shadow_Shanghai!3b4f3795@gateway/web/freenode/ip.> has quit IRC16:34
mr_sciencewell, try -c fetch and -c unpack and see if they actually work16:35
*** belen1 <belen1!~Adium@> has quit IRC16:35
mr_sciencetypically you wouldn't want to commit a zipfile/tarball to your recipe repo16:35
mr_scienceit's fine for initial testing, but i'd stick it somewhere else for "production"16:36
Krise1ok, i tried to find some docs on how to get this right but after going trough for about a week now i still havent found the correct solution for deploying files as a recipe16:37
mr_sciencenormally you'd want an md5sum/sha256sum in your recipe for the zipfile16:37
Krise1ah, yeah im pusing it to a git when i get the hang of this16:37
*** belen <belen!~Adium@> has joined #yocto16:37
*** dvhart_ <dvhart_!~dvhart@> has quit IRC16:37
Krise1but the unpack command failed and when i run the command manualy it dose not throw an error16:38
weebetyou are talking about do_unpack. is it possible to disable the do_unpack ? I want to copy a tar.gz on my target and since I add it to SRC_URI = file://... bitbake will unpack it. So I pack it twice... to what I want16:38
Krise1yeah, do_unpack16:39
Krise1do i need to zip the zip?16:39
Krise1oh, i want it to be unpacked and deployed to a specific folder on the build16:39
*** dvhart <dvhart!~dvhart@> has joined #yocto16:40
kergothweebet: there's a url parameter to disable the unpack. ;unpack=false or ;unpack=0 will disable extraction16:40
Krise1hmm when i look in core2-64-poky-linux/webadmin/0.1-r0 it extracted the folder webadmin-0.1 and that folder contains the corret files16:41
Krise1what else is do_unpack trying to accomplish16:41
kergothKrise1: I don't understand the question16:42
kergothcompressed files in SRC_URI get extracted, it's that simple16:42
weebetthank you kergoth !16:42
weebetkergoth : where did you learn that ?16:43
*** dzoe <dzoe!joe@pdpc/supporter/active/dzoe> has quit IRC16:43
Xzwhat's the difference between binutils-cross and binutils-crosssdk?16:43
kergothweebet: I examined the code. do_unpack in base.bbclass calls bb.fetch2.unpack(), which is in poky/bitbake/lib/bb/fetch2/__init__.py16:44
Krise1i have created simple recipe that should deploy a web application to a folder. but it thorws an error on bitbake saying Task 0 do_unpack filed with exit code '1'. but the files get extracted to the folder16:44
*** zecke <zecke!> has joined #yocto16:44
kergothKrise1: so look at the do_fetch log, and post it to a pastebin for us to look at16:44
kergothsummarizing isnt' going to solve your problem16:44
weebetThank you kergoth.16:45
zeckeJaMa: hi! I am a bit puzzled with the PACKAGESCONFIG of The intent is that users create a .bbappend to replace things?16:45
kergothweebet: np16:45
mr_scienceKrise1: typically you would do something like this:
mr_scienceunpack=no would let you manually do it16:46
kergothI think Krise1 wants it to extract the zip, but weebet doesn't. Krise1 is getting a do_unpack failure16:46
* kergoth shrugs16:46
*** rainerschuster <rainerschuster!> has joined #yocto16:46
mr_scienceotherwise leave it out and let it do its thing16:47
*** rainerschuster <rainerschuster!> has left #yocto16:47
Krise1ok, but do the files have to be hased16:47
kergothlook at the pastebin he just showed you16:47
Krise1yeah kergoth thats right16:47
kergoththeres md5 and sha checksums of the zip file, that's all16:47
kergothand yes, those ones are required16:47
Krise1ok il add it16:48
XzHow can I bbappend .inc file?16:48
kergothXz: you can't16:48
Xzkergoth: that's sad :(16:48
*** dzoe <dzoe!> has joined #yocto16:50
mr_scienceextinction is sad...16:50
*** SorenHolm <SorenHolm!> has joined #yocto16:52
*** e8johan <e8johan!> has joined #yocto16:53
Krise1 ERROR: Function failed: Unpack failure for URL: 'file://webroot/webadmin-0.1.zip16:53
mr_sciencepaste the details16:54
XzI want to add one flag to GCC globally, for every package. Can I do that somehow in my machine.conf file?16:56
mr_scienceis there something funky about that zipfile?16:56
mr_sciencethe only thing i see that looks weird is "shieldbox-webadmin-0.1/:  ucsize 4096 <> csize 0 for STORED entry"16:57
Krise1no it's a standard zip file. when i extract i manualy it all works16:57
Krise1should i use tar instead?16:57
mr_sciencetry it and see16:57
mr_scienceoops, mtg time...16:57
*** zeddii <zeddii!> has quit IRC16:58
Xzdo I just append that flag to CLFAGS in machine.conf?16:59
khemappend to it17:01
khemin local.conf17:01
Krise1BAM! that worked. thanks mr_science17:01
*** mckoan is now known as mckoan|away17:02
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has quit IRC17:02
*** Squix <Squix!> has quit IRC17:03
Xzkhem: I need to append that flag for everybody17:03
Xzkhem: not just for me, *once*17:03
*** wfailla_ <wfailla_!~wfailla@2001:6f8:12d9:13:a45c:4a96:22cf:cd4c> has quit IRC17:03
khemXz: so add it to distro conf17:04
Xzkhem: Yocto glossary doesn't reallt say much about the second17:04
Xzkhem: yeah17:05
khemthat should be a filed as bug in yocto docs then17:05
khembut is the right set here17:06
khemsome packages like eglibc do not want to honor your options for valid reasons17:06
khemand if you butcher in CFLAGS ou might get more issues17:06
Xzso SELECTED_OPTIMIZATION changes CFLAGS for choosen subset of packages, not all of them?17:09
khemit changes it for all17:12
*** drfu_ <drfu_!40c71302@gateway/web/freenode/ip.> has quit IRC17:12
*** nitink <nitink!~nitink@> has joined #yocto17:12
Xzthen I don't understand the difference between SELECTED_OPTIMIZATION and CFLAGS. They both do exactly the same - pass flags to gcc for every package (including binutils/libc)17:14
khemlook at the code17:15
khemin some cases recipes alter it17:15
khemsince you have modified compiler to hack the option in17:15
khemyou might very well hack the compiler further to bundle it with O217:15
khemor any O level17:16
khemthen you dont deal with OE metadata17:16
*** kalyank <kalyank!> has joined #yocto17:18
*** fp_ <fp_!~Chaudhary@> has quit IRC17:23
*** zeeblex <zeeblex!apalalax@nat/intel/x-upyknogfbpqnlyyw> has left #yocto17:24
*** mihai <mihai!~mihai@> has quit IRC17:31
bluelightningkhem: hey, I'm just preparing some fixes for the python manifests inc file and the scripts, but I've noticed some of the dependencies added in 2.7 haven't been added to the 3.3 version - does this change look OK?
*** pidge <pidge!~pidge@> has joined #yocto17:35
*** diego_r <diego_r!> has quit IRC17:39
Krise1when i add install -d to the bb file the log says omitting directory. why is that?17:40
Krise1can i move a directory contents with intall -d?17:41
Krise1install -m17:41
*** nitink <nitink!~nitink@> has quit IRC17:42
*** sameo <sameo!~samuel@> has quit IRC17:46
mr_scienceinstall doesn't have a "move" option afaik17:47
mr_scienceand which task is spitting out "omitting directory" ?17:48
Krise1btw adding the content to tar worked. guess the zip file was broken. but how would i go about moving all the files to a specific directory17:50
Krise1should i use some bash script17:50
*** hasselmm <hasselmm!~mathias@> has quit IRC17:53
mr_scienceyou can do bash commands inside do_install17:54
Krise1ok, so cp -R is okey. cause i read on the openembedded that it should be avoided17:55
mr_sciencewell, it should be but sometimes you kinda have to17:55
mr_scienceat least for initial testing, etc17:56
Krise1ok, that worked. thanks17:56
mr_scienceat some point you would want to clean things up17:56
Krise1yeah, but for production what would be the best route to take. moveing a tar file and running script17:56
mr_science"production" usually means installing correctly to image/usr and what not17:57
Krise1yes, but i would have to use a shell script for that or would i package it another way17:58
kergothKrise1: there's nothing wrong with using cp to copy a subtree. install is only appropriate for individual files/dirs. sometimes you're just stuck with it17:58
kergotheg. meta-sourcery still uses cp to extract bits from the external toolchain sysroot17:58
Krise1ok, thanks. cause i can't see any other way for that web application17:59
* kergoth nods18:00
kergothunless there's an upstream buildsystem to call into, it makes sense to retain the copy in the recipe, but its a case by case thing18:00
*** nitink <nitink!nitink@nat/intel/x-otraneabrxubguij> has joined #yocto18:00
Krise1one more thing. in my image i use udev, and udev add gnome-desktop-testing. and i have to remove it everytime i want to do a build in hob. and udev is still compiled into the image without the gnome-desktop-testing package18:01
Krise1why is udev importing gnome-desktop-testing18:01
Krise1no sorry, it's glib-2.0 thats improting the gnome-destop-testing18:02
Krise1stupid me, i should remove glib-2.018:02
kapareHey, just by curiosity  how do you do a extract with change directory, I'm think more specificly for Krise1 case that want to move a directory. could he simply use tar xvf file.tar.gz -C <new_path>? Is there some option do to this in recipes?18:04
mr_sciencelots of things are build deps but not runtime deps18:04
mr_scienceis it actually installed in your rootfs, or just pulled in at build time?18:05
Krise1but i think i added a recipe that pulls it in18:05
mr_sciencethat's weird because i have a bunch of gnome/glib deps in my xaorg image but nothing has pulled in gnome-desktop-testing or whatever18:06
Krise1hmm, i don't even have X in my image18:06
mr_scienceie, glib-2 is a dependency for lxdm login manager18:07
kergothkapare: yes, subdir=<dir relative to ${S}> in the url18:07
kergothkapare: iirc anyway18:07
kaparekergoth, thx18:09
*** zerus <zerus!> has quit IRC18:09
JaMazecke: you can do it from distro config without .bbappend18:12
zeckeah thanks. I didn't know about PACKAGECONFIG yet and I am reading base.bbclass for it now18:15
bluelightningzecke: of course the code is the ultimate reference, but that variable is also documented in the manual ;)18:16
*** eballetbo <eballetbo!> has quit IRC18:20
zeckebluelightning: yes, but it looks like only how to use it in your package but not how to influence it from the distro18:21
zecke(at least with the dora documentation)18:21
zeckeJaMa: will you accept tufao and libsystemd-qt patches for meta-qt5?18:22
bluelightningzecke: the _pn-<PN> override is usable for setting any variable in a recipe-specific manner18:22
bluelightningzecke: i.e. you can set PACKAGECONFIG_pn-yourrecipe = "..."18:23
JaMazecke: I haven't seen them yet, but maybe I will :)18:23
kergothand _append_pn-foo and _remove_pn-foo. i find often my intent is more accurately reflected by using those rather than an override18:23
kergoththough admittedly, the fact that you can't "un-remove" something is occasionally irritating18:23
zeckekergoth: :)18:23
zeckeJaMa: I haven't written them yet. But the intent is to have !QtProject libs/tools in recipes-qt?18:24
kergothRP: thoughts on changing it so _append/_remove act in order? e.g. an _append defined after a _remove would bring it back, and another _remove after that would remove it again.. i think that would be most intuitive18:24
JaMatrue, in this case you usually want just append18:24
kergothRP: currently a single _remove anywhere will always override all _appends18:24
kergothRP: afaict anyway18:24
bluelightningkergoth: I'm not sure it is what everyone expects18:27
bluelightningkergoth: a lot of people just want "remove this thing, I don't care how it got there"18:27
mr_sciencebluelightning: PACKAGECONFIG_pn-foo = "bar" supposed to work outside of local.conf ?18:27
kergothbluelightning: i think file parse orer would still take care of that in a lot of cases, but its a good point18:27
kergothi don't think being entirely unable to undo a _remove_ is kosher, though18:27
mr_sciencei kinda expected it to work in an image recipe but it doesn't...18:27
bluelightningmr_science: it'll work from any conf file, provided that there's not another PACKAGECONFIG_pn-foo line somewhere afterwards18:28
kergothif my distro wants to remove something today, it *must* use := with oe_filter_out, otherwise the user can't add it back18:28
kergotheven if they want it18:28
bluelightningmr_science: no, that can't work18:28
bluelightningmr_science: recipes cannot change eachother's configuration18:28
mr_scienceso you can set it in the original recipe but not another recipe?18:28
mr_scienceokay, makes sense i guess18:28
bluelightningmr_science: right, or you can set configuration from "above" via conf files for both recipes18:29
bluelightninge.g. DISTRO_FEATURES is set from above and acted upon by many recipes18:30
mr_scienceseems like "above" would include the image level but okay...18:32
bluelightningmr_science: the image is just another recipe18:33
mr_scienceyeah, but it's somewhat "special" compared toa package recipe18:33
mr_scienceconceptually at least18:33
bluelightningmr_science: really all you can do at the image level is decide what packages you want in it and then process the files in the resulting filesystem afterwards (e.g. with ROOTFS_POSTPROCESS_COMMAND) if you need to18:33
mr_sciencesame concept as my current ml argument18:34
mr_scienceto me (being a gentoo guy) isn't "configure" per se, it's preparing the source for configure18:35
bluelightningif images could influence how other recipes were built, you could never have a consistent package feed when building >1 image18:35
kergothmr_science: an image is just another recipe.18:35
kergothit's not magic, it doesn't have any special control18:35
mr_scienceso conceptually a src_prepare task makes more sense than autogen in do_configure18:35
kergothconsider bitbake oneimage twoimage threeimage, what would happen if those try to alter configuration of something else?18:35
kergothwould it rebuild something else three times?18:35
kergoththere's ar eason it's the way it is :)18:35
mr_sciencethat typo is dangerously close to talk-like-a-pirate day...18:37
*** fp_ <fp_!~Chaudhary@> has joined #yocto18:37
*** sgw_ <sgw_!> has quit IRC18:38
*** Krise1 <Krise1!~kro@> has left #yocto18:38
*** belen <belen!~Adium@> has quit IRC18:40
*** TanviM <TanviM!~tanvimalh@> has quit IRC18:58
*** roric <roric!> has joined #yocto19:02
*** TanviM <TanviM!~tanvimalh@> has joined #yocto19:03
*** TanviM <TanviM!~tanvimalh@> has quit IRC19:09
*** TanviM <TanviM!~tanvimalh@> has joined #yocto19:10
*** drfu_ <drfu_!40c71302@gateway/web/freenode/ip.> has joined #yocto19:18
*** zecke <zecke!> has quit IRC19:19
bluelightningkhem: I've sent the patch anyway19:25
*** smartin_ <smartin_!> has joined #yocto19:28
*** staylor <staylor!> has joined #yocto19:36
staylorwhat causes a package to be (skipped) in the bitbake-layers show-recipes output?19:37
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC19:38
kergothgenerally it means that it raised the SkipPackage ecxeption, which means it considers itself unbuildable in the current context19:38
kergothwhich usually means COMPATIBLE_HOST/COMPATIBLE_MACHINE indicates its incompatible with your current configuration19:38
kergothiirc, anyway19:38
staylorthanks I'll look in that direction19:38
*** e8johan <e8johan!> has quit IRC19:43
Crofton|workThis is cool, but we shoudl make one on and use the oe-core toolchain19:48
*** e8johan <e8johan!> has joined #yocto19:48
*** fp_ <fp_!~Chaudhary@> has quit IRC19:49
LetoThe2ndCrofton|work: :)19:51
mr_scienceCrofton: that *is* cool...19:53
mr_scienceand feel free to fork/deploy it19:53
LetoThe2ndCrofton|work: you should've looked into my g+ posts earlier ;)19:53
Crofton|workit seems familiar19:54
*** fp_ <fp_!~Chaudhary@> has joined #yocto19:58
otaviorburton: sent an email about cogl20:01
LetoThe2ndis there anything known about mesa breaking on arm? it seems to compile fine here, but break building the rootfs
*** e8johan <e8johan!> has quit IRC20:12
*** JimBaxter <JimBaxter!> has quit IRC20:14
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has quit IRC20:16
*** e8johan <e8johan!> has joined #yocto20:16
*** sroy_ <sroy_!~sroy@> has quit IRC20:17
LetoThe2ndthis should be the corresponding install log
*** rec <rec!> has joined #yocto20:23
kergothrobertyang: thought about using to add the inter-task deps in archiver.bbclass rather than using ${PN}:<task>?20:24
kergothrobertyang: might be cleaner, since thats specifically for inter-task deps within a recipe20:25
pidgehalstead: We're going to need to check the filesystem on opensuse131-dev. I'm getting input/output errors trying to rm.20:26
*** rec <rec!> has quit IRC20:31
*** zecke <zecke!> has joined #yocto20:32
*** belen <belen!> has joined #yocto20:34
*** dv__ is now known as dv_20:46
*** roric <roric!> has quit IRC20:51
*** belen <belen!> has quit IRC20:52
kergothrobertyang: any objection to adding emission of patch series files next to patches when using 'original' archiver mode, to gain feature parity with copyleft_compliance?20:58
*** SnookEE <SnookEE!~msnook@> has quit IRC21:00
*** br1_21 <br1_21!~br1@> has quit IRC21:03
*** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:5e51:4fff:febb:401d> has joined #yocto21:03
*** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:5e51:4fff:febb:401d> has quit IRC21:03
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto21:03
kapareFrom what I'm seeing the hostname is set by meta/recipes-core/bases-files and this will result in default openembedded then is MACHINE exist it became it. So what will be the best way to change this to something diff to MACHINE? I try local.conf without success...21:06
kapareThere's the this comment that doesn't help me yet: set standard hostname, might be a candidate for a DISTRO variable? :M:21:06
mr_scienceLetoThe2nd: there's no error in that install log21:10
mr_sciencei hate those...21:10
LetoThe2ndmr_science: yeah, thats what i thought too.21:10
mr_scienceusually there's an actual error in there somewhere21:10
mr_sciencedid you look at what mesa packages are in the feed?21:11
LetoThe2ndwhat do you mean exactly?21:11
mr_sciencemaybe it didn't package the mesa_blah ipk for some reason21:11
mr_sciencedo an ls -l on tmp/deploy/ipks/arm-blah/mesa*21:12
*** sjolley <sjolley!sjolley@nat/intel/x-dutjdobyppjixtnm> has quit IRC21:12
LetoThe2nd-rw-r--r-- 2 jd jd 9451418 Mär 20 20:54 tmp/deploy/ipk/armv5te/mesa-dbg_9.1.6-r0_armv5te.ipk21:12
LetoThe2nd-rw-r--r-- 2 jd jd    1522 Mär 20 20:54 tmp/deploy/ipk/armv5te/mesa-dev_9.1.6-r0_armv5te.ipk21:12
LetoThe2nd-rw-r--r-- 2 jd jd    9118 Mär 20 20:54 tmp/deploy/ipk/armv5te/mesa-driver-swrast_9.1.6-r0_armv5te.ipk21:12
mr_scienceit didn't leave unpackaged files since that would be an error21:12
*** challinan_ <challinan_!> has quit IRC21:13
mr_scienceyup, i don't see mesa_9.1.6-r0_armv5te.ipk21:13
LetoThe2ndhm ok? or rather, not ok?21:13
mr_scienceso that would be the reason for the do_rootfs install error21:13
mr_sciencetrying to install a package that doesn't exist21:13
mr_scienceso your mesa build is somewhat fubared21:14
*** fp_ <fp_!~Chaudhary@> has quit IRC21:14
mr_sciencei've had lots of weirdeness lately with changing upstream behavior21:14
LetoThe2ndhehe, this is a totally untinkered dora-10.0.1 for qemuarm21:14
mr_sciencemeaning several things that worked fine in November don't work now21:15
mr_scienceon master anyway21:15
LetoThe2ndthis is the log of a bitbake mesa -f -c package21:16
LetoThe2ndi can also try for head, if you like21:16
kergothkapare: best to bbappend base-files, most likely21:17
mr_scienceLetoThe2nd: i do see a mesa package in that log21:18
mr_scienceso you get a cookie, since i have no idea what's wrong...21:18
LetoThe2ndmr_science: cookie? ;)21:18
mr_sciencethe edible chocolate variety21:19
LetoThe2ndmr_science: anyways, what might help you? trying on HEAD? trying on qemux86?21:19
mr_sciencei guess first you might scan/grep the other build logs and see if you can figure out what happened to the mesa package21:20
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC21:20
mr_scienceif it was actually packaged (which is what it looks like) then i should end up in the feed21:20
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto21:21
*** challinan <challinan!> has joined #yocto21:21
staylorWhat would be the best way to trace why a recipe is listed as (skipped) in the output of bitbake-layers show-recipes, it appears to have appropriate settings for COMPATIBLE_MACHINE.21:22
*** sjolley <sjolley!sjolley@nat/intel/x-qwdjhwmghsockbgw> has joined #yocto21:22
staylorthere is another recipe with a newer version, I'm specifically trying to see why the older version is listed (skipped) in case that's also relevant.21:23
LetoThe2ndmr_science: unfortunately, i have built inside a folder with "mesa" in the path which makes grepping hard. let me fix that and then see.21:23
*** e8johan <e8johan!> has quit IRC21:36
*** smartin_ <smartin_!> has quit IRC21:43
*** drfu_ <drfu_!40c71302@gateway/web/freenode/ip.> has quit IRC21:49
LetoThe2ndmr_science: does maybe give a hint why the mesa package is not built?21:58
LetoThe2ndmh, "NOTE: Not creating empty RPM package for mesa"22:01
*** agust <agust!> has quit IRC22:03
*** zecke <zecke!> has quit IRC22:05
*** dlerner <dlerner!~dlerner@> has quit IRC22:05
*** Jin|away is now known as Jin^eLD22:11
*** Jefro <Jefro!> has quit IRC22:15
mr_scienceLetoThe2nd: sorry, was running some tests on an RC build...22:16
mr_scienceif all you see is the "NOTE" about not creating an empty package then it sounds like the install was image was missing some stuff22:17
mr_scienceso try maybe a "bitbake mesa -c install" and look at the install image dirs/files22:18
mr_sciencecompare to what the recipe has in the FILES_${PN} bits22:18
-YoctoAutoBuilder- build #100 of nightly-oecore is complete: Failure [failed] Build details are at
-YoctoAutoBuilder- build #107 of nightly-fsl-ppc-lsb is complete: Failure [failed] Build details are at
-YoctoAutoBuilder- build #108 of nightly-x86-64 is complete: Failure [failed] Build details are at
-YoctoAutoBuilder- build #103 of minnow is complete: Failure [failed] Build details are at
-YoctoAutoBuilder- build #106 of nightly-arm is complete: Failure [failed] Build details are at
-YoctoAutoBuilder- build #105 of eclipse-plugin-juno is complete: Failure [failed Publishing Artifacts] Build details are at
*** jbrianceau is now known as jbrianceau_away22:21
*** nitink <nitink!nitink@nat/intel/x-otraneabrxubguij> has quit IRC22:29
*** asdf__ <asdf__!180fb763@gateway/web/freenode/ip.> has joined #yocto22:32
asdf__Curious- if I run menuconfig on linux-yocto I'm able to create a config, I can compile/deploy that target and looking at the deploy folder it appears that the modules/packages are setup correctly22:33
asdf__but images like core-image-sato aren't valid targets for menuconfig22:33
*** neabax <neabax!~neabax@> has joined #yocto22:34
asdf__and if I compile linux-yocto, then try to bitbake core-image-sato, my changes are erased and it uses a default config. Is this expected behavior? any way around it?22:34
*** SorenHolm <SorenHolm!> has quit IRC22:35
-YoctoAutoBuilder- build #98 of eclipse-plugin-kepler is complete: Failure [failed Publishing Artifacts] Build details are at
*** TanviM <TanviM!~tanvimalh@> has left #yocto22:36
kergothmenuconfig would be meaningless for core-image-sato. core-image-sato has no configuration22:43
kergothcore-image-sato is just an image, not a kernel22:43
kergothif you want your menuconfig changes to persist, then you need to put your defconfig you create with it in an appropriate place so the recipe uses it22:44
dvhartasdf__, have you read the kernel-dev manual?22:44
kergothmenuconfig was never intended to make permanent changes22:44
dvhartasdf__, that process is meticulously documented there22:44
dvhartthe author is a bit of a know it all, but it's still informative ;-)22:44
* mranostay yawns in22:46
*** sameo <sameo!~samuel@> has joined #yocto22:46
dvhartasdf__, please do let me know if you encounter issues with the manual22:46
kergothgah, I'm not sure if archiver will really work as a replacement for copyleft_compliance for us22:46
asdf__I've read that, was hoping there was a way to avoid creating a custom layer JUST to add bluetooth.22:47
kergoththe archive original sources function is rather heavyweight. emits sstate archives duplicating DL_DIR contents, etc22:47
dvhartasdf__, you can do it in local.conf as well22:47
kergoththat mdoe of operation makes sense for many of the more complex configurations, but the archive original sources only case can be quicker than that, just re-run the task instead of using sstate, and symlink from DL_DIR rather than copying22:47
kergothwhich is how copyleft_compliance works, so there's less impact to enabling it22:47
dvhartKERNEL_FEATURES_pn-linux-yocto += "features/bluetooth.scc" or similar22:47
* kergoth ponders22:47
asdf__I can add kernel config changes to it? I thought it was mostly just for machine declaration and build environment setup22:48
asdf__thank you for the information, that clears it up a bit!22:48
dvhartasdf__, you do most anything in local.conf22:48
dvhartbut you have to be aware of scope22:48
dvhartthus the _pn-...22:48
dvhartThe other thing you could do is ask the recipe maintainer (another know it all) to add the fragment you care about, they just might to it...22:49
asdf__Ahh okay, see I wasn't sure of the scope of local.conf and didn't want to add things that didn't belong there22:50
dvhartasdf__, I would say it doesn't belong there, it belongs in a layer22:51
dvhartbut if you don't want to add a layer, you can do local changes there22:51
asdf__sure, but for testing purposes it'd be okay there?22:51
dvhartjust hard to share with others22:51
dvhartI do that sometimes22:51
Crofton|workDon't forget, get travel apporved, add your names22:51
rburtonkergoth: the new archiver when in original mode simply invokes fetch and "unpacks" anything that is a directory beforing taring it up (thus handling git clones)22:52
asdf__so for beagleboard or the like, it'd be something along the lines of: KERNEL_FEATURES_beagleboard-linux-yocto += "features/bluetooth.scc"22:52
kergothrburton: Yeah, I know. but it uses sstate, which means it then tars up those tarballs into an sstate archive, duplicating the DL_DIR contents, to use to avoid re-running the task later22:53
asdf__or if I just added it to KERNEL_FEATURES it'd apply it to all boards?22:53
rburtonkergoth: never noticed it hitting sstate22:53
kergothI'm talking about the refactored one, no idea on the old one22:53
rburtoncan that be avoided?22:53
kergothbut copyleft_compliance doesn't tar anything, it symlinks, so re-running the task is extremely quick, so there's no need for sstate22:53
kergothpossibly, by special casing the original mode, but there'd be lots of little hacks, since there are other combination modes of operation it supports. e.g. original sources + srpm probably still wants to use sstate to avoid re-creating the srpm :)22:54
asdf__also, is there an easy way to list what features/*.scc's are available to me on the linux-yocto kernel?22:55
asdf__(sorry for the newb questions, just starting off with a beagleboard)22:55
dvhartasdf__, hrm... I believe there is... toms or zedd might know - I usually just search the meta branch myself22:57
*** challinan <challinan!> has quit IRC22:57
asdf__Thank you VERY much dvhart. Got me started. I suppose you're an author on the project. :)22:58
dvhart;-) I'm the Intel kernel lead22:59
rburtonhooray dvhart!22:59
dvhart(for yocto)22:59
asdf__well, that would explain it! cheers!22:59
neabaxdo you guys have any idea why a kernel option  set in my defconfig doesn't get set when the .config is generated?22:59
asdf__side question: will Galileo be added to the BSP's on the yocto page? or is that a non-official support type of thing?23:00
*** sjolley <sjolley!sjolley@nat/intel/x-qwdjhwmghsockbgw> has quit IRC23:00
dvhartGalileo is more of an independent project that uses Yocto, among other things.23:00
dvhartneabax, usually because a dependency is missing23:00
rburtonasdf__: the gailileo site has their bsp to download now23:00
*** bfederau <bfederau!> has quit IRC23:01
*** bfederau <bfederau!> has joined #yocto23:01
neabaxdvhart: does it usually throw a warning about that? I don't see anything in my log.do_configure23:01
*** Jefro <Jefro!> has joined #yocto23:02
dvhartit's in the logs in the build dir... something like "tmp/work/MACHINE*/linux-yocto*/*/linux/.meta/standard/*23:02
dvhartsomething like that... just dumped that from memory23:02
dvhart(that's admittedly a totally crap location for this stuff ;-)23:03
*** Jefro <Jefro!> has quit IRC23:07
*** Jefro <Jefro!> has joined #yocto23:10
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-reohtnueuwkzrcec> has quit IRC23:13
mranostaydvhart: that seems a bit hard to find :)23:13
neabaxAlright it seems the configure step overwrites the defconfig that ends up being patched23:21
neabaxso instead of patching that option in I had to just change the defconfig in the linux-mainline folder23:21
*** Jefro <Jefro!> has quit IRC23:22
kergothneabax: sounds like you'd be better off using a config fragment23:23
neabaxkergoth: thanks, that seems a lot cleaner, I'll look into using that23:25
dvhartneabax, config fragments are also a lot easier to maintain23:26
dvhartyou define only what you really care about23:26
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC23:27
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto23:27
kergothyeah, meta-mentor *still* has an old busybox defconfig, from so long ago int eh mists of time that I have no idea which options we had to enable23:27
*** Jefro <Jefro!> has joined #yocto23:27
kergothso trying to get that into a fragment now is a pain :)23:27
kergothmight just ahve to abandon it and let QA open new issues if we'r emissing something23:28
neabaxit's not super clear in the yocto manual, can you use config fragments in any recipe or does it have to be in the kernel recipe?23:29
kergothnot all recipes even have a config to have fragments of :P23:29
dvhartneabax, busybox and linux-yocto*23:29
kergothbusybox and kernel-yocto recipes support it out of the box today for sure. certain others, but theres' no generic mechanism for non-linux-yocto kernels (yet)23:29
dvhartAlthough you can use them on non linux-yocto sources using the linux-yocto-custom template in meta-skeleton23:30
neabaxso can I use that for linux-mainline or does it only work for kernel-yocto?23:30
fray_I thoguth the cml class supports fragments now.. so as long as the thing being configured uses the cml class you are good.. (which of course also means it uses the kernel-like method of config)23:30
*** fray_ is now known as fray23:31
dvhartneabax, see the linux-yocto-custom recipe and the kernel-dev manual, they document this23:31
kergothnope, doesn't yet23:31
kergothcml1 provides a diffconfig task to let you generate fragments, but it can't use them, since cml1 doesn't provide a generic mechanism for the defconfig -> .config process23:31
kergothevery cml1 recipe doe sthat themselves, so there's no standard DEFCONFIG variable, or place in the build to inject hte fragments23:32
frayI thought it did23:32
frayI guess not..23:34
frayit's apparently pretty simple though23:34
fraydo_configure () {23:35
*** Jefro <Jefro!> has quit IRC23:35
fray -m .config ${@" ".join(find_cfgs(d))}23:35
fray        cml1_do_configure23:35
fray(see for the definition of find_cfgs)23:35
kergotha simple little cml1-config class which does that in a task between do_patch and do_configure, using DEFCONFIG, which we could adapt cml1-based recipes to use, would be nice. i created one along those lines for meta-mentor, but it can be simplified now. it had a fragment filtering pipeline to let you remove bits, but now that we can use _remove, its likely overkill23:37
kergoth is that one, definitely overkill :)23:37
frayI suspect it's not there by default because the kernel and busybox find and combine their fragments differently..23:37
fraybut the busybox 'way' is what I'd suggest for the default.. (minus the busybox specific line which I didn't paste above)23:38
kergothwell, like i said, there's no standard mechanism to even write .config. since its inside of do_configure, there's no injection point, so we can't modify cml1 to handle it without having to change all the recipes anyway23:38
kergothhas to be something new which is opt-in23:38
* kergoth shrugs23:38
fraysimply documenting what I posted above wouldn't be a bad idea..23:41
fraythe only thing busybox does "special" is the setup of the initial .config based on the distro feature flags..23:42
fraythat could probably be do in a do_configure_prepend actually..23:42
fraythen the do_configure could be "more standard"23:42
*** pidge <pidge!~pidge@> has quit IRC23:42
asdf__I can say from a newbie's perspective, a step-by-step guide on how to, say, add the bluetooth module specifically (or any module specifically) would be useful :D23:43
frayUmm.. I have an example of how to enable selinux....23:44
frayadd a .bbappend for the kernel..23:45
fraythen add a custom '.cfg' file..23:45
*** Jefro <Jefro!> has joined #yocto23:45
fraythe contents of the bbappend simply adds the '.cfg' to the SRC_URI.. and add the location of the .cfg to the FILESEXTRAPATHS..23:45
frayso.. something like:  linux-yocto_3.16.bbappend:23:46
*** neabax <neabax!~neabax@> has quit IRC23:46
frayFILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"23:46
fraySRC_URI += "file://myconfigfrag.cfg"23:46
dvhartasdf__, please do send me email feedback on the manual23:46
*** staylor <staylor!> has quit IRC23:46
fraythen linux-yocto/myconfigfrag.cfg contains just the items to enable/disable for your config23:47
fray(but I agree.. the manual should have this info)23:47
dvhartit does23:47
frayespecially since it is fairly easy to do it.. once you know how23:47
*** neabax <neabax!~neabax@> has joined #yocto23:48
frayyup that's it..23:48
dvhartasdf__, there is an example there specifically how to add 8250 support23:48
frayboth the full defconfig, and a "fragment"23:48
dvhartI can't very well document how to add all 5000 possible kernel configurations....23:48
dvhartso some level of abstraction has to be allowed for :-)23:48
*** munch <munch!> has quit IRC23:49
*** Jefro <Jefro!> has quit IRC23:50
dvhartI'm curious - did you read this section and it didn't make sense? Did you not find this section in your search? Sometimes creating the right structure can be a challenge. The manual is intended to be organized by commonly performed tasks - specifically the ones you have been describing23:50
dvhartSo I'm concerned it isn't meeting your needs....23:50
asdf__I guess that's a good point, it does mention that, I just fell back to the 'well does bluetooth.scc even exist by default?, how do I know which modules are supported?"23:51
asdf__the documentation is VERY good, it's just a lot for a newbie to absorb in less than 24 hours23:51
*** sjolley <sjolley!~sjolley@> has joined #yocto23:51
dvhartthat's fair enough23:51
dvhartI was at it two years before I wrote it after all ;-)23:51
frayya.. a link for beginners to 'start here'.. may be useful.. I know the few times I've had to adjust the kernel the items in the section dvhart pointed you at was enough..23:52
dvhartSo that is one good bit of feedback - how do I know which fragments already exist23:52
fraythe scc stuff wasn't needed until you get to more advanced features..23:52
asdf__I actually have to say, of most 'side linux projects' ive seen, the documentation for Yocto is absolutely incredible23:52
dvhartlog that and print it23:52
dvhartbefore the internet dies23:52
asdf__And see, I'm uncertain what something like: KERNEL_FEATURES_beagleboard-linux-yocto += "features/bluetooth.scc" would do as opposed to adding bluetooth enabling in a config fragment.23:53
asdf__"adding bluetooth enabling" - I'm rocking english tonight. Heh.23:54
*** scottrif <scottrif!~scott-len@> has joined #yocto23:54
*** scottrif <scottrif!~scott-len@> has left #yocto23:54
dvhartasdf__, they would do the exact same thing provided they contain the same CONFIG_* lines23:54
asdf__gotcha, and the .SCC includes all of that CONFIG_ line data23:55
asdf__(I need to go look for .scc's)23:55
dvhartthe .scc is a description file that contains links to .cfg files23:55
dvhartacc is also documented in the kernel-dev manual under advanced meta data23:55
dvhartscc even23:55
asdf__There we go, that makes sense.23:56
asdf__again, just a lot of info I'm still sifting through, documentation is amazing, just overwhelming simply based on how much there is of it23:56
*** Jefro <Jefro!> has joined #yocto23:56
asdf__I don't think anything is necessarily lacking in the documentation, for the record.23:56
yoctiBug 6022: normal, Undecided, ---, scott.m.rifenbark, NEW , kernel-dev: How do I know which features are available for KERNEL_FEATURES ?23:57
dvhartasdf__, if you could Cc yourself, you can help review the solution.23:58
asdf__will do, thanks.23:58
*** weebet <weebet!> has quit IRC23:58

Generated by 2.11.0 by Marius Gedminas - find it at!