Tuesday, 2016-07-12

khemit looks like that missing prefix in sysroot is not repeated when rebuilt however the error which was originally reported still remains and it not connected00:00
khemqemu: uncaught target signal 4 (Illegal instruction) - core dumped00:00
khemwhich is qemu: uncaught target signal 4 (Illegal instruction) - core dumped00:00
khemso may be its only that its fooling the prints00:00
*** nighty <nighty!~nighty@d246113.ppp.asahi-net.or.jp> has joined #yocto00:01
khemso now i wonder where do we use qemu during builds for gstreamer1.0-plugins-bad00:01
bluelightningbitbake -g should show that00:03
khemyes I see that its inheriting gobject-introspection00:07
khemwhich does call out for qemu usermode00:07
khemso now I need to see why it fails with clang00:07
khemits possible that some intruction thats now generating by clang in some binary is not understood by qemu00:08
khemand the usermode binary pukes it out00:08
*** toscalix <toscalix!~toscalix@> has joined #yocto00:09
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC00:13
*** evanmeagher <evanmeagher!~MongooseW@> has quit IRC00:22
*** toscalix <toscalix!~toscalix@> has quit IRC00:25
*** billr <billr!~wcrandle@> has quit IRC00:58
*** evanmeagher <evanmeagher!~MongooseW@c-73-71-33-109.hsd1.ca.comcast.net> has joined #yocto01:06
*** fray <fray!~mhatle@> has quit IRC01:31
*** dreyna <dreyna!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto01:35
*** crankslider <crankslider!~slidercra@unaffiliated/slidercrank> has quit IRC01:54
*** armpit <armpit!~akuster@2601:202:4001:9ea0:6ce8:588a:7616:ca9> has quit IRC02:17
*** armpit <armpit!~akuster@2601:202:4001:9ea0:c008:4767:f9d2:dea7> has joined #yocto02:29
*** evanmeagher <evanmeagher!~MongooseW@c-73-71-33-109.hsd1.ca.comcast.net> has quit IRC02:37
-YoctoAutoBuilder- build #498 of nightly-rpm-non-rpm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-rpm-non-rpm/builds/49802:47
*** fray <fray!~mhatle@> has joined #yocto03:26
*** armpit <armpit!~akuster@2601:202:4001:9ea0:c008:4767:f9d2:dea7> has quit IRC03:33
*** armpit <armpit!~akuster@2601:202:4001:9ea0:c008:4767:f9d2:dea7> has joined #yocto03:44
*** evanmeagher <evanmeagher!~MongooseW@c-73-71-33-109.hsd1.ca.comcast.net> has joined #yocto03:48
*** Jefro <Jefro!~jefro@ip-64-134-136-113.public.wayport.net> has joined #yocto03:54
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto04:06
*** Jefro <Jefro!~jefro@ip-64-134-136-113.public.wayport.net> has quit IRC04:11
-YoctoAutoBuilder- build #855 of nightly-world is complete: Failure [failed BuildImages] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-world/builds/85504:13
*** agust <agust!~agust@p4FCB5814.dip0.t-ipconnect.de> has joined #yocto04:18
*** Jefro <Jefro!~jefro@ip-64-134-136-113.public.wayport.net> has joined #yocto04:36
-YoctoAutoBuilder- build #826 of nightly-ipk is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ipk/builds/82604:37
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC04:46
*** Crofton <Crofton!~balister@pool-71-171-10-138.ronkva.east.verizon.net> has quit IRC04:50
*** Crofton|work <Crofton|work!~balister@pool-71-171-10-138.ronkva.east.verizon.net> has quit IRC04:50
*** Crofton <Crofton!~balister@pool-71-171-10-138.ronkva.east.verizon.net> has joined #yocto04:50
*** evanmeagher <evanmeagher!~MongooseW@c-73-71-33-109.hsd1.ca.comcast.net> has quit IRC04:51
*** Crofton|work <Crofton|work!~balister@pool-71-171-10-138.ronkva.east.verizon.net> has joined #yocto04:51
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto04:54
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC04:58
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto04:58
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC05:03
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto05:04
*** Crofton|work <Crofton|work!~balister@pool-71-171-10-138.ronkva.east.verizon.net> has quit IRC05:05
*** Crofton <Crofton!~balister@pool-71-171-10-138.ronkva.east.verizon.net> has quit IRC05:05
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC05:10
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto05:10
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC05:16
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto05:16
-YoctoAutoBuilder- build #820 of nightly-rpm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-rpm/builds/82005:18
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC05:22
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto05:24
-YoctoAutoBuilder- build #870 of nightly-x86-64-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-64-lsb/builds/87005:25
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC05:29
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto05:30
*** Crofton|work <Crofton|work!~balister@pool-71-171-10-138.ronkva.east.verizon.net> has joined #yocto05:32
*** Crofton <Crofton!~balister@pool-71-171-10-138.ronkva.east.verizon.net> has joined #yocto05:32
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC05:34
*** Jefro <Jefro!~jefro@ip-64-134-136-113.public.wayport.net> has quit IRC05:35
*** qt-x <qt-x!~Thunderbi@> has joined #yocto05:36
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto05:37
*** qt-x <qt-x!~Thunderbi@> has quit IRC05:38
*** qt-x <qt-x!~Thunderbi@> has joined #yocto05:41
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC05:42
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto05:43
-YoctoAutoBuilder- build #806 of nightly-deb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-deb/builds/80605:48
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC05:48
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto05:50
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC05:55
*** phatina <phatina!~phatina@82-119-96-90.static.chello.sk> has joined #yocto05:55
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto05:57
*** Jefro <Jefro!~jefro@ip-64-134-136-113.public.wayport.net> has joined #yocto06:02
*** stryx`_ <stryx`_!~stryx@> has joined #yocto06:04
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC06:06
*** TobSnyder <TobSnyder!~schneider@ip9234b44d.dynamic.kabel-deutschland.de> has joined #yocto06:06
*** frsc <frsc!~frsc@> has joined #yocto06:09
*** stryx`_ <stryx`_!~stryx@> has quit IRC06:10
*** stryx`_ <stryx`_!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto06:10
-YoctoAutoBuilder- build #500 of nightly-deb-non-deb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-deb-non-deb/builds/50006:11
*** stryx`_ <stryx`_!~stryx@unaffiliated/stryx/x-3871776> has quit IRC06:14
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto06:15
-YoctoAutoBuilder- build #863 of nightly-x86 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86/builds/86306:15
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC06:21
*** rajm <rajm!~robertmar@cpc14-macc3-2-0-cust149.1-3.cable.virginm.net> has joined #yocto06:23
*** yann <yann!~yann@nan92-1-81-57-214-146.fbx.proxad.net> has joined #yocto06:26
*** stryx` <stryx`!~stryx@> has joined #yocto06:26
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto06:26
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has joined #yocto06:26
-YoctoAutoBuilder- build #876 of nightly-arm is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm/builds/87606:27
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC06:31
*** yann <yann!~yann@nan92-1-81-57-214-146.fbx.proxad.net> has quit IRC06:31
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto06:32
*** hamis_lt_u <hamis_lt_u!~irfan@> has joined #yocto06:34
*** josep <josep!~josep@c-3b1ae455.010-118-73746f7.cust.bredbandsbolaget.se> has joined #yocto06:34
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC06:37
*** pohly <pohly!~pohly@host-091-097-029-052.ewe-ip-backbone.de> has joined #yocto06:38
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto06:39
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC06:45
*** bottazzini <bottazzini!~realBigfo@> has quit IRC06:46
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto06:46
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC06:55
*** marquiz <marquiz!~marquiz@> has joined #yocto06:55
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto06:57
*** bottazzini <bottazzini!~realBigfo@> has joined #yocto06:58
*** grma <grma!~gruberm@> has joined #yocto07:00
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-vopmtgavjqfyfjwz> has joined #yocto07:01
*** jbrianceau_away is now known as jbrianceau07:01
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC07:02
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto07:03
*** csanchezdll <csanchezdll!~user@galileo.kdpof.com> has joined #yocto07:05
*** t0mmy <t0mmy!~tprrt@> has joined #yocto07:05
*** stryx`_ <stryx`_!~stryx@> has joined #yocto07:09
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC07:10
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto07:15
*** fl0v0 <fl0v0!~fvo@pD9F6B209.dip0.t-ipconnect.de> has joined #yocto07:16
-YoctoAutoBuilder- build #881 of nightly-x86-64 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-64/builds/88107:19
*** stryx`_ <stryx`_!~stryx@> has quit IRC07:20
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:20
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC07:20
*** josep <josep!~josep@c-3b1ae455.010-118-73746f7.cust.bredbandsbolaget.se> has quit IRC07:20
*** townxelliot <townxelliot!~ell@> has joined #yocto07:21
*** yann <yann!~yann@85-171-21-92.rev.numericable.fr> has joined #yocto07:21
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto07:21
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC07:26
*** ftonello <ftonello!~felipe@> has joined #yocto07:31
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto07:31
*** Jefro <Jefro!~jefro@ip-64-134-136-113.public.wayport.net> has quit IRC07:33
*** Jefro <Jefro!~jefro@ip-64-134-136-113.public.wayport.net> has joined #yocto07:34
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC07:36
*** frsc <frsc!~frsc@> has quit IRC07:37
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto07:37
*** jku <jku!jku@nat/intel/x-uxdxfgwkcdgxkbwv> has joined #yocto07:37
*** joshuagl <joshuagl!~joshuagl@> has joined #yocto07:40
*** rburton <rburton!~Adium@home.burtonini.com> has joined #yocto07:42
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC07:42
*** aida_ <aida_!~aida@mir31-1-82-224-13-158.fbx.proxad.net> has joined #yocto07:44
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto07:44
-YoctoAutoBuilder- build #482 of nightly-arm64 is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm64/builds/48207:45
*** frsc <frsc!~frsc@> has joined #yocto07:49
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC07:50
*** sa2ajj <sa2ajj!~quassel@dsl-espbrasgw1-50de2f-243.dhcp.inet.fi> has quit IRC07:52
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto07:52
*** aida_ <aida_!~aida@mir31-1-82-224-13-158.fbx.proxad.net> has quit IRC07:54
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC07:56
*** belen <belen!~Adium@> has joined #yocto07:56
*** psnsilva <psnsilva!~psnsilva@193-126-29-154.net.novis.pt> has joined #yocto07:58
*** Jefro <Jefro!~jefro@ip-64-134-136-113.public.wayport.net> has quit IRC07:58
*** Biliogadafr <Biliogadafr!~pin@nat3-minsk-pool-46-53-183-225.telecom.by> has joined #yocto08:01
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto08:02
*** Jefro <Jefro!~jefro@ip-64-134-136-113.public.wayport.net> has joined #yocto08:02
*** belen <belen!~Adium@> has quit IRC08:06
*** belen <belen!Adium@nat/intel/x-qbduhfydtwemuhju> has joined #yocto08:07
*** aida_ <aida_!~aida@mir31-1-82-224-13-158.fbx.proxad.net> has joined #yocto08:08
*** Jefro <Jefro!~jefro@ip-64-134-136-113.public.wayport.net> has quit IRC08:13
*** Jefro <Jefro!~jefro@ip-64-134-136-113.public.wayport.net> has joined #yocto08:15
*** Jefro <Jefro!~jefro@ip-64-134-136-113.public.wayport.net> has quit IRC08:16
-YoctoAutoBuilder- build #836 of nightly-ppc-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-ppc-lsb/builds/83608:30
-YoctoAutoBuilder- build #851 of nightly-x86-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-lsb/builds/85108:36
*** dreyna <dreyna!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has quit IRC08:51
*** sveinse <sveinse!~chatzilla@> has joined #yocto08:53
sveinsebitbake does not support hg:// URLs in SRC_URI, right?08:55
sveinseI get ExpansionError, failure expanding variable SRCPV, MissingParameterError: URL 'hg://...' is missing the required parameter 'module'08:57
mathieu_lathe docs say it is supported, but I had the same issue with svn, you just have to specify a module (the trunk or a branch generally)09:05
sveinsemathieu_la: SRC_URL="hg://...;module=mymodule", right?09:06
sveinseOk, so it's a reference to hg, not to something in oe?09:07
sveinsei.e. a branch?09:07
mathieu_layes it's about what is in your tree09:07
mathieu_lain my case I directed the url to the top folder and module=trunk09:08
*** fledermaus <fledermaus!~vivek@2a00:1098:5:0:5d4f:49fc:3e09:693> has joined #yocto09:13
*** lewiatan <lewiatan!~piotr@b2b-94-79-174-114.unitymedia.biz> has joined #yocto09:25
*** mortderire <mortderire!~rkinsell@> has joined #yocto09:28
-YoctoAutoBuilder- build #245 of nightly-checkuri is complete: Failure [failed BuildImages] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-checkuri/builds/24509:30
sveinsehow do I restart building a recipe from the beginning?09:34
*** vdehors <vdehors!~vdehors@bob75-2-81-56-46-209.fbx.proxad.net> has quit IRC09:37
lewiatanwhat do you mean? you can clean the building of recipe with "bitbake -c cleansstate <recipe_name>"09:39
rburtonbitbake [recipe] -C unpack will tell it to do a build and force unpack to happen, so it does a full build09:40
sveinseI'm learning yocto, and are bringing up a recipe for the first time, so please be patient with me. I'm reading the man, but there's a lot of new concepts to take in09:41
CTtpollardor -c rebuild (I think)09:41
sveinselewiatan: bitbake -c cleanslate resulted in "task do_clean slate does not exist for target"09:42
mathieu_la-c cleanall should clean everything (including the downloading part)09:42
mathieu_lait's cleansstate, not cleanslate09:42
lewiatanit is "cleansstate"09:42
sveinsebah :P09:43
lewiatanand of course after that you need to start recipe again with "bitbake <recipe_name>"09:43
rburtonthe derivation of cleansstate is "clean shared state", where "shared state" if often shortened to "sstate"09:44
rburtonthe top-step nature of clean then build is why I endorse -C unpack, as its a single command09:44
*** toscalix <toscalix!~toscalix@> has joined #yocto09:45
*** diego_r <diego_r!~diego@host65-246-static.10-188-b.business.telecomitalia.it> has joined #yocto09:47
*** vdehors <vdehors!~vdehors@> has joined #yocto09:49
*** crankslider <crankslider!~slidercra@unaffiliated/slidercrank> has joined #yocto09:54
lewiatanrburton: but does "-C unpack" clean/remove old build directory? I personally use bash function for that that first: does cleansstate or cleanall and second: builds the recipe that was just cleaned09:57
hsychlaHi. If I change only the URL in a recipe because it changed on the server, will that trigger a rebuild of the package?10:07
*** belen <belen!Adium@nat/intel/x-qbduhfydtwemuhju> has quit IRC10:09
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto10:10
lpapphi, I may have asked this three years ago when coming to Yocto, so pardon me, but can you remind me again why the branch has to be specified properly when using SRCREV to work? I thought the hash identifier was unique.10:11
*** toscalix <toscalix!~toscalix@> has quit IRC10:14
*** belen <belen!~Adium@> has joined #yocto10:19
sveinsewhat is the advantage over sandboxing recipes with devtool, rather than doing the same thing in-tree?10:27
*** rob_w <rob_w!~bob@unaffiliated/rob-w/x-1112029> has quit IRC10:28
sveinseif I specify SRC_URI="file://" does it copy the files before building them? Does it build it in-source?10:35
-YoctoAutoBuilder- build #821 of nightly-arm-lsb is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-arm-lsb/builds/82110:37
-YoctoAutoBuilder- build #936 of nightly is complete: Success [build successful] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly/builds/93610:39
*** jku <jku!jku@nat/intel/x-uxdxfgwkcdgxkbwv> has quit IRC10:44
*** crankslider <crankslider!~slidercra@unaffiliated/slidercrank> has quit IRC10:44
*** jku <jku!jku@nat/intel/x-mrxtimftkplnegwn> has joined #yocto10:46
*** fl0v01 <fl0v01!~fvo@pD9F6ACA5.dip0.t-ipconnect.de> has joined #yocto10:49
*** fl0v0 <fl0v0!~fvo@pD9F6B209.dip0.t-ipconnect.de> has quit IRC10:52
sveinseI trying to run bitbake-layers show-layers (while reading the dev. manual). I then get: ERROR: Only one copy of bitbake should be run against a build directory10:53
*** belen <belen!~Adium@> has quit IRC11:00
*** redengin <redengin!~redengin@c-67-160-25-22.hsd1.wa.comcast.net> has quit IRC11:00
*** belen <belen!~Adium@> has joined #yocto11:00
*** redengin <redengin!~redengin@c-67-160-25-22.hsd1.wa.comcast.net> has joined #yocto11:00
rburtonlewiatan: if your using autotools or cmake then the build directory is always removed before a build, so "it depends"11:05
rburtonlpapp: iirc its basically a sanity check11:05
lewiatanok. thanks rburton11:05
rburtonlpapp: you can disable the sha-is-on-branch check if you have to grab a srcrev which isn't on any branch11:06
rburtonlpapp: looks like bitbake a9112a introduced the check11:08
lpapprburton: right, so I was going to try removing the branch specification whether the SRCREV would work on its on then.11:09
lpappwhen both specified, in our Yocto version, the branch takes precedence, apparently.11:10
rburtonis that a very old bitbake?11:10
rburtonwith SRCREV=abc and branch=foo you should be unpacking rev abc on branch foo, or erroring11:11
lpapprburton: daisy11:11
*** sameo <sameo!samuel@nat/intel/x-jivxylzwduyidhjy> has joined #yocto11:12
sveinseCan I get bitbake to show all the commands only pertaining to one receipe?11:14
rburtonsveinse: bitbake -e [recipe]?11:15
*** maxin <maxin!~maxin@37-219-225-102.nat.bb.dnainternet.fi> has joined #yocto11:15
rburtonsveinse: do you mean what it will run for a particular task?11:15
sveinseIn my recipe bitbake -C unpack does not work. It apparently does not start over. It says task do_unpack does not exist, and then it start to compile11:16
rburtonno unpack is quite unusual11:16
rburtonmight be worth trying -C do_unpack just in case there was a bug in an older version :)11:17
sveinseThis being a qt application, I have a custom do_configure() section which runs qmake, but I cannot find any output showing me that it has run qmake. This is why I want to start over11:17
rburtonthere are classes to do qmake for you11:18
sveinseI use require recipes-qt/qt5/qt5.inc, which is what our subcontractor did for a similar qt application11:19
rburtonand that would be why nothing works11:19
sveinseThen I don't understand why the other qt app works... hmm11:20
rburtonis your app qt5?11:20
rburtonhttps://github.com/meta-qt5/meta-qt5/blob/master/recipes-qt/tufao/tufao_1.2.1.bb is fairly simple11:20
rburtonbasically, inherit cmake_qt5 if its using cmake with qt5 bits11:20
rburtonor https://github.com/meta-qt5/meta-qt5/blob/master/recipes-qt/qsiv/qsiv_1.1.bb if its using qmake11:20
rburtonall you *need* is the meta-qt5 layer, inherit qmake, and you're done11:21
rburtonerm, inherit qmake511:21
rburtonthe only reason to inherit qt5.inc is if you're writing a qt5 recipe11:21
rburtonso i'd have a moan at your contractor :)11:22
sveinseNow I'm actually even more confused. How can this other app work then...11:22
sveinseYes, it seems I have to11:22
rburtonwell, qt5.inc isn't going to tragically break the recipe, its just stupid11:22
rburtonshare their recipe if you'd like a review done of it :)11:22
sveinseThis is one of the reasons I'm/we're learning yocto now11:22
rburtonif you're using a fairly recent yocto, then the recipetool command is great at writing starting points for recipes11:24
sveinseI've been doing embedded linux systems for many years, but yocto is somewhat a handsful I'd admit11:24
sveinseSo pardon me for asking stupid and basic questions :D11:24
rburtonjust do recipetool create [some uri] and it will write a starting point11:24
rburtonno need, that's what this channel is for :)11:25
mathieu_laI have some login issue with krogoth, it seems that 20 char passwords do not work (8 char works)11:30
mathieu_laI found some related issues with tinylogin (now part of busybox), how do I check if I'm using it?11:30
sveinsecan I get bitbake to output everything for a specific recipe or step (do_configure) while running bitbake?11:31
rburtonsveinse: bitbake -e recipe will have the shell in the output if you grep it, or go to the work dir and eg temp/run.do_configure has the full script that runs11:33
sveinsewhoah, that was verbose11:34
rburtonyeah pipe though less ;)11:35
rburtonyou did say "everything" ...11:35
sveinsewell, I still haven't found the output I'm looking for, so yes, my bad: I meant the execution of the task, which would be running qmake and getting its output in this case11:36
rburtonthe output would be in temp/log.do_configure11:38
rburtonrun.do_configure will have you running qmake, unless what you're doing is not working11:38
rburtonas i said, just inheriting the right qmake5 class should do everything for you11:38
rburtonfor actual help, share the recipe11:39
*** vdehors <vdehors!~vdehors@> has quit IRC11:39
sveinsefirstly, bitbake -e did not run qmake output. Secondly, I have added qmake5, and I saw some configure output, so I think its working. Lastly, I will share it11:40
sveinseDo you always use the tmp/ log output for output? Isn't that tedious?11:41
*** nighty <nighty!~nighty@d246113.ppp.asahi-net.or.jp> has quit IRC11:41
*** lpapp <lpapp!~lpapp@kde/lpapp> has left #yocto11:41
*** vdehors <vdehors!~vdehors@> has joined #yocto11:42
*** berton <berton!~fabio@> has joined #yocto11:43
sveinsemine is in tmp/work/cortexa9-vfp-neon-poky-linux-gnueabi/mypkg/1.0-r0/temp/log.do_configure which is a handsfull11:43
rburtonwell, that's the output from running what you told it to do11:45
rburtonpersonally i use "bb" to see logs easily11:45
rburton"$ bb log mypkg configure" is a lot easier11:46
sveinserburton: aha, right! I would think that using this very long path would seem to tedious11:47
sveinsewhat in the recipe controls where it is built: I have tmp/work: all-poky-linux, cortexa9hf-vfp-neo-poky-linux-gnueabi, cortexa9hf-vfp-neo-mx6qdl-poky-linux-gnueabi and so on?11:47
mathieu_lalooks like I'll have to add another repo in my installation, this seems really handy11:47
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC11:48
rburtonsveinse: your machine and its tune controls where it ends up11:49
sveinseIs it difficult to write an image recipe? We have a custom image format that we ultimately will have to integrate with yocto11:53
sveinseI notice that the log.do_configure does not contain the command it executes, only its output. Is that possible to read somewhere?11:59
sveinseYes.... run.do_configure12:00
sveinseThis logging scheme is apparently going to take some getting used to...12:00
*** mckoan|away is now known as mckoan12:00
rburtonhm there is a way to get the sh output in the logs12:01
rburtontbh, probably sensible to enable that12:01
sveinseis yocto always building in-source?12:03
rburtonup to the recipe (or class, really). autotools and cmake default to out of tree12:04
rburtonif qmake does in tree but its trivial to make it out out of tree then it should be fixed to do that12:04
sveinseqmake as well? do you know?12:04
rburtonmy knowledge of qt is limited at getting it out of oe-core and into other layers so i don't need to care about it12:05
sveinsewe have always built qt, qmake qt apps, linux kernel out of tree, so yes, its possible12:05
sveinseis it possible to temporarily disable parallel builds, or do I need to edit my local.conf to do it?12:09
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has joined #yocto12:11
mathieu_laPARALLEL_MAKE = "-j 1" bitbake  [recipe] should override it I guess12:11
*** LocutusOfBorg <LocutusOfBorg!~Gianfranc@ubuntu/member/locutusofborg> has left #yocto12:12
mathieu_la(without spaces of course)12:12
sveinsemathieu_la: heh, yeah. shell parsing is different that bb rules ;)12:13
sveinsehmm. I've changed SRC_URI, and bitbake -C unpack does not do much12:17
*** sno <sno!~sno@p578b540c.dip0.t-ipconnect.de> has quit IRC12:31
*** sno <sno!~sno@b2b-78-94-80-58.unitymedia.biz> has joined #yocto12:35
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto12:35
*** lamego <lamego!jose@nat/intel/x-xntfpwjklzfedxsa> has joined #yocto12:36
*** t0mmy <t0mmy!~tprrt@> has quit IRC12:37
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has joined #yocto12:38
*** t0mmy <t0mmy!~tprrt@> has joined #yocto12:44
*** paulg <paulg!~paulg@> has joined #yocto12:45
*** JaMa <JaMa!~martin@ip-89-176-104-169.net.upcbroadband.cz> has joined #yocto12:52
*** nighty <nighty!~nighty@s229123.ppp.asahi-net.or.jp> has joined #yocto12:57
*** grma <grma!~gruberm@> has quit IRC12:59
*** t0mmy <t0mmy!~tprrt@> has quit IRC13:05
*** ziggo <ziggo!~ziggo@> has quit IRC13:10
sveinseHow do I reset everything pertaining to a recipe? That is delete states, output, everything?13:10
sveinsebitbake -c cleansstate erase every output, but does not redownload the code when SRC_URI has changes. bitbake -C unpack does not have any impact13:22
rburton-c cleanall will also delete from DL_DIR, so forcing you to re-download the tarball13:26
rburtonof course you only need to do that if you changed the tarball and need to re-fetch it13:26
*** igor2 <igor2!~igor@> has joined #yocto13:26
*** benjamirc <benjamirc!~besquive@> has joined #yocto13:26
sveinserburton: Its hg src repo, not a tarball13:27
rburtonah, you want to set SRCREV to ${AUTOREV} so it will fetch and incorporate updates on every build13:28
sveinserburton: actually I'm stuck further behind than that: I created a recipe based on a file location using devtool, and I've later edited SRC_REV to point to the upstream code. Now, I've deleted my local file location, but I just can't get it to take.13:30
sveinseeven running bitbake -c cleanall, and then rerunning the recipe, it wants to configure the old now gone directory....13:31
sveinseThere is some state stuck here somewhere13:31
*** joeythesaint <joeythesaint!~joe@vegas.deserted.net> has joined #yocto13:32
jkusveinse: likely something wrong with the recipe, can you share it?13:32
sveinsewhich paster?13:32
*** aida_ <aida_!~aida@mir31-1-82-224-13-158.fbx.proxad.net> has quit IRC13:33
sveinse(some channels ban you if you pick the wrong one :P )13:33
*** t0mmy <t0mmy!~tprrt@> has joined #yocto13:38
rburtonsveinse: you likely need to set S (where the sources have ended up).  it defaults to ${WORKDIR}/${PN}-${PV}, which works for 99% of tarballs but i doubt it works for this13:38
rburtonno idea what directories the hg fetcher uses, for git you need to use S="${WORKDIR}/git"13:39
sveinserburton: yes, let me try that13:39
*** jku <jku!jku@nat/intel/x-mrxtimftkplnegwn> has quit IRC13:40
rburtonalso you can remove section and homepage, and hopefully paralllel_make - fix your app instead :)13:40
*** cference <cference!~cference@> has joined #yocto13:41
sveinserburton: Oh, the parallel_make is because I know it does not compile, and I'd like to view the cause without other interleaving msgs. It will be gone :D13:41
rburtonheh fair enough :)13:42
*** CTtpollard <CTtpollard!~tom@82-70-136-246.dsl.in-addr.zen.co.uk> has quit IRC13:42
*** nish <nish!~nisha@> has joined #yocto13:43
*** CTtpollard <CTtpollard!~tom@82-70-136-246.dsl.in-addr.zen.co.uk> has joined #yocto13:44
*** nish is now known as nisha13:44
sveinsebtw, perhaps hg support is dodgy. I see no effort trying to clone with hg anywhere.13:44
sveinseAs a development effort, is it possible to configure SRC_URI such that it will copy it from a local location, not just use it directly?13:44
rburtonfor the general situation where you want to use a local clone instead of the canonical upstream, then yes you can use the externalsrc class.13:46
sveinseaahhhhh and d'oh: devtools crates workspace/appends/myapp.bbappend where it sets EXTERNALSRC and co!13:47
rburtonthe hg fetcher is definitely less used than the others13:47
sveinsewell our company use hg (after having a serious comparison between hg and git a few years back). Hg won due to better windows support at the time. Boy, I regret that we did so!13:49
*** sameo <sameo!samuel@nat/intel/x-jivxylzwduyidhjy> has quit IRC13:49
*** belen1 <belen1!~Adium@> has joined #yocto13:54
*** belen <belen!~Adium@> has quit IRC13:55
sveinseI can delete the whole .bbappend file when it only contains EXTERNALSRC and EXTERNALSRC_BUILD right?13:56
*** sameo <sameo!~samuel@> has joined #yocto13:56
rburtonif you dont want those yeah13:57
sveinsewhy is devtool splitting the recipe like this?13:58
sveinseTook me a few hours to find it :(13:58
rburtonarmpit: would you be willing to take 9383 then?13:58
rburtonsveinse: because the appends are not needed in the recipe and shouldn't be accidently committed13:59
sveinseSo it will override the official SRC_URI and enable one to work local only before going to the real deal, right?14:00
rburtonnot before, instead of14:05
sveinseit didn't work. I commented out the lines in the .bbappend file, but it still does not fetch the sources after -c cleanall :(14:06
sveinsebitbake -C unpack also had no effect14:07
sveinseto be honest, I14:08
sveinseI'm giving up soon...14:08
rburtonjust delete the bbappend to be sure its gone14:08
*** hamis_lt_u <hamis_lt_u!~irfan@> has quit IRC14:12
sveinserburton: That seemed to work, its now fetching mercurial host tools. Commenting the bbappend file wan't enough for some reason14:12
rburtonshould have been, but <shrugs> working now14:13
*** joshuagl_ <joshuagl_!~joshuagl@> has joined #yocto14:14
*** joshuagl <joshuagl!~joshuagl@> has quit IRC14:15
*** t0mmy <t0mmy!~tprrt@> has quit IRC14:15
*** kad <kad!~kad@unaffiliated/kad> has quit IRC14:15
*** kad_ <kad_!~kad@dsl-hkibrasgw3-54fb77-110.dhcp.inet.fi> has joined #yocto14:15
*** t0mmy <t0mmy!~tprrt@> has joined #yocto14:15
*** aehs29 <aehs29!~aehernan@> has joined #yocto14:16
sveinsenext complication:  SRC_URI fails if it looks like this "http://dkhg.local/hg/QtApp" as its missing module, but hg clone fails if it looks like this "http://dkhg.local/hg/QtApp;module=default"14:18
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC14:18
sveinseIs there another way to specify the module?14:18
rburtonwhy does the clone fail?14:19
rburtonliterally never used hg14:19
sveinseIt sais "http://dkhg.local/hg/QtApp;module=default" is not a valid URL for a hg repo14:20
sveinseIt smells like a parsing bug in bitbake14:20
rburtonwhat's your SRC_URI?14:20
sveinsethe above14:20
rburtonits not, as neither of those say hg://14:20
sveinseSorry, manual typeout error, it sais hg://14:21
*** madisox <madisox!~madison@> has joined #yocto14:21
rburtonyeah might be a bug in the fetcher.  bitbake/lib/bb/fetch2/hg.py, probably _buildhgcommand() is a good place to start14:22
sveinsedarn, the lake is deeper than I'd hoped it would be it seems :(14:23
sveinseCan you do a    "URL;name=foo" and SRC_URI[name.module=... Hmm, no because name would interfer14:25
rburtonit looks like its expecting SRC_URI=hg://host.name/path;module=modulename14:26
rburtonand shuffles that into the relevant command line14:26
rburtonkhem: thanks14:29
*** silviof <silviof!~silviof@unaffiliated/silviof> has quit IRC14:29
armpitrburton,   9383 sure14:29
*** yann <yann!~yann@85-171-21-92.rev.numericable.fr> has quit IRC14:33
*** silviof <silviof!~silviof@unaffiliated/silviof> has joined #yocto14:35
rburtonarmpit: can  you take ownership then, thanks14:39
*** csanchezdll <csanchezdll!~user@galileo.kdpof.com> has left #yocto14:41
*** TobSnyder <TobSnyder!~schneider@ip9234b44d.dynamic.kabel-deutschland.de> has quit IRC14:45
*** yann <yann!~yann@85-171-21-92.rev.numericable.fr> has joined #yocto14:45
*** ntl <ntl!~nathanl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has quit IRC14:47
*** aragua_ <aragua_!~aragua@232-28-190-109.dsl.ovh.fr> has quit IRC14:48
*** billr <billr!~wcrandle@> has joined #yocto14:50
*** toscalix <toscalix!~toscalix@> has joined #yocto14:50
*** aragua_ <aragua_!~aragua@232-28-190-109.dsl.ovh.fr> has joined #yocto14:50
*** benjamirc <benjamirc!~besquive@> has quit IRC15:05
*** evanmeagher <evanmeagher!~MongooseW@c-73-71-33-109.hsd1.ca.comcast.net> has joined #yocto15:06
*** lewiatan <lewiatan!~piotr@b2b-94-79-174-114.unitymedia.biz> has quit IRC15:07
*** qt-x <qt-x!~Thunderbi@> has quit IRC15:09
simonlI'm trying to make a clean build (ie new build directory) of daisy. However my host system uses arch which has long since switched to gcc 5.x and then 6.x as the default compiler. Can I tell poky to use say, gcc-4.9 instead?15:15
simonlI've tried symlink-hacking gcc to be 4.9, but that's not enough, likely because I still get newer versions of other parts like the standard library(?)15:16
*** dmoseley <dmoseley!~dmoseley@6532158hfc157.tampabay.res.rr.com> has joined #yocto15:17
sveinseIs it possible to run bitbake without the "interactivity" where it updates the console, but rather print every task it executes?15:18
rburtonpipe to cat is the easy way15:20
rburtonsimonl: set BUILD_CC etc15:21
rburtonsimonl: http://pastebin.com/hjJnvGBU <— from my local.conf from when i was testing gcc5 on my host15:21
simonlrburton: awesome, I'll give that a try!15:22
sveinseI'm finally getting this compilation going!15:26
*** tjamison <tjamison!~tjamison@> has joined #yocto15:26
sveinseHow do you access host tools? Use inherit for them?15:27
sveinseAnyone with any example references for it?15:27
rburtonsveinse: just use them15:28
rburtonthey're still on the path15:28
sveinseApparently not: protoc command not found15:29
rburtonwhere is it on your host?15:29
rburtonpath does get reset a bit15:29
rburtonif thats protobufs then theres a recipe in meta-oe you can depend on to built the binaries natively15:31
*** maxin <maxin!~maxin@37-219-225-102.nat.bb.dnainternet.fi> has left #yocto15:32
sveinserburton, yes, It's in meta-oe/recipes-devtools/protobuf/, so I assume it hasn't been built yet. Hence I lack a dependency or something?15:33
sveinserburton: thanks!15:34
*** pohly <pohly!~pohly@host-091-097-029-052.ewe-ip-backbone.de> has quit IRC15:35
simark1rburton: isn't it protobuf-compiler-native?15:36
simark1In order to get protoc15:36
*** _pacopedraza <_pacopedraza!c0373628@gateway/web/freenode/ip.> has joined #yocto15:36
*** pohly <pohly!~pohly@dyndsl-178-142-071-142.ewe-ip-backbone.de> has joined #yocto15:36
rburtonyeah maybe :)15:36
rburtonnever used it15:36
simark1sveinse: ^15:37
simark1I recetnly spent one day fighting with that until I realized it was in protobuf-compiler :)15:37
*** benjamirc <benjamirc!besquive@nat/intel/x-hoglzstviwnzkjof> has joined #yocto15:38
*** vdehors_ <vdehors_!~vdehors@bob75-2-81-56-46-209.fbx.proxad.net> has joined #yocto15:38
sveinseDo I need to do something when I change DEPENDS statements? It seems none of the above proposals work15:40
*** frsc <frsc!~frsc@> has quit IRC15:41
*** joeythesaint <joeythesaint!~joe@vegas.deserted.net> has quit IRC15:41
*** vdehors <vdehors!~vdehors@> has quit IRC15:42
billrsimonl: if you want to build daisy with gcc5, I do have a set of patches that will let you do that.15:43
*** ndec_ <ndec_!~ndec@linaro/ndec> has quit IRC15:48
sveinseApparently I need to run something for it to parse DEPENDS changes. I'm running toaster, and it shows no depends on other packages15:50
*** toscalix <toscalix!~toscalix@> has quit IRC15:50
*** ndec <ndec!~ndec@linaro/ndec> has joined #yocto15:51
learnerHow can I restrict a native recipe so that it can be only build on x64 machines?15:51
*** _pacopedraza <_pacopedraza!c0373628@gateway/web/freenode/ip.> has quit IRC15:52
learnerI was told to use COMPATIBLE_MACHINE some days ago, but all the examples I see use that for restricting the TARGET machine15:52
*** townxelliot <townxelliot!~ell@> has quit IRC15:55
*** aragua_ <aragua_!~aragua@232-28-190-109.dsl.ovh.fr> has quit IRC15:56
simonlbillr: that'd be nice!15:57
sveinsesimark1: ^ I can't get it to build protoc...15:57
*** ntl <ntl!~nathanl@cpe-24-242-74-130.austin.res.rr.com> has joined #yocto15:58
billrsimonl: send me a PM with your email address15:58
rburtonlearner: what if the build host is something else?15:59
*** townxelliot <townxelliot!~ell@> has joined #yocto15:59
sveinsewhen do you use DEPENDS="something" and DEPENDS+="something" ?16:00
sveinseHow do you know which one to use?16:00
*** mckoan is now known as mckoan|away16:01
*** evanmeagher <evanmeagher!~MongooseW@c-73-71-33-109.hsd1.ca.comcast.net> has quit IRC16:04
sveinseIf I run bitbake protobuf-native manually first, then my build continues. Its apparently that my depends haven't been reread16:05
*** fl0v01 <fl0v01!~fvo@pD9F6ACA5.dip0.t-ipconnect.de> has quit IRC16:08
rburtonare you using memory-resident bitbake?16:09
*** rajm <rajm!~robertmar@cpc14-macc3-2-0-cust149.1-3.cable.virginm.net> has quit IRC16:10
*** evanmeagher <evanmeagher!~MongooseW@c-73-71-33-109.hsd1.ca.comcast.net> has joined #yocto16:11
learnerrburton: just refuse to build, show an error16:12
learnerthe recipe won't work in no x64 machines16:12
*** JaMa <JaMa!~martin@ip-89-176-104-169.net.upcbroadband.cz> has quit IRC16:13
neverpanicHow do I modify $PATH on a per-task basis? I'd like to write a function that adds entries to $PATH depending on what BB_TASKDEPDATA contains.16:14
rburtonneverpanic: not sure you can16:15
neverpanicyeah, that's what I feared16:15
neverpanicUnfortunately the other solution would be building a native sysroot for each task with its dependencies, and that's also pretty cumbersome16:16
kergothwe really should implement support for per-recipe sysroots based on its deps one of these days, it should be doable16:18
kergothbut in theory the PATH thing should be possible, i think a prefunc could modify the env and affect the main task.. not sure, though16:18
kergothalso i haven't had my caffeine yet, so ..16:18
neverpanicThe problem with per-recipe native sysroots is that you configured that piece of software for a certain prefix, so you cannot easily move it16:19
neverpanicExcept using tricks such as overlayfs or mount namespaces of course, but I wanted to avoid those for now.16:19
kergothwe relocate native sysroot content all the time, just when the sstate archive is created/extracted, via sed replacements. not pretty, but..16:19
neverpanicHm, maybe I can do that as well for the native sysroot and hardlink for the target sysroot then.16:20
sveinsewe do that in our current custom build server (in which we are replacing with Yocto, btw). We did it by massively deleting, and redeploying the sysroot foreach package.16:20
sveinseIts great for the security of the packages (control leakage and such), but the devs hate it, since its consumes more time16:21
neverpanicWell, I have a working proof of concept using overlayfs in a mount namespace, but that only works with user namespaces and on distributions that allow overlayfs in mount namespaces (i.e. recent Ubuntu)16:22
neverpanicI was trying to get this implemented in a way that could be upstreamable16:22
*** RzR <RzR!~RzR@unaffiliated/rzr> has joined #yocto16:28
*** t0mmy <t0mmy!~tprrt@> has quit IRC16:30
*** evanmeagher <evanmeagher!~MongooseW@c-73-71-33-109.hsd1.ca.comcast.net> has quit IRC16:32
*** billr <billr!~wcrandle@> has quit IRC16:34
*** belen1 <belen1!~Adium@> has quit IRC16:36
*** learner <learner!d997f20f@gateway/web/freenode/ip.> has quit IRC16:36
khemhalstead: https://gist.github.com/kraj/6caf2a31ff4701c784c2337b4cf0669f16:41
khemhalfhalo: I am trying to use pwclient16:41
khemit used to work fine with old instance16:41
*** jbrianceau is now known as jbrianceau_away16:47
*** mortderire <mortderire!~rkinsell@> has quit IRC16:48
halsteadLooking khem.16:51
halsteadkhem, Can you update your .pwclientrc to point at https://patchwork.openembedded.org/xmlrpc/ ?16:52
halsteadAnd try again?16:52
*** billr <billr!~wcrandle@> has joined #yocto16:53
*** tlwoerner <tlwoerner!~trevor@unaffiliated/tlwoerner> has joined #yocto16:57
*** dreyna <dreyna!~dreyna@unknown-216-200.windriver.com> has joined #yocto16:57
*** belen <belen!~Adium@> has joined #yocto16:57
*** dmoseley <dmoseley!~dmoseley@6532158hfc157.tampabay.res.rr.com> has quit IRC16:59
khemhalstead: ok so I had http so changing to https helped17:00
sveinsehmm. My qt app package fails on missing linux_types.h17:00
*** armpit <armpit!~akuster@2601:202:4001:9ea0:c008:4767:f9d2:dea7> has quit IRC17:01
*** JaMa <JaMa!~martin@ip-89-176-104-169.net.upcbroadband.cz> has joined #yocto17:05
rburtonsveinse: its probably assuming that it can look in /usr for something17:06
sveinseHmm, is PARALLEL_MAKE="" in a recipe global? If yes, would PARALLEL_MAKE_mypkg="" work?17:08
rburtonin a recipe, everything is scoped to the recipe17:08
*** Nilesh_ <Nilesh_!uid116340@gateway/web/irccloud.com/x-zbvqjaojindmufzs> has joined #yocto17:09
rburtonbasically the data is a CoW database which is populated with the distro and local conf files, and then cloned for each recipe17:09
rburtonso you can't impact other recipes from inside a recipe17:09
sveinserburton: ok. I got the include resolved. The only thing remaining is the dependency on protobuf which apparently does not work17:09
sveinseI can call bitbake protobuf-native, and things work out. But it does not build protobuf-native, if I mention it in DEPENDS="protobuf-native"17:10
sveinse...or protobuf-compiler-native as previously suggested17:11
sveinseHow can I debug a recipes depends?17:11
sveinseI seriously don't understand how this depend system in yocto works17:12
khemsveinse: bitbake -e <recipe> | grep "^DEPENDS"17:13
sveinsekhem: ok, so it sais protobuf-native. How can I check if this package has been built?17:14
khemis protobuf-native providing some tools which will generate linux_types.h17:15
sveinsekhem: No, that issue is resolved :D17:16
khemok so it the dependency on protobuf then protobuf-native wont help17:17
khemif you are using some libs and APIs from protobuf then you have to depend on protobuf17:17
khemnot on native version of protobuf which is for build host not target host17:17
sveinsekhem: if I manually run bitbake protobuf-native prior to my build, then my recipe build finds protoc and continues17:18
*** belen <belen!~Adium@> has quit IRC17:18
sveinseHence, I think I need to depend on protobuf-native17:18
*** evanmeagher <evanmeagher!~MongooseW@> has joined #yocto17:20
*** joshuagl_ <joshuagl_!~joshuagl@> has quit IRC17:21
sveinsesimark1 suggested earlier that I need to depend on protobuf-compiler-native, yet it does not remedy the case. Nor does bitbake know about any recipes with that name17:22
sveinseIsn't the purpose of DEPENDS=xyz to run the full bitbake xyz process prior to its own compile?17:23
kergothspecifically, DEPENDS=xyz means the do_populate_sysroot task of xyz will be run before do_configure in the recipe with the DEPENDS17:24
sveinseyes, and I assume do_populate_sysroot on a native package implies installing the files into its sysroot, right? So why isn't it when I write DEPENDS="protobuf-native", when running bitbake protobuf-native first works?17:26
*** wmryrx <wmryrx!0cc9f26a@gateway/web/freenode/ip.> has joined #yocto17:26
wmryrxhey, does anyone have experience with the device tree changes needed to bring up a camera?17:27
kergothsveinse: no idea, it works fine for every other recipe we have17:29
kergothyou must be doing something wrong17:29
kergothmight want to pastebin the recipe for us to examine17:29
sveinsekergoth: Not much to look at, the only thing added is this DEPENDS = "protobuf-native" to this: https://bpaste.net/show/f4899bb3a29c17:31
*** townxelliot <townxelliot!~ell@> has quit IRC17:32
sveinsekergoth: The qt app source make use of protoc17:32
*** obsrwr_ <obsrwr_!~obsrwr@> has joined #yocto17:32
sveinse(No wonder our consultants can charge us a lot for Yocto customization :P )17:33
*** fledermaus <fledermaus!~vivek@2a00:1098:5:0:5d4f:49fc:3e09:693> has quit IRC17:34
*** fledermaus <fledermaus!~vivek@2a00:1098:5:0:5d4f:49fc:3e09:693> has joined #yocto17:35
sveinseThis has been my very first day with Yocto, and I have have a lot to learn, that is for sure. Lots of getting used to, especially with logging/output. And this elusive dependency system and how to debug it17:40
sveinserburton, thanks for all your help today. It has been very valuable and I really appreciate it.17:41
*** paulg is now known as paulg_17:49
*** wmryrx <wmryrx!0cc9f26a@gateway/web/freenode/ip.> has quit IRC17:52
*** wrmyrx <wrmyrx!0cc9f26a@gateway/web/freenode/ip.> has joined #yocto17:53
*** evanmeagher <evanmeagher!~MongooseW@> has quit IRC17:55
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has quit IRC17:57
wrmyrxif i'm trying to configure my device tree to enable a serial camera - do i need to make a patch like this: http://www.xilka.com/kernel/3/3.14/3.14.30/source/Linux-3.14.29-ov5647-20150126.patch which adds a specific entry for that camera into the device tree?18:01
sveinseWhen we build our Qt application under a Yocto SDK, we set an environment file which, amongst many, defines SDKTARGETSYSROOT. How do I set an equivalent set of variables from within a recipe?18:10
sveinseSpecifically, is there an environment variable the Qt app can use to test that it is compiling under Yocto?18:11
khemsveinse: ok so that answers my first question. Which is you are using protoc tool from native package18:17
*** paulg <paulg!~paulg@OTWAON23-3096772825.sdsl.bell.ca> has joined #yocto18:18
khemnow can you change DEPENDS = "xxx" to DEPEND += "xxx"18:18
sveinsetypo, thanks. typo or subtle difference?18:19
kergothtypo, DEPENDS is correct18:19
khemI am just thinking if there are more dependencies18:19
khemoh yes DEPENDS18:20
sveinseI've installed protobuf-native manually, so I won't know until I remove protobuf. I can erase it by running bitbake -c cleanall protobuf-native, right?18:21
khemthen do bitbake your-recipe18:23
sveinsekhem: Nope, did not trigger build of protobuf-native18:26
*** aehs29 <aehs29!~aehernan@> has left #yocto18:28
khemcan you show your recipe ?18:29
sveinsekhem: https://bpaste.net/show/3412c6c5b11718:32
sveinseIts highly work in progress, so you'll parden me for the do_configure() mess. I'm working on how to pass options to qmake18:32
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-vopmtgavjqfyfjwz> has quit IRC18:49
*** joeythesaint <joeythesaint!~joe@vegas.deserted.net> has joined #yocto18:49
neverpanicsveinse: EXTRA_QMAKEVARS_{PRE,POST}, iirc18:50
sveinseneverpanic: Worked brilliantly, thanks18:53
sveinseOne catch thou: Qmake needs a CONFIG statement which is based on the combination of two recipe vars. I need some lookuptable/logic to find the correct value to give to qmake18:55
sveinseCan I run a conditional script in recipe setting a var based on that script?18:55
*** anselmolsm <anselmolsm!~anselmols@> has quit IRC18:55
neverpanicYou can even do it in a variable: ${@python code that returns the value you need}18:56
sveinseCan I do something like this: https://bpaste.net/show/887b670c7d9318:58
sveinseneverpanic: ok, does the py script need to be a py oneliner?18:58
neverpanice.g. https://p.dnnr.de/odn8gg98Ko_98m7n18:58
sveinseneverpanic: right, brilliant, thanks18:59
neverpanicbtw, how do you determine that protobuf-native isn't being built? If you have built it previously it will just be extracted if you need it, it will likely not be recompiled.19:00
sveinseneverpanic: I haven't. Its just not available in path for the qt app I'm compiling19:01
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto19:02
*** evanmeagher <evanmeagher!~MongooseW@> has joined #yocto19:03
neverpanicsveinse: check $BUILDDIR/tmp/sysroots/x86_64-linux/usr/bin (assuming you're on a 64bit build machine)19:03
sveinseneverpanic: I have. I test it with find . -name protoc from the top of the build19:04
sveinseSo even broader search19:04
*** josep_ <josep_!~josep@c-3b1ae455.010-118-73746f7.cust.bredbandsbolaget.se> has joined #yocto19:05
*** fledermaus <fledermaus!~vivek@2a00:1098:5:0:5d4f:49fc:3e09:693> has quit IRC19:05
neverpanichow do you trigger the build of your recipe then?19:08
rburtonjust built protobuf-native and i have ./x86_64-linux/usr/bin/protoc in my sysroots19:08
neverpanicAlso, LIC_FILES_CHKSUM isn't necessary if you set LICENSE = "CLOSED"19:08
sveinseneverpanic: the CLOSED is just a temporary means, it will be replace by the actual license19:08
rburtonso provide evidence that it can't be found, instead of just saying so19:09
rburtonie the shell output and evidence that the build isn't just trying to run /usr/bin/protoc19:09
*** Nilesh_ <Nilesh_!uid116340@gateway/web/irccloud.com/x-zbvqjaojindmufzs> has quit IRC19:17
*** yann <yann!~yann@85-171-21-92.rev.numericable.fr> has quit IRC19:18
*** crankslider <crankslider!~slidercra@unaffiliated/slidercrank> has joined #yocto19:18
sveinserburton: https://bpaste.net/show/8f2715df920819:26
*** obsrwr <obsrwr!~obsrwr@> has joined #yocto19:26
*** pohly <pohly!~pohly@dyndsl-178-142-071-142.ewe-ip-backbone.de> has quit IRC19:28
*** obsrwr_ <obsrwr_!~obsrwr@> has quit IRC19:30
neverpanicsveinse: whats's bitbake -e sp | grep -E ^DEPENDS=19:30
rburtonyeah i was thinking "i bet qmake5 is stupid"19:31
*** yann <yann!~yann@85-171-21-92.rev.numericable.fr> has joined #yocto19:32
sveinse(can I run bitbake -e while another build is running?)19:32
neverpanicno :/19:32
rburtonwell you can if you're using memres bitbake, but don't do that yet - it's not ready19:33
sveinseI'll wait for this build to finish :)19:33
rburtoncurrently suspicious about the makefile19:34
rburtonlike is it doing something stupid like resetting PATH19:34
neverpanicyeah, the qmake5.bbclasses I can see all use DEPENDS_prepend, so they should be fine19:34
sveinserburton: Then you should never get to know qmake. Whoa, I loathe that tool19:34
sveinseThis is going to be a manual typeover: DEPENDS="qtbase-native virtual/arm-poky-linux-gnueabi-gcc virtual/arm-poky-linux-gnueabi-compilerlibs protobuf-native"19:36
sveinse^ neverpanic19:37
neverpaniclooks sane to me19:37
sveinseyes, it does19:38
sveinsewell, I'll leave this for now. its late19:38
sveinseThank you very much, both of you!19:38
rburtonsveinse: considered porting to cmake? :)19:40
sveinserburton: Not my call. I'm not part of the Qt team.19:41
sveinseBut it looks to me that qmake is working fine. Its the fact that protoc isn't installed into the x86_64 sysroot even when I specify it with DEPENDS that is the cause for this19:42
rburtontotally works for me, so <shrug> no idea19:42
rburtonpresumably this is source you can't share?19:43
*** belen <belen!~Adium@> has joined #yocto19:43
*** aehs29 <aehs29!~aehernan@> has joined #yocto19:43
sveinsenot all of it, no. not yet at least19:44
sveinseand I'm fearing some intermixing with the imx BSP machine setup that cause some ill effect with protoc.19:45
rburtonwell, one solution is MACHINE=qemux86 bitbake myrecipe, and see what happens19:45
sveinseyes, that was the plan. (going to be exciting to see how qt5 makes it out there)19:46
*** ntl <ntl!~nathanl@cpe-24-242-74-130.austin.res.rr.com> has quit IRC19:48
*** belen <belen!~Adium@> has quit IRC19:50
*** sveinse <sveinse!~chatzilla@> has quit IRC19:56
*** ziggo_ <ziggo_!~ziggo@p2003006CCD49010036363BFFFED11AA2.dip0.t-ipconnect.de> has joined #yocto19:59
*** bluelightning <bluelightning!~paul@> has joined #yocto20:01
*** bluelightning <bluelightning!~paul@> has quit IRC20:01
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto20:01
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has quit IRC20:11
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has joined #yocto20:11
*** radzy <radzy!~radzy@unknown-216-192.windriver.com> has quit IRC20:23
*** ntl <ntl!~nathanl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has joined #yocto20:28
*** pohly <pohly!~pohly@dyndsl-178-142-071-142.ewe-ip-backbone.de> has joined #yocto20:28
*** radzy <radzy!~radzy@unknown-216-87.windriver.com> has joined #yocto20:29
*** armpit <armpit!~akuster@> has joined #yocto20:32
*** JaMa <JaMa!~martin@ip-89-176-104-169.net.upcbroadband.cz> has quit IRC20:47
*** obsrwr <obsrwr!~obsrwr@> has quit IRC20:48
*** __karthik <__karthik!~karthik@> has quit IRC20:51
*** __karthik <__karthik!~karthik@> has joined #yocto20:51
*** sgw_ <sgw_!~sgw_@> has quit IRC20:54
*** pohly <pohly!~pohly@dyndsl-178-142-071-142.ewe-ip-backbone.de> has quit IRC21:04
*** paulg <paulg!~paulg@OTWAON23-3096772825.sdsl.bell.ca> has quit IRC21:08
*** sgw_ <sgw_!~sgw_@> has joined #yocto21:10
*** benjamirc <benjamirc!besquive@nat/intel/x-hoglzstviwnzkjof> has quit IRC21:18
*** berton <berton!~fabio@> has quit IRC21:23
*** kad_ <kad_!~kad@dsl-hkibrasgw3-54fb77-110.dhcp.inet.fi> has quit IRC21:26
*** kad <kad!~kad@unaffiliated/kad> has joined #yocto21:27
*** rob_w <rob_w!~rob@unaffiliated/rob-w/x-1112029> has quit IRC21:29
*** paulg <paulg!~paulg@198-84-239-75.cpe.teksavvy.com> has joined #yocto21:30
*** townxelliot <townxelliot!~ell@> has joined #yocto21:36
*** evanmeagher <evanmeagher!~MongooseW@> has quit IRC21:42
*** evanmeagher <evanmeagher!~MongooseW@> has joined #yocto21:42
*** bottazzini <bottazzini!~realBigfo@> has quit IRC21:45
*** ziggo_ <ziggo_!~ziggo@p2003006CCD49010036363BFFFED11AA2.dip0.t-ipconnect.de> has quit IRC21:48
*** megha_dey <megha_dey!meghadey@nat/intel/x-esgrgyesbwawrzfv> has joined #yocto21:59
megha_deyHi I am trying to use plymouth to display boot screen using yocto... but am not able to do so. Has anyone tried incorporating plymouth into yocto and successfully booted a graphical splash screen?22:00
*** fmeerkoetter <fmeerkoetter!~quassel@service.basyskom.com> has quit IRC22:01
*** bfederau <bfederau!~quassel@service.basyskom.com> has quit IRC22:01
*** bfederau <bfederau!~quassel@service.basyskom.com> has joined #yocto22:01
*** fmeerkoetter <fmeerkoetter!~quassel@service.basyskom.com> has joined #yocto22:01
*** Biliogadafr <Biliogadafr!~pin@nat3-minsk-pool-46-53-183-225.telecom.by> has quit IRC22:02
*** mortderire <mortderire!rkinsell@nat/intel/x-niqdaeaehmzbybzv> has joined #yocto22:21
*** mortderire <mortderire!rkinsell@nat/intel/x-niqdaeaehmzbybzv> has quit IRC22:23
*** aehs29 <aehs29!~aehernan@> has left #yocto22:30
*** void-dev <void-dev!FqiedjcsNV@monoceres.uberspace.de> has quit IRC22:30
*** jwessel <jwessel!~jwessel@> has quit IRC22:33
*** zeddii_home <zeddii_home!~zeddii_ho@CPEe8de27b71faa-CMbcc810032faf.cpe.net.cable.rogers.com> has quit IRC22:34
*** paulg_ <paulg_!~paulg@> has quit IRC22:35
*** zeddii <zeddii!~bruce@> has quit IRC22:36
*** zeddii <zeddii!~bruce@> has joined #yocto22:36
*** lexano <lexano!~lexano@CPEa021b7ac59c9-CMf0f249028110.cpe.net.cable.rogers.com> has quit IRC22:36
*** lexano <lexano!~lexano@CPEa021b7ac59c9-CMf0f249028110.cpe.net.cable.rogers.com> has joined #yocto22:37
*** paulg_ <paulg_!~paulg@> has joined #yocto22:37
*** jwessel <jwessel!~jwessel@> has joined #yocto22:37
*** rburton <rburton!~Adium@home.burtonini.com> has quit IRC22:42
*** nighty <nighty!~nighty@s229123.ppp.asahi-net.or.jp> has quit IRC22:43
*** megha_dey <megha_dey!meghadey@nat/intel/x-esgrgyesbwawrzfv> has quit IRC22:48
*** megha_dey <megha_dey!meghadey@nat/intel/x-zsrxziytclzdpesn> has joined #yocto22:49
*** igor2 <igor2!~igor@> has quit IRC22:51
*** lamego <lamego!jose@nat/intel/x-xntfpwjklzfedxsa> has quit IRC22:57
*** evanmeagher <evanmeagher!~MongooseW@> has quit IRC23:02
*** sameo <sameo!~samuel@> has quit IRC23:02
*** evanmeag_ <evanmeag_!~MongooseW@> has joined #yocto23:02
*** Biliogadafr <Biliogadafr!~pin@nat3-minsk-pool-46-53-183-225.telecom.by> has joined #yocto23:05
*** Biliogadafr <Biliogadafr!~pin@nat3-minsk-pool-46-53-183-225.telecom.by> has quit IRC23:05
*** Biliogadafr <Biliogadafr!~pin@nat3-minsk-pool-46-53-183-225.telecom.by> has joined #yocto23:07
*** Biliogadafr <Biliogadafr!~pin@nat3-minsk-pool-46-53-183-225.telecom.by> has quit IRC23:15
khemmegha_dey: are you using systemd ?23:16
khemmegha_dey: its not integrated with sysvinit but should work out of box with systemd as init manager23:17
*** agust <agust!~agust@p4FCB5814.dip0.t-ipconnect.de> has quit IRC23:22
*** dv__ <dv__!~quassel@62-178-118-86.cable.dynamic.surfer.at> has joined #yocto23:22
*** dv_ <dv_!~quassel@> has quit IRC23:22
*** townxelliot <townxelliot!~ell@> has quit IRC23:48

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!