| *** SoylentYellow <SoylentYellow!~SoylentYe@209-234-137-234.static.twtelecom.net> has quit IRC | 00:05 | |
| *** anselmolsm <anselmolsm!~anselmols@192.55.54.36> has joined #yocto | 00:09 | |
| *** behanw <behanw!~behanw@2001:470:b26c:0:68ce:c64e:c7a1:795a> has quit IRC | 00:27 | |
| *** sjolley <sjolley!~sjolley@134.134.137.71> has joined #yocto | 00:31 | |
| *** benjamirc <benjamirc!~besquive@134.134.137.71> has quit IRC | 00:50 | |
| *** paulg <paulg!~paulg@71-19-175-186.dedicated.allstream.net> has quit IRC | 01:00 | |
| *** benjamirc <benjamirc!besquive@nat/intel/x-yqlnabqxwmxkaxlf> has joined #yocto | 01:08 | |
| *** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has joined #yocto | 01:14 | |
| *** pidge <pidge!~pidge@2a02:8084:0:3000:ddd2:556c:d35a:c5cc> has quit IRC | 01:17 | |
| *** vmesons <vmesons!~rmacleod@24-212-184-107.cable.teksavvy.com> has quit IRC | 01:18 | |
| *** paulg <paulg!~paul@24-246-6-178.cable.teksavvy.com> has joined #yocto | 01:27 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC | 01:35 | |
| *** Jackie_huang <Jackie_huang!~quassel@106.120.101.38> has quit IRC | 01:35 | |
| *** Jackie <Jackie!~quassel@106.120.101.38> has joined #yocto | 01:37 | |
| *** Jackie is now known as Guest24743 | 01:37 | |
| *** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto | 01:54 | |
| *** wenzong <wenzong!~wfan@106.120.101.38> has quit IRC | 01:54 | |
| *** wenzong <wenzong!~wfan@106.120.101.38> has joined #yocto | 01:55 | |
| *** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC | 01:58 | |
| *** staylor <staylor!~staylor@184.68.113.94> has joined #yocto | 02:15 | |
| *** pidge <pidge!~pidge@2a02:8084:0:3000:c8fa:9120:d0d0:542a> has joined #yocto | 02:30 | |
| *** dryawgmoth <dryawgmoth!~varx@wsip-174-66-84-98.oc.oc.cox.net> has quit IRC | 02:32 | |
| *** pidge <pidge!~pidge@2a02:8084:0:3000:c8fa:9120:d0d0:542a> has quit IRC | 02:44 | |
| *** marcosps <marcosps!~Thunderbi@177.132.130.138> has quit IRC | 03:03 | |
| *** OutOfNoWhere <OutOfNoWhere!~rpb@199.68.195.101> has quit IRC | 03:09 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto | 03:09 | |
| *** staylor <staylor!~staylor@184.68.113.94> has quit IRC | 03:15 | |
| *** RP <RP!~richard@200.52.194.114> has joined #yocto | 03:19 | |
| *** luyu__ <luyu__!luyu@nat/intel/x-txhirlymneyfuhpq> has quit IRC | 03:48 | |
| *** luyu__ <luyu__!luyu@nat/intel/x-jcvmbpmjzjphmnmc> has joined #yocto | 03:49 | |
| *** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto | 03:54 | |
| *** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC | 03:59 | |
| *** SoylentYellow <SoylentYellow!~SoylentYe@130.164.63.74> has joined #yocto | 04:00 | |
| *** TobSnyder <TobSnyder!~schneider@ip923450f2.dynamic.kabel-deutschland.de> has joined #yocto | 04:57 | |
| *** ddalex <ddalex!~ddalex@233.128.113.87.dyn.plus.net> has joined #yocto | 05:07 | |
| *** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has quit IRC | 05:09 | |
| *** ddalex <ddalex!~ddalex@233.128.113.87.dyn.plus.net> has quit IRC | 05:16 | |
| *** parrot1 <parrot1!~chankitx@192.198.146.171> has joined #yocto | 05:26 | |
| *** lyang0 <lyang0!~lyang001@106.120.101.38> has quit IRC | 05:27 | |
| parrot1 | hello, so if I find a file under sysroots/<recipes-package>/ , can I expect to find that file under the resulting final image? | 05:28 |
|---|---|---|
| parrot1 | for some reason, i915_dri.so is missing from the final image although I can clearly see the library in /tmp/sysroots/intel-corei7-64 | 05:29 |
| kergoth | nope. sysroots are directory hierarchies which hold files for recipes to share with one another, e.g. libs an dheaders to satisfy dependencies | 05:29 |
| kergoth | recipes can emit any number of binary packages, whereas sysroots are monolithic, everything the recipe installed to certain paths | 05:29 |
| kergoth | packages listed in IMAGE_INSTALL in the image are installed into the image | 05:30 |
| kergoth | see the yocto documentation on that | 05:30 |
| parrot1 | ok. So if I want to see the list of packages installed i can simply refer to the manifest file right? | 05:32 |
| *** drou <drou!c32a382b@gateway/web/freenode/ip.195.42.56.43> has joined #yocto | 05:35 | |
| drou | hi guys | 05:35 |
| drou | i'd like to have my keyboard layout as azerty & qwerty but i'm not able to do it. | 05:39 |
| drou | Here is what I have when I ran the bitbake -e command : IMAGE_LINGUAS="fr-fr en-us" | 05:39 |
| drou | not sure if it's the appropriate variable | 05:40 |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has quit IRC | 05:42 | |
| *** Guest99907 <Guest99907!~dennis@116.228.88.131> has quit IRC | 05:48 | |
| *** Guest76860 <Guest76860!~dennis@116.228.88.131> has joined #yocto | 05:51 | |
| *** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto | 05:55 | |
| *** Guest76860 <Guest76860!~dennis@116.228.88.131> has quit IRC | 05:56 | |
| *** dlan_ <dlan_!~dennis@gentoo/developer/dlan> has joined #yocto | 05:57 | |
| *** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC | 06:00 | |
| *** pohly <pohly!~pohly@p5DE8CA2B.dip0.t-ipconnect.de> has joined #yocto | 06:04 | |
| *** TobSnyder1 <TobSnyder1!~schneider@ip923450f2.dynamic.kabel-deutschland.de> has joined #yocto | 06:33 | |
| *** TobSnyder <TobSnyder!~schneider@ip923450f2.dynamic.kabel-deutschland.de> has quit IRC | 06:34 | |
| *** Biliogadafr <Biliogadafr!~User@37.44.102.241> has joined #yocto | 06:45 | |
| *** paulg <paulg!~paul@24-246-6-178.cable.teksavvy.com> has quit IRC | 06:47 | |
| *** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-csaomwrsxzyyvduh> has joined #yocto | 06:51 | |
| *** jbrianceau_away is now known as jbrianceau | 06:53 | |
| *** jku <jku!jku@nat/intel/x-ihxhtictjkommohv> has joined #yocto | 07:00 | |
| *** ant_work <ant_work!~ant__@host222-188-static.61-79-b.business.telecomitalia.it> has joined #yocto | 07:02 | |
| *** dieter_ <dieter_!~quassel@p5795C37F.dip0.t-ipconnect.de> has joined #yocto | 07:03 | |
| *** jku <jku!jku@nat/intel/x-ihxhtictjkommohv> has left #yocto | 07:08 | |
| *** jku <jku!jku@nat/intel/x-eosnuowfmemkmfsz> has joined #yocto | 07:10 | |
| *** hamis <hamis!~irfan@110.93.212.98> has joined #yocto | 07:10 | |
| *** ant_work <ant_work!~ant__@host222-188-static.61-79-b.business.telecomitalia.it> has quit IRC | 07:11 | |
| *** ant_work <ant_work!~ant__@host222-188-static.61-79-b.business.telecomitalia.it> has joined #yocto | 07:11 | |
| *** miandonmenmian_ <miandonmenmian_!~miandonme@95-170-82-196.colo.transip.net> has joined #yocto | 07:14 | |
| *** ant_work <ant_work!~ant__@host222-188-static.61-79-b.business.telecomitalia.it> has quit IRC | 07:31 | |
| *** drou <drou!c32a382b@gateway/web/freenode/ip.195.42.56.43> has quit IRC | 07:38 | |
| *** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto | 07:43 | |
| *** ericst <ericst!~ericst@ceres.ukito.net> has quit IRC | 07:49 | |
| *** marek__ <marek__!~marek@81.89.61.168.vnet.sk> has joined #yocto | 07:50 | |
| *** psnsilva <psnsilva!~psnsilva@193-126-29-154.net.novis.pt> has joined #yocto | 07:52 | |
| *** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has joined #yocto | 07:56 | |
| *** likewise <likewise!~likewise@178-85-26-82.dynamic.upc.nl> has quit IRC | 08:00 | |
| *** florian_kc is now known as florian | 08:01 | |
| *** bluelightning <bluelightning!~paul@83.217.123.106> has joined #yocto | 08:05 | |
| *** bluelightning <bluelightning!~paul@83.217.123.106> has quit IRC | 08:05 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 08:05 | |
| bluelightning | morning all | 08:07 |
| miandonmenmian_ | morning bluelightning | 08:07 |
| *** mckoan|away <mckoan|away!~marco@unaffiliated/mckoan> has quit IRC | 08:11 | |
| marek__ | hi all | 08:11 |
| *** mckoan|away <mckoan|away!~marco@host56-7-static.30-87-b.business.telecomitalia.it> has joined #yocto | 08:11 | |
| marek__ | is there some example hot to add external binary kernel module to final image? | 08:12 |
| marek__ | *how | 08:12 |
| *** soderstrom <soderstrom!~soderstro@81.216.59.226> has joined #yocto | 08:14 | |
| *** lordzen <lordzen!~lordzen@93-51-177-218.ip268.fastwebnet.it> has joined #yocto | 08:15 | |
| bluelightning | marek__: binary, no, not really... however it would be a fairly straightforward recipe, just copy the files into the appropriate place and ensure they get packaged | 08:15 |
| marek__ | yes this was also my idea but what if kernel version will change | 08:15 |
| marek__ | bluelightning: I want to keep /lib/modules/xxx/ to be extracted somehow | 08:15 |
| *** soderstrom <soderstrom!~soderstro@81.216.59.226> has quit IRC | 08:16 | |
| *** soderstrom <soderstrom!~soderstro@81.216.59.226> has joined #yocto | 08:16 | |
| *** jonathanmaw <jonathanmaw!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has joined #yocto | 08:17 | |
| *** psnsilva <psnsilva!~psnsilva@193-126-29-154.net.novis.pt> has quit IRC | 08:18 | |
| bluelightning | marek__: your recipe can inherit linux-kernel-base then set KERNEL_VERSION = "${@get_kernelversion_file("${STAGING_KERNEL_BUILDDIR}")}" and then install the files within do install to ${D}/lib/modules/${KERNEL_VERSION} | 08:20 |
| marek__ | bluelightning: many thanks | 08:20 |
| bluelightning | oh, you should also have DEPENDS = "virtual/kernel" | 08:21 |
| miandonmenmian_ | how can I change this line to use http protocol? : SRC_URI = "git://github.com/mygit/mygit.git;branch=2" | 08:21 |
| bluelightning | miandonmenmian_: add ;protocol=http | 08:21 |
| *** ant_work <ant_work!~ant__@host222-188-static.61-79-b.business.telecomitalia.it> has joined #yocto | 08:21 | |
| marek__ | bluelightning: unparsed line: 'KERNEL_VERSION = "${@get_kernelversion_file("${STAGING_KERNEL_BUILDDIR}" (I have poky daisy) | 08:26 |
| bluelightning | marek__: ah, I see | 08:28 |
| bluelightning | marek__: in which case try KERNEL_VERSION = "${@base_read_file('${STAGING_KERNEL_DIR}/kernel-abiversion')}" | 08:28 |
| *** pohly <pohly!~pohly@p5DE8CA2B.dip0.t-ipconnect.de> has quit IRC | 08:35 | |
| *** vquicksilver <vquicksilver!~nobody@gentoo/contributor/vquicksilver> has quit IRC | 08:35 | |
| *** nemequ <nemequ!~nemequ@ip68-111-201-164.sd.sd.cox.net> has quit IRC | 08:35 | |
| *** deception <deception!~deception@unaffiliated/deception> has quit IRC | 08:35 | |
| *** moto-timo <moto-timo!~timo@fsf/member/moto-timo> has quit IRC | 08:35 | |
| *** zaman1 <zaman1!zaman@nat/intel/x-awlasgsjevruhjzf> has quit IRC | 08:35 | |
| *** dshwang <dshwang!dshwang@nat/intel/x-wozdbeqdbruatrny> has quit IRC | 08:35 | |
| *** scot <scot!~scot@130.164.62.160> has quit IRC | 08:35 | |
| *** el_robin <el_robin!~el_robin@5.39.92.155> has quit IRC | 08:35 | |
| *** seezer <seezer!quassel@quassel/developer/seezer> has quit IRC | 08:35 | |
| *** Sput <Sput!~sputnick@quassel/developer/sput> has quit IRC | 08:35 | |
| *** ecdhe <ecdhe!~ecdhe@173-22-126-166.client.mchsi.com> has quit IRC | 08:35 | |
| *** pohly <pohly!~pohly@p5DE8CA2B.dip0.t-ipconnect.de> has joined #yocto | 08:37 | |
| *** vquicksilver <vquicksilver!~nobody@gentoo/contributor/vquicksilver> has joined #yocto | 08:37 | |
| *** nemequ <nemequ!~nemequ@ip68-111-201-164.sd.sd.cox.net> has joined #yocto | 08:37 | |
| *** deception <deception!~deception@unaffiliated/deception> has joined #yocto | 08:37 | |
| *** moto-timo <moto-timo!~timo@fsf/member/moto-timo> has joined #yocto | 08:37 | |
| *** zaman1 <zaman1!zaman@nat/intel/x-awlasgsjevruhjzf> has joined #yocto | 08:37 | |
| *** dshwang <dshwang!dshwang@nat/intel/x-wozdbeqdbruatrny> has joined #yocto | 08:37 | |
| *** scot <scot!~scot@130.164.62.160> has joined #yocto | 08:37 | |
| *** el_robin <el_robin!~el_robin@5.39.92.155> has joined #yocto | 08:37 | |
| *** seezer <seezer!quassel@quassel/developer/seezer> has joined #yocto | 08:37 | |
| *** Sput <Sput!~sputnick@quassel/developer/sput> has joined #yocto | 08:37 | |
| *** ecdhe <ecdhe!~ecdhe@173-22-126-166.client.mchsi.com> has joined #yocto | 08:37 | |
| *** psnsilva <psnsilva!~psnsilva@80.251.162.78> has joined #yocto | 08:39 | |
| marek__ | bluelightning: second version works fine, many thanks again | 08:52 |
| *** pidge <pidge!~pidge@2a02:8084:0:3000:c8fa:9120:d0d0:542a> has joined #yocto | 09:05 | |
| bluelightning | marek__: np | 09:05 |
| *** jimBaxter <jimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto | 09:05 | |
| *** belen <belen!~Adium@192.198.151.44> has joined #yocto | 09:12 | |
| *** imrehg <imrehg!~imrehg@27.246.192.109> has joined #yocto | 09:17 | |
| miandonmenmian_ | that hit the spot, thanks | 09:19 |
| *** psnsilva <psnsilva!~psnsilva@80.251.162.78> has quit IRC | 09:22 | |
| *** dieter__ <dieter__!~quassel@pD9FCD712.dip0.t-ipconnect.de> has joined #yocto | 09:28 | |
| *** parrot1 <parrot1!~chankitx@192.198.146.171> has quit IRC | 09:29 | |
| *** dieter_ <dieter_!~quassel@p5795C37F.dip0.t-ipconnect.de> has quit IRC | 09:31 | |
| *** psnsilva <psnsilva!~psnsilva@193-126-29-154.net.novis.pt> has joined #yocto | 09:34 | |
| *** miandonmenmian_ <miandonmenmian_!~miandonme@95-170-82-196.colo.transip.net> has quit IRC | 09:41 | |
| *** likewise <likewise!~likewise@ip4da37457.direct-adsl.nl> has joined #yocto | 09:43 | |
| *** miandonmenmian_ <miandonmenmian_!~miandonme@210.22.153.182> has joined #yocto | 09:43 | |
| *** dieter_ <dieter_!~quassel@p4FDC5AEA.dip0.t-ipconnect.de> has joined #yocto | 09:54 | |
| *** dieter__ <dieter__!~quassel@pD9FCD712.dip0.t-ipconnect.de> has quit IRC | 09:56 | |
| *** psnsilva <psnsilva!~psnsilva@193-126-29-154.net.novis.pt> has quit IRC | 09:56 | |
| *** imrehg <imrehg!~imrehg@27.246.192.109> has quit IRC | 10:01 | |
| *** psnsilva <psnsilva!~psnsilva@80.251.162.78> has joined #yocto | 10:11 | |
| *** cristianiorga <cristianiorga!~cristiani@134.134.137.71> has joined #yocto | 10:37 | |
| *** zenx <zenx!~quassel@37.189.236.81> has joined #yocto | 10:43 | |
| *** JaMae <JaMae!~martin@ip-86-49-34-37.net.upcbroadband.cz> has joined #yocto | 11:05 | |
| *** wschaller <wschaller!~wschaller@82-70-136-246.dsl.in-addr.zen.co.uk> has joined #yocto | 11:17 | |
| *** sameo <sameo!samuel@nat/intel/x-yrxuinuhmmwiuxwk> has joined #yocto | 11:22 | |
| mcfrisk | Does yocto have/do any tests for the generated sdk's? | 11:28 |
| sujith_h | michaelw_: ping | 11:32 |
| bluelightning | mcfrisk: yes, IIRC bitbake -c testsdk <image> | 11:38 |
| *** wschaller <wschaller!~wschaller@82-70-136-246.dsl.in-addr.zen.co.uk> has quit IRC | 11:45 | |
| *** nighty^ <nighty^!~nighty@hokuriku.rural-networks.com> has joined #yocto | 11:46 | |
| mcfrisk | bluelightning: thanks! is there any documentation to go with that? e.g. how to execute and write tests for the sdk packages. | 11:47 |
| *** fishey1 <fishey1!~ydoc@vcr.einic.org> has quit IRC | 11:48 | |
| *** jbrianceau <jbrianceau!uid10952@gateway/web/irccloud.com/x-csaomwrsxzyyvduh> has quit IRC | 11:51 | |
| *** jbrianceau <jbrianceau!uid10952@gateway/web/irccloud.com/x-arweptmpeeervist> has joined #yocto | 11:52 | |
| sujith_h | michaelw_: May I know if I am missing anything in my modified code ( which I have posted in mailing list)? When I tried to check request.POST ( in toastergui/views.py), the dictionary was empty. | 11:56 |
| *** seezer <seezer!quassel@quassel/developer/seezer> has quit IRC | 11:57 | |
| *** seezer <seezer!quassel@quassel/developer/seezer> has joined #yocto | 12:00 | |
| *** anselmolsm <anselmolsm!~anselmols@192.55.55.41> has joined #yocto | 12:13 | |
| *** fishey1 <fishey1!~ydoc@vcr.einic.org> has joined #yocto | 12:15 | |
| *** JaMae is now known as JaMa | 12:18 | |
| *** RP <RP!~richard@200.52.194.114> has quit IRC | 12:23 | |
| *** hugovs <hugovs!~hugo@177.159.144.73> has joined #yocto | 12:30 | |
| *** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has quit IRC | 12:34 | |
| *** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@yocto-www.yoctoproject.org> has joined #yocto | 12:34 | |
| *** zwerch <zwerch!~Adium@ip-178-200-96-248.hsi07.unitymediagroup.de> has joined #yocto | 12:35 | |
| *** slips <slips!~slips@240.150.34.95.customer.cdi.no> has quit IRC | 12:36 | |
| zwerch | Hello together. I have a question concerning the package management. We are using an image based on core-image-x11. We have defined all packages needed on the image via "IMAGE_INSTALL" variable. Updates are handled over the air, installed via "opkg update / upgrade". But we didn | 12:37 |
| zwerch | * Is there a way to install new packages over this mechanism? | 12:38 |
| zwerch | Without doing it manually | 12:38 |
| *** orzen <orzen!~orz@h180n2-ld-c-a31.ias.bredband.telia.com> has joined #yocto | 12:39 | |
| *** slips <slips!~slips@240.150.34.95.customer.cdi.no> has joined #yocto | 12:40 | |
| orzen | Hi, I wonder when aclocals end up in sysroot and where they're coming from? From a recipe or the host system? | 12:40 |
| bluelightning | mcfrisk: I don't believe we do have any documentation on testsdk, no, but see meta/lib/oeqa/sdk/ for the current tests which should serve as examples | 12:49 |
| *** psnsilva <psnsilva!~psnsilva@80.251.162.78> has quit IRC | 12:50 | |
| michaelw_ | sujith_h: yep, let me reply on the email thread | 12:50 |
| bluelightning | zwerch: you mean as part of an upgrade? wouldn't you just make them a dependency of some already-installed package? | 12:50 |
| mcfrisk | bluelightning: yes, I read meta/lib/oeqa/sdk/ but am failing to execute them on dizzy. tried to backport the gcc tests for example but something is wrong in my config since they fail with "Test ping specified in TEST_SUITES could not be found in lib/oeqa/runtime under BBPATH" | 12:52 |
| michaelw_ | sujith_h: what is the 'json' for in " client.post(reverse('xhr_importlayer'),data,'json' " | 12:52 |
| bluelightning | mcfrisk: strange, that sounds like testimage rather than testsdk | 12:53 |
| zwerch | bluelightning: Yes. We need a mechanism that upgrades the whole system with one command / small failsafe-script, not via images but via intelligent incremental upgrades (and opkg does this very well, but not with new packages). So in this case it wouldn't be bad practice to use all packages as a dependency of a virtual package instead of installing them via "IMAGE_INSTALL"? | 12:54 |
| *** wschaller <wschaller!~wschaller@82-70-136-246.dsl.in-addr.zen.co.uk> has joined #yocto | 12:55 | |
| zwerch | michaelw_: I assume it sets the content-type header to "application/json" | 12:55 |
| *** zenx <zenx!~quassel@37.189.236.81> has quit IRC | 12:55 | |
| *** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has joined #yocto | 12:55 | |
| bluelightning | zwerch: I don't see a problem with that... but you need not add all packages as dependencies, in fact you could install a packagegroup and have no dependencies initially, just adding them as needed as time goes on | 12:55 |
| *** davis <davis!~davis@rrcs-96-10-245-18.midsouth.biz.rr.com> has joined #yocto | 12:55 | |
| *** tsramos <tsramos!~tsramos@192.55.54.42> has joined #yocto | 12:56 | |
| davis | i can use hob to build custom targets, but how can I get a list of targets available at bitbake prompt? | 12:57 |
| *** ant_work <ant_work!~ant__@host222-188-static.61-79-b.business.telecomitalia.it> has quit IRC | 12:57 | |
| bluelightning | davis: bitbake -s or bitbake-layers show-recipes perhaps | 12:58 |
| zwerch | bluelightning: okay, thanks so far. How do I define runtime dependencies? And what is a packagegroup? | 12:58 |
| davis | bluelightning: many thanks. | 12:59 |
| bluelightning | zwerch: RDEPENDS_<packagename> (RDEPENDS_${PN} for the main package of a recipe) | 12:59 |
| bluelightning | zwerch: a packagegroup is a way of grouping together packages as the name suggests; but fundamentally on the runtime end it's just a package with no contents and a list of dependencies on other packages | 12:59 |
| bluelightning | zwerch: on the recipe end it's a recipe that inherits packagegroup | 13:00 |
| *** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto | 13:00 | |
| bluelightning | zwerch: loads of examples in meta/recipes-core/packagegroups/ | 13:00 |
| sujith_h | michaelw_: If I have: response = client.post(reverse('xhr_importlayer'), data, HTTP_X_REQUESTED_WITH='XMLHttpRequest'). I am getting same error. | 13:00 |
| zwerch | bluelightning: awesome, thanks! | 13:00 |
| mcfrisk | hmm, how to run bitbake python snippets things like run.do_testsdk in a devshell? | 13:04 |
| bluelightning | mcfrisk: I don't think you can | 13:04 |
| mcfrisk | sigh, then I'll debug this in some other way... | 13:07 |
| bluelightning | mcfrisk: to be honest I almost never use devshell myself, I just insert bb.warn() calls in where I need to see what is happening | 13:08 |
| bluelightning | crude, but effective# | 13:08 |
| michaelw_ | sujith_h: hmm odd it works here | 13:13 |
| mcfrisk | bluelightning: thanks, I saw that TEST_SUITES wasn't defined in my local.conf and ping was a default. Now I need to fix those tests for our setup... | 13:13 |
| *** wschaller <wschaller!~wschaller@82-70-136-246.dsl.in-addr.zen.co.uk> has quit IRC | 13:15 | |
| abelloni | bluelightning: that reminds me of when people are asking how to debug the kernel, my only answer is pr_err | 13:15 |
| abelloni | they are always disappointed :) | 13:15 |
| michaelw_ | sujith_h: http://pastebin.com/bkLAwtjm | 13:16 |
| bluelightning | mcfrisk: the error would suggest that it's looking in the wrong place, perhaps the error is simply incorrect for testsdk | 13:22 |
| bluelightning | abelloni: indeed | 13:23 |
| davis | i read someplace that mods done in hob do not take affect bitbake cmdline builds. Is that correct? I see changes in my local.conf files and it does seem to affect my bitbake builds. | 13:26 |
| *** luyu__ <luyu__!luyu@nat/intel/x-jcvmbpmjzjphmnmc> has quit IRC | 13:28 | |
| *** luyu__ <luyu__!luyu@nat/intel/x-uxkvkjhxzwfffbzk> has joined #yocto | 13:31 | |
| * paulg_ wonders how accepting folks would be of patches that turn tar based pkgs into git based... | 13:31 | |
| paulg_ | bisecting within a pkg within yocto is a heck of a lot easier if the pkg is already git based. | 13:31 |
| paulg_ | at the cost of a slightly larger download. | 13:32 |
| bluelightning | davis: that might have been true in older versions of Hob | 13:34 |
| *** belen1 <belen1!~Adium@17.114.2.81.in-addr.arpa> has joined #yocto | 13:35 | |
| davis | bluelightning: that makes sense. thanks | 13:35 |
| bluelightning | paulg_: across the board, I think we would prefer not to make that change | 13:35 |
| paulg_ | bluelightning, ok, then my next suggestion would be to somehow have it there, but off by default then. | 13:36 |
| davis | fwiw, i learned you can do "bitbake -c menuconfig virtual/kernel" and it will pull up make menuconfig for the virtual kernel. Is there a way to run menuconfig for the specific kernel I am using? ie. Not edit generic/virtual kernel config but arm/beaglebone kernel. | 13:37 |
| paulg_ | not sure the implementation specifics of how best to make that work... | 13:37 |
| ndec | davis: you can use the kernel recipe name instead of virtual/kernel, no? | 13:37 |
| bluelightning | paulg_: it may be something to open up a discussion on on the OE-Core mailing list - the topic of git vs. tarballs has come up in a couple of threads lately but we haven't had a proper discussion about it | 13:38 |
| bluelightning | davis: virtual/kernel should be the kernel for your machine if MACHINE has been set | 13:38 |
| davis | ndec, got me. I'm not sure how to specify the particular name. Is there a way to list the different kernels available? | 13:38 |
| davis | bluelightning: hmm. I don't see any arm specific options. When this build finishes. I'll try again. | 13:39 |
| bluelightning | virtual/kernel isn't a "generic" kernel, it just points to the selected kernel for your configuration | 13:39 |
| *** belen1 <belen1!~Adium@17.114.2.81.in-addr.arpa> has quit IRC | 13:39 | |
| paulg_ | bluelightning, yeah - it just seems fresh on my mind since I had to bisect both libdrm and xf86-video-intel to solve that latest X11 segfault mess. | 13:40 |
| paulg_ | http://thread.gmane.org/gmane.comp.handhelds.openembedded.core | 13:40 |
| bluelightning | paulg_: in order to bisect easily though wouldn't you need to be pointing to a local source tree? in which case "devtool modify" would be the recommended way to set that up for almost any recipe | 13:42 |
| bluelightning | although that still provides no shortcut to the upstream git for a recipe that fetches from a tarball instead, admittedly | 13:43 |
| paulg_ | bluelightning, in this case, I wanted to be sure of what libdrm was putting in the sysroot, so while I ran the bisect commands on a local tree, I used the output of those commands in a SRCREV in the bb to ensure I wasn't changing two things at once. | 13:45 |
| paulg_ | and of course put the git repo in the SRC_URI and put S="${WORKDIR}/git" | 13:45 |
| * paulg_ has never used "devtool modify" | 13:46 | |
| neverpanic | Is there a recipe that should provide cc and c++ symlinks? I would expect GCC to use update-alternatives to do that, but it doesn't seem to be happening for me... | 13:47 |
| zwerch | bluelightning: what is the name I need to use in IMAGE_INSTALL if my packagegroup-recipe is "packagegroup-core-mystuff.bb"? | 13:47 |
| bluelightning | zwerch: packagegroup-core-mystuff | 13:47 |
| zwerch | bluelightning: ok, thanks | 13:48 |
| bluelightning | zwerch: also, it should not be named including "core" - it's not a core recipe if it's not in OE-Core ;) | 13:48 |
| davis | bluelightning: you are correct. I must have been using qemu before. It indeed shows arm config. cool. | 13:48 |
| davis | bluelightning: many thanks | 13:48 |
| bluelightning | davis: no worries | 13:48 |
| zwerch | bluelightning: ok 😄 | 13:48 |
| bluelightning | paulg_: it's new as of the last release... if you get a chance, give it a try | 13:48 |
| * paulg_ reads | 13:48 | |
| davis | does it matter what the order is when you add layers? I have built a bootable rootfs with the stock layers. I would like to add the meta-ti layer since it has the cape manager. supposedly it modifies the kernel config as well. | 13:50 |
| davis | owuld I add this to BBLAYERS at end or beginning or does it matter? | 13:51 |
| zwerch | bluelightning: so if I install "packagegroup-mystuff", it automatically installs all packages defined in there? :O | 13:51 |
| denix | davis: it doesn't have the cape manager | 13:52 |
| bluelightning | zwerch: yes | 13:52 |
| zwerch | bluelightning: cool! | 13:52 |
| davis | denix: the ti kernel or the stock one? | 13:52 |
| denix | davis: but the order is important when you have overlapping configs | 13:52 |
| davis | when I boot the stock one, and I do the grep config.gz I don't see it. | 13:52 |
| bluelightning | zwerch: well, it'll install all the packages defined as dependencies in RDEPENDS_${PN} in that recipe, to be specific | 13:53 |
| davis | denix: I figured, the meta-ti one would since I found the cape-manager user space tools in the meta-ti layer via some tool | 13:53 |
| neverpanic | nevermind, c++ and cc are in gcc/g++-symlinks, I just need to install them | 13:53 |
| denix | davis: neither | 13:54 |
| davis | hmm. | 13:54 |
| davis | on the kernel i am running, this fails zcat /proc/config.gz | grep CONFIG_BONE_CAPEMGR | 13:56 |
| davis | this is from https://github.com/beagleboard/bb.org-overlays readme | 13:56 |
| denix | davis: as of the order - meta-yocto-bsp provides beaglebone.conf as well as meta-ti, so depending on the order, you get one machine definition or another. best to remove meta-yocto-bsp reference bsp when switching to real bsp | 13:56 |
| *** belen1 <belen1!~Adium@17.114.2.81.in-addr.arpa> has joined #yocto | 13:56 | |
| davis | denix, sorry pal I am so new to this I don't know what I am doing. So I should remove the meta-yocto-bsp and add meta-ti. | 13:57 |
| davis | i'll try that and see what happens. | 13:57 |
| davis | i removed the meta-yocto-bsp and only have the meta-ti one. Any idea where in menuconfig the cape manager would be? under what heading? | 13:59 |
| *** belen <belen!~Adium@192.198.151.44> has quit IRC | 14:00 | |
| *** tsramos_ <tsramos_!~tsramos@134.134.137.71> has joined #yocto | 14:01 | |
| *** belen <belen!Adium@nat/intel/x-otnqfrntiowitfcu> has joined #yocto | 14:01 | |
| *** belen1 <belen1!~Adium@17.114.2.81.in-addr.arpa> has quit IRC | 14:01 | |
| *** tsramos__ <tsramos__!~tsramos@192.55.54.36> has joined #yocto | 14:03 | |
| *** tsramos <tsramos!~tsramos@192.55.54.42> has quit IRC | 14:04 | |
| *** tsramos__ <tsramos__!~tsramos@192.55.54.36> has quit IRC | 14:04 | |
| zwerch | bluelightning: I must've done something wrong, I'm getting " * opkg_install_cmd: Cannot install package packagegroup-mystuff", what could cause this? | 14:04 |
| *** madisox <madisox!~madison@64-71-1-115.static.wiline.com> has joined #yocto | 14:05 | |
| *** tsramos_ <tsramos_!~tsramos@134.134.137.71> has quit IRC | 14:05 | |
| bluelightning | zwerch: your recipe does "inherit packagegroup" right ? | 14:05 |
| zwerch | bluelightning: yep | 14:06 |
| bluelightning | zwerch: then you should not see that... what that indicates is the recipe claimed to produce that package and in the end didn't | 14:06 |
| *** afxez0r <afxez0r!afxez0r@nat/intel/x-byzlogofhzlpdrga> has joined #yocto | 14:08 | |
| zwerch | bluelightning: https://gist.github.com/zwerch/d797d5ce3e411d6f39fc | 14:09 |
| bluelightning | zwerch: having set PACKAGES to what you have set, you have stopped it providing the main package | 14:09 |
| bluelightning | zwerch: which is probably not what you want | 14:10 |
| zwerch | bluelightning: so deleting the PACKAGES part fixes it? | 14:11 |
| bluelightning | zwerch: well, decide what you want - do you need more than one packagegroup package defined by the recipe or not? | 14:11 |
| *** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC | 14:13 | |
| davis | denix: this seems to be important. I added ti before and it simply busted my build. Now that I removed meta-yocto-bsp it is at least fetching new sources or so it seems. that appears to be an improvment. | 14:13 |
| zwerch | bluelightning: I need a "dynamic" packagegroup that also allows me to add a new group if necessary with new packages but is installed via one IMAGE_INSTALL (so new packages are automatically added via opkg upgrade) | 14:14 |
| bluelightning | zwerch: you can comfortably add new packagegroups to that recipe as dependencies of the main package, but when you do that, use PACKAGES += not PACKAGES = | 14:15 |
| *** belen1 <belen1!~Adium@17.114.2.81.in-addr.arpa> has joined #yocto | 14:18 | |
| *** lamego <lamego!~lamego@134.134.139.70> has joined #yocto | 14:19 | |
| zwerch | bluelightning: it seems to have worked, thanks again! | 14:20 |
| bluelightning | zwerch: np | 14:20 |
| davis | zwerch: congratualtions! | 14:21 |
| *** belen1 <belen1!~Adium@17.114.2.81.in-addr.arpa> has quit IRC | 14:22 | |
| zwerch | haha, thanks | 14:23 |
| *** jku <jku!jku@nat/intel/x-eosnuowfmemkmfsz> has quit IRC | 14:24 | |
| *** RP <RP!~richard@192.55.54.60> has joined #yocto | 14:28 | |
| *** jbrianceau is now known as jbrianceau_brb | 14:32 | |
| *** hsychla <hsychla!~hsychla@pd95c9392.dip0.t-ipconnect.de> has joined #yocto | 14:32 | |
| hsychla | Hi all! I am getting "WARNING: Inode check for /srv/yocto-dl-dir is unavaliable, will remove it from disk monitor". "df -i" shows | 14:33 |
| hsychla | Filesystem Inodes IUsed IFree IUse% Mounted on | 14:33 |
| hsychla | rootfs 0 0 0 - / | 14:33 |
| hsychla | am I missing a dependency? | 14:33 |
| bluelightning | hsychla: what fs is in use there? | 14:33 |
| hsychla | bluelightning: btrfs | 14:33 |
| bluelightning | hsychla: I suspect you can ignore the warning, it probably shouldn't be shown | 14:34 |
| hsychla | it's not only dl-dir but sstate-cache etc as well. and it want's to build all packages from scratch which I guess is related | 14:34 |
| bluelightning | hsychla: I doubt that that's related, the disk monitor is unconnected to sstate | 14:35 |
| hsychla | ah ok | 14:35 |
| *** marek__ <marek__!~marek@81.89.61.168.vnet.sk> has quit IRC | 14:35 | |
| hsychla | we moved the buildroot from a VM into a docker container. did it before without problems but this time bitbake want to rebuild everything | 14:37 |
| sujith_h | michaelw_: Thanks for help. But I still not getting "error": "hint-layer-version-exists". Instead what I am getting is http://pastebin.com/JMhTP0p5 | 14:37 |
| bluelightning | hsychla: you would have to do comparisons of siginfo/sigdata files with bitbake-diffsigs to determine for sure what changed, but something must have | 14:38 |
| *** belen1 <belen1!~Adium@17.114.2.81.in-addr.arpa> has joined #yocto | 14:40 | |
| *** hamis <hamis!~irfan@110.93.212.98> has quit IRC | 14:40 | |
| hsychla | bluelightning: is that always for one package or can I check the diffsigs for a whole core-image | 14:42 |
| hsychla | ? | 14:42 |
| bluelightning | hsychla: one task at a time I'm afraid, though -t is supposed to allow you to trace back in practice it doesn't work as well as it should | 14:42 |
| hsychla | ok, thanks. this helped a lot | 14:43 |
| bluelightning | hsychla: simplest thing is to do it for the earliest task that ran; you can look at the latest log under tmp/log/cooker/ to find what that was | 14:43 |
| hsychla | already found a difference | 14:44 |
| *** belen1 <belen1!~Adium@17.114.2.81.in-addr.arpa> has quit IRC | 14:44 | |
| *** Jefro <Jefro!~jefro@50-0-152-82.dedicated.static.sonic.net> has joined #yocto | 14:54 | |
| *** belen1 <belen1!Adium@nat/intel/x-relykrkvqzzysnpw> has joined #yocto | 14:54 | |
| *** belen <belen!Adium@nat/intel/x-otnqfrntiowitfcu> has quit IRC | 14:55 | |
| sjolley | YPTM: Ready-Access Number: 8007302996 Access Code: 2705751 | 14:57 |
| sjolley | YPTM: Stephen Joined | 14:57 |
| belen1 | YPTM: belen joined | 15:00 |
| halstead | YPTM: Michael present. | 15:00 |
| *** dlerner <dlerner!~dlerner@50-198-55-145-static.hfc.comcastbusiness.net> has joined #yocto | 15:00 | |
| *** sona <sona!5518c375@gateway/web/freenode/ip.85.24.195.117> has joined #yocto | 15:01 | |
| *** belen <belen!~Adium@17.114.2.81.in-addr.arpa> has joined #yocto | 15:01 | |
| sona | hi, sona here ! | 15:03 |
| *** Raad_ <Raad_!c0373624@gateway/web/freenode/ip.192.55.54.36> has joined #yocto | 15:03 | |
| *** Ovidiu <Ovidiu!567d0cc4@gateway/web/freenode/ip.86.125.12.196> has joined #yocto | 15:03 | |
| Ovidiu | Ovidiu Poncea @ windriver | 15:04 |
| *** belen <belen!~Adium@17.114.2.81.in-addr.arpa> has quit IRC | 15:06 | |
| *** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC | 15:08 | |
| *** Ovidiu <Ovidiu!567d0cc4@gateway/web/freenode/ip.86.125.12.196> has quit IRC | 15:09 | |
| sjolley | Musat, George L <george.l.musat@intel.com> - QA contact. | 15:10 |
| *** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has joined #yocto | 15:11 | |
| *** Raad_ <Raad_!c0373624@gateway/web/freenode/ip.192.55.54.36> has quit IRC | 15:12 | |
| sjolley | YPTM is over. | 15:12 |
| michaelw_ | sujith_h: Does the layer you're adding actually already exist? Remember that the unit tests run on a clean database, the only layers the system knows about are the ones added in the setUp function | 15:13 |
| *** sjolley <sjolley!~sjolley@134.134.137.71> has quit IRC | 15:16 | |
| sujith_h | michaelw_: yes it does exist in location : /home/sujith/MEL/toaster_work/meta-oe | 15:17 |
| michaelw_ | sujith_h: is that in the database then? | 15:20 |
| *** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has quit IRC | 15:21 | |
| *** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto | 15:21 | |
| *** sona <sona!5518c375@gateway/web/freenode/ip.85.24.195.117> has quit IRC | 15:22 | |
| sujith_h | michaelw_: give me a min | 15:22 |
| sujith_h | michaelw_: checking | 15:22 |
| *** belen <belen!~Adium@17.114.2.81.in-addr.arpa> has joined #yocto | 15:23 | |
| *** belen <belen!~Adium@17.114.2.81.in-addr.arpa> has quit IRC | 15:27 | |
| *** jbrianceau_brb is now known as jbrianceau | 15:29 | |
| *** belen <belen!~Adium@192.198.151.44> has joined #yocto | 15:34 | |
| *** belen1 <belen1!Adium@nat/intel/x-relykrkvqzzysnpw> has quit IRC | 15:34 | |
| otavio | RP: did you look at mesa fixes? | 15:34 |
| *** wschaller <wschaller!~wschaller@82-70-136-246.dsl.in-addr.zen.co.uk> has joined #yocto | 15:35 | |
| davis | there is this git repot https://github.com/beagleboard/meta-beagleboard | 15:37 |
| davis | if I download all these sub repots, and replace the ones I'm using in yocto now. meta-yocto-bsp with meta-beagleboard, openembedded-core, etc. Will I be able to build the beaglebone reference or will it break yocto and I need to do this from openembedded instead? | 15:38 |
| *** T0mW <T0mW!~Tom@70.15.161.110.res-cmts.t132.ptd.net> has joined #yocto | 15:39 | |
| *** TobSnyder1 <TobSnyder1!~schneider@ip923450f2.dynamic.kabel-deutschland.de> has quit IRC | 15:43 | |
| *** sjolley <sjolley!sjolley@nat/intel/x-ttywhbdqgjkqshlv> has joined #yocto | 15:44 | |
| *** zwerch <zwerch!~Adium@ip-178-200-96-248.hsi07.unitymediagroup.de> has left #yocto | 15:45 | |
| sujith_h | michaelw_: Is it orm_layer table which has the info? | 15:45 |
| *** belen1 <belen1!~Adium@17.114.2.81.in-addr.arpa> has joined #yocto | 15:45 | |
| bluelightning | davis: that should work fine | 15:47 |
| *** belen1 <belen1!~Adium@17.114.2.81.in-addr.arpa> has quit IRC | 15:50 | |
| davis | bluelightning: somehow, I think i'm going to fsck it up though | 15:50 |
| sujith_h | michaelw_: I couldn't find it in orm_layer table. In orm_layersource, I have only 3 entries | 15:50 |
| davis | i pulled the layers referenced here https://github.com/beagleboard/meta-beagleboard | 15:51 |
| davis | which is meta-beagleboard meta-openembedded and openembedded-core | 15:51 |
| *** paulg <paulg!~paulg@72.1.195.9> has joined #yocto | 15:51 | |
| davis | and then in poky/build/conf/bblayers.conf I have the following layers set: | 15:52 |
| davis | "/home/davis/progs/poky/meta /home/davis/progs/poky/meta-yocto /home/davis/progs/beagle-ref/meta-beagleboard /home/davis/progs/beagle-ref/meta-openembedded /home/davis/progs/beagle-ref/openembedded-core" | 15:52 |
| davis | but I notice that openembedded-core has its own oe-init-build-env which looks like a script similar to the one I source in yocto | 15:53 |
| kergoth | the poky repository is an integration of bitbake, oe-core, and meta-yocto | 15:53 |
| kergoth | so yes, the oe-init-build-env from oe-core is exactly the same as the one you source from poky | 15:54 |
| davis | thats good | 15:54 |
| davis | sadly bitbake -c menuconfig virtual/kernel no longer works though. | 15:55 |
| davis | if I cc ~/progs/poky and then source oe-init-build-env and then bitbake -c menuconfig virtual/kernel it fails. it is looking for a meta-beagleboard/conf/layer.conf file | 15:57 |
| davis | im totally confused | 16:02 |
| kergoth | if you read https://github.com/beagleboard/meta-beagleboard#introduction, you'll see that the meta-beagleboard repository includes two layers, it itself isn't a layer | 16:04 |
| kergoth | assuming you want the beaglebone machine, you'd want common-bsp, see https://github.com/beagleboard/meta-beagleboard/tree/master/common-bsp/conf/machine | 16:04 |
| davis | ok one sec, let me read that. | 16:05 |
| davis | i'm not sure how you know it includes two layers and is not itself a layer | 16:06 |
| *** belen1 <belen1!~Adium@17.114.2.81.in-addr.arpa> has joined #yocto | 16:07 | |
| davis | are you looking at the list of files and see that it has two subdirs? common-bsp and meta-beagleboard-extras? | 16:07 |
| davis | so https://github.com/beagleboard/meta-beagleboard/tree/master/common-bsp/conf/machine that beaglebone.conf should be put where the missing config file was mentioned by bitbake? | 16:09 |
| *** SoylentYellow <SoylentYellow!~SoylentYe@130.164.63.74> has quit IRC | 16:10 | |
| *** belen1 <belen1!~Adium@17.114.2.81.in-addr.arpa> has quit IRC | 16:11 | |
| *** behanw <behanw!~behanw@2001:470:b26c:0:8124:ab83:8ad4:e6ed> has joined #yocto | 16:14 | |
| mcfrisk | sigh, sdk installer shell script is quite crappy. full of non-quoted variables, non-checked return values... A run with shellcheck would be in order, as would 'set -euxo pipefail'. Are there any standards for shell scripts in yocto? | 16:16 |
| *** dlan_ <dlan_!~dennis@gentoo/developer/dlan> has quit IRC | 16:18 | |
| *** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto | 16:19 | |
| kergoth | davis: just add meta-beaglebone/common-bsp/ to bblayers, not meta-beagleboard. | 16:26 |
| *** belen1 <belen1!~Adium@17.114.2.81.in-addr.arpa> has joined #yocto | 16:29 | |
| davis | kergoth: ok. i'll try that. I appreciate your expertise. I'm really lost in this whole layer thing. | 16:31 |
| davis | i belive this is the change you suggest | 16:32 |
| davis | BBLAYERS = "/home/davis/progs/poky/meta /home/davis/progs/poky/meta-yocto /home/davis/progs/beagle-ref/meta-beagleboard/common-bsp /home/davis/progs/beagle-ref/meta-openembedded /home/davis/progs/beagle-ref/openembedded-core" | 16:32 |
| davis | nope. fails again. | 16:33 |
| *** belen1 <belen1!~Adium@17.114.2.81.in-addr.arpa> has quit IRC | 16:33 | |
| kergoth | 'fails again' tells us nothing | 16:35 |
| davis | its the same error. ERROR: Unable to parse /home/davis/progs/beagle-ref/meta-openembedded/conf/layer.conf: file /home/davis/progs/beagle-ref/meta-openembedded/conf/layer.conf not found | 16:36 |
| kergoth | meta-openembedded is the same thing. it's multiple layers, not one. | 16:37 |
| davis | i'm thinking i need to revert the layers | 16:37 |
| kergoth | which of its layers are you wanting? | 16:37 |
| kergoth | most likely it's meta-oe | 16:37 |
| kergoth | so add meta-openembedded/meta-oe | 16:37 |
| davis | all i'm trying to do is get the LCD cape working on this beaglebone with a custom build. | 16:37 |
| davis | I know that the build which I downloaded in binary form has it, but the one I built as a result of pulling down poky does not. | 16:38 |
| davis | i asked around and found that git repot which I am trying to use. | 16:38 |
| davis | this one worked for building java but no lcd | 16:39 |
| *** wschaller <wschaller!~wschaller@82-70-136-246.dsl.in-addr.zen.co.uk> has quit IRC | 16:39 | |
| davis | #BBLAYERS = "/home/davis/progs/poky/meta /home/davis/progs/poky/meta-yocto /home/davis/progs/poky/meta-yocto-bsp /home/davis/progs/meta-oracle-java " | 16:39 |
| davis | adding the meta-openembedded/meta-oe as you suggests gives the same error | 16:41 |
| davis | BBLAYERS = "/home/davis/progs/poky/meta /home/davis/progs/poky/meta-yocto /home/davis/progs/beagle-ref/meta-beagleboard/common-bsp /home/davis/progs/beagle-ref/meta-openembedded /home/davis/progs/beagle-ref/openembedded-core /ho | 16:41 |
| davis | me/davis/progs/beagle-ref/meta-openembedded/meta-oe" | 16:41 |
| kergoth | you didn't remove the old non-existant meta-openembedded | 16:42 |
| kergoth | as i said, it's not a layer | 16:42 |
| *** ftonello <ftonello!~felipe@81.145.202.106> has joined #yocto | 16:42 | |
| *** jonathanmaw <jonathanmaw!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has quit IRC | 16:45 | |
| *** ftonello <ftonello!~felipe@81.145.202.106> has quit IRC | 16:47 | |
| davis | kergoth: sorry man. I don't really know how to determine if something is a layer. I just saw on that git repot it said it depended on it. so every thing it depened upon I pulled and then added to the layers. | 16:48 |
| davis | BBLAYERS = "/home/davis/progs/poky/meta /home/davis/progs/poky/meta-yocto /home/davis/progs/beagle-ref/meta-beagleboard/common-bsp /home/davis/progs/beagle-ref/openembedded-core /home/davis/progs/beagle-ref/meta-openembedded/met | 16:48 |
| davis | a-oe" | 16:48 |
| davis | that still fails with the same error. | 16:48 |
| kergoth | you'll note bitbake complains if <layer path>/conf/layer.conf doesn't exist. if a path has no conf/layer.conf, it's not a layer. now you know | 16:49 |
| fray | at a minimum a layer includes a 'conf' directory containing the file 'layer.conf' | 16:49 |
| davis | in beaglebone-ref, the meta-beagleboneboard does not have a layer.conf in top dir | 16:50 |
| fray | layer.conf is in the 'conf' directory of a layer.. | 16:50 |
| davis | ditto for the other two dirs, meta-openembedded and openembedded-core | 16:50 |
| fray | if there is no conf directory and a conf/layer.conf, they're not layers | 16:50 |
| *** belen1 <belen1!~Adium@17.114.2.81.in-addr.arpa> has joined #yocto | 16:50 | |
| fray | layers in the openembedded-core are in the 'meta', 'meta-selftest' and 'meta-skeleton' directories.. | 16:51 |
| fray | Note, your first BBLAYERS= value is your 'meta' directory.. | 16:51 |
| davis | well, none of these things that I pulled are layers then | 16:51 |
| fray | poky is based on OpenEmbedded-core.. so including both 'poky' and 'openembedded-core' is going to also cause problems | 16:51 |
| davis | none have a conf/layer.conf file | 16:51 |
| fray | they're directories that may contain layers, but they are not layers themselves | 16:52 |
| davis | ok this is frustrating. i should go back to buildroot | 16:52 |
| *** SoylentYellow <SoylentYellow!~SoylentYe@209-234-137-234.static.twtelecom.net> has joined #yocto | 16:52 | |
| davis | i just dont have the expertise for this | 16:53 |
| bluelightning | davis: you just need to get the paths correct... you're like two steps away now | 16:53 |
| davis | if I revert back to what I started with, at least I can do the make menuconfig ok | 16:54 |
| davis | BBLAYERS = "/home/davis/progs/poky/meta /home/davis/progs/poky/meta-yocto /home/davis/progs/poky/meta-yocto-bsp /home/davis/progs/meta-oracle-java " | 16:54 |
| fray | that is a correct bblayers configuration | 16:54 |
| fray | all four of those are layers AFAIK | 16:54 |
| davis | and Robert Nelson made this for me | 16:54 |
| davis | https://github.com/RobertCNelson/meta-beagleboard-kernel | 16:54 |
| *** belen1 <belen1!~Adium@17.114.2.81.in-addr.arpa> has quit IRC | 16:55 | |
| *** likewise <likewise!~likewise@ip4da37457.direct-adsl.nl> has quit IRC | 16:55 | |
| davis | i'm going to try and see if I can build core-image-sato with the original layer. If that finishes, i'll try this agian. | 16:57 |
| davis | i appreciate the help | 16:57 |
| *** jbrianceau is now known as jbrianceau_away | 17:00 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 17:04 | |
| *** tsramos <tsramos!tsramos@nat/intel/x-pfrzhvxkpsblbyeo> has joined #yocto | 17:04 | |
| *** benjamirc <benjamirc!besquive@nat/intel/x-yqlnabqxwmxkaxlf> has quit IRC | 17:05 | |
| *** benjamirc <benjamirc!besquive@nat/intel/x-wezjqeraflhhuwvj> has joined #yocto | 17:08 | |
| *** belen1 <belen1!~Adium@17.114.2.81.in-addr.arpa> has joined #yocto | 17:12 | |
| *** belen1 <belen1!~Adium@17.114.2.81.in-addr.arpa> has quit IRC | 17:17 | |
| *** RP <RP!~richard@192.55.54.60> has quit IRC | 17:21 | |
| *** lordzen <lordzen!~lordzen@93-51-177-218.ip268.fastwebnet.it> has quit IRC | 17:21 | |
| *** dieter_ <dieter_!~quassel@p4FDC5AEA.dip0.t-ipconnect.de> has quit IRC | 17:25 | |
| *** psnsilva <psnsilva!~psnsilva@80.251.162.78> has joined #yocto | 17:27 | |
| *** dryawgmoth <dryawgmoth!~varx@173.200.77.82> has joined #yocto | 17:28 | |
| *** psnsilva <psnsilva!~psnsilva@80.251.162.78> has quit IRC | 17:31 | |
| *** belen1 <belen1!~Adium@17.114.2.81.in-addr.arpa> has joined #yocto | 17:34 | |
| *** dryawgmoth <dryawgmoth!~varx@173.200.77.82> has quit IRC | 17:34 | |
| *** dfaught <dfaught!~dfaught@cpe-70-119-105-90.tx.res.rr.com> has joined #yocto | 17:36 | |
| *** belen <belen!~Adium@192.198.151.44> has quit IRC | 17:39 | |
| *** belen1 <belen1!~Adium@17.114.2.81.in-addr.arpa> has quit IRC | 17:39 | |
| *** hsychla <hsychla!~hsychla@pd95c9392.dip0.t-ipconnect.de> has quit IRC | 17:40 | |
| *** dryawgmoth <dryawgmoth!~varx@173.200.77.82> has joined #yocto | 17:46 | |
| *** dryawgmoth <dryawgmoth!~varx@173.200.77.82> has quit IRC | 17:55 | |
| davis | hmm. After i reverted my bblayers variable, bitbake of core-image-sato and the other image I built jfd-image-recipe fails at the last task. | 17:58 |
| davis | Error: min. I/O unit was not specified (use -h for help) | 17:59 |
| *** silviof <silviof!~silviof@unaffiliated/silviof> has quit IRC | 18:04 | |
| *** dryawgmoth <dryawgmoth!~varx@173.200.77.82> has joined #yocto | 18:08 | |
| davis | so what is the yocto way of solving this problem? I look at the create_image.ubifs script and I don't see any path wrong at the end where it invokes mkfs.ubifs, but I do see some .lock files around. | 18:20 |
| davis | ie. in the dir where rootfs is located, there is a rootfs.lock file. | 18:21 |
| davis | perhaps its an error where a lockfile has kept something from being used | 18:21 |
| davis | i read something about cleaning a build results using the term sane. i can't remember where I saw it though. | 18:22 |
| fray | I'm unfamiliar with that error message. I'd suggest a quick google search or look in the docs specific about building a ubifs under OE | 18:22 |
| fray | But my suspicion is that the machine you choose does not have UBIFS support enabled or configured properly | 18:22 |
| davis | hmm. i remember when I was using hob there was a button you could press which would bring up a config for those tyupe of things | 18:23 |
| fray | that would be the toaster in modern items.. | 18:23 |
| davis | i don't remember adjusting it though. | 18:23 |
| davis | i tried to use toaster. I played with it sunday in analyze and build mode | 18:24 |
| fray | docs explain how to start the toaster and how to conncet to it with your web browser.. I don't know if those configuration settings are available or not. The docs on the Yocto Project site should explain the various configuration parameters.. otherwise look in meta/conf/documentation.conf | 18:24 |
| fray | if there is a setting needed and it's not listed, then it's likely a bug in the docs | 18:24 |
| davis | i could start it. I think I even used it to do a build. | 18:25 |
| davis | when I used it, I was able to find the layer for pulling in capes. When I added the layer, it would fetch things for me. | 18:25 |
| davis | do you use toaster or use the command line? | 18:25 |
| fray | yes.. that is what toaster allows you to do.. | 18:26 |
| fray | I use command line mostly.. but rarely need ubifs | 18:26 |
| davis | i don't have a clue where that would be specified in command line | 18:26 |
| davis | i imaging its a conf file | 18:26 |
| davis | in my local.conf there is this | 18:27 |
| davis | #added by hob | 18:27 |
| davis | IMAGE_FSTYPES = "jffs2 ext4 ubi tar.gz tar.bz2" | 18:27 |
| davis | that would lead me to think I have ubi specified | 18:28 |
| fray | yes, but you or your MACHINE need to configure the filesystem.. | 18:28 |
| fray | thus the error from the mkfs ubifs | 18:28 |
| fray | it sounds like something is not configured and doesn't have a default value | 18:29 |
| *** bongo <bongo!~bnogo@38.97.94.98> has joined #yocto | 18:29 | |
| *** bradfa <bradfa!~andrew@clr-vpn01.kodakalaris.com> has quit IRC | 18:29 | |
| davis | i did a diff of my tree and the only thing I see is meta-yocto-bsp/recipes-bsp/formfacotor/beagleboard/machconfig has an entry for HAVE_TOUCHSCREEN=1 instead of 0 | 18:30 |
| davis | but that does not sound like a ubi file system issue | 18:31 |
| *** silviof <silviof!~silviof@unaffiliated/silviof> has joined #yocto | 18:31 | |
| davis | is there a command for bitbake which does a check to see if files are valid? | 18:34 |
| kergoth | OT, quick prototype of prefixing task log messages with the recipe/task they came from: https://gist.github.com/kergoth/50af1ca12692d39f0338 - haven't decided if that'd be better in a subclass of the log formatter rather than directly modifying the message in the ui main loop, though | 18:34 |
| davis | or at least removes the .lock files? maybe they are stale and causing a problem. i don't know but it seems odd that it no longer would work. | 18:35 |
| kergoth | if the lock file was stale, the build wouldn't even begin | 18:36 |
| davis | ahh | 18:37 |
| *** jmpdelos <jmpdelos!~polk@delos.delosent.com> has quit IRC | 18:37 | |
| davis | i opened a new terminal, reran the init script and I'm trying to build it again. its on task 5039 of 5041 | 18:37 |
| davis | looking at ps, it seems to be building various archives. at first i saw jffs, then tar | 18:40 |
| *** jmpdelos <jmpdelos!~polk@delos.delosent.com> has joined #yocto | 18:40 | |
| davis | then it failed again on create_image.ubifs | 18:40 |
| davis | what is ubifs used for? | 18:41 |
| davis | uboot? | 18:41 |
| davis | if I take it out of the conf/local.conf file maybe it will work | 18:42 |
| *** pohly <pohly!~pohly@p5DE8CA2B.dip0.t-ipconnect.de> has quit IRC | 18:46 | |
| *** dryawgmoth <dryawgmoth!~varx@173.200.77.82> has quit IRC | 18:49 | |
| *** bradfa <bradfa!~andrew@clr-vpn01.kodakalaris.com> has joined #yocto | 18:50 | |
| *** dlerner <dlerner!~dlerner@50-198-55-145-static.hfc.comcastbusiness.net> has left #yocto | 18:53 | |
| davis | interesting. I removed the ubi specification from local.conf and my old custom image built | 18:53 |
| davis | so i'm back where i started. | 18:53 |
| davis | since the whole oe versions rabbit hole did not work. How would a newbie go at enabling the lcd on a beagleboard? | 18:54 |
| davis | i have this meta-beagleboard-kernel from Robert. it has a recipes-kernel with a .bb file and a defconfig but no conf/layer.conf. | 18:57 |
| davis | could I stick this in my recipes-kernel dir and enable it? | 18:57 |
| *** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has quit IRC | 18:58 | |
| fray | https://github.com/beagleboard/meta-beagleboard | 18:59 |
| fray | in the original meta-beagleboard.. the 'common-bsp- was the layer | 18:59 |
| fray | I haven't used a beagleboard in a long time though, so I have no idea what is correct or current | 18:59 |
| *** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has joined #yocto | 19:00 | |
| davis | hmm. i don't understand. | 19:01 |
| fray | the git repository 'meta-beagleboard' has a directory in it called 'common-bsp'. That is the layer that would be added to yoru bblayers entry.. | 19:01 |
| davis | i see that meta and meta-yocto-bsp both have a recipes-kernel | 19:01 |
| *** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has quit IRC | 19:01 | |
| fray | I don't know of any other beagleboard layers, but that one is fairly old.. so it's likely not correct | 19:01 |
| davis | this guy Robert, seems like he is a guy who is knowledable was kind enough to give me a recipes-kernel tree | 19:02 |
| fray | I don't know anything about that work.. sorry | 19:02 |
| davis | i think he was assuming I would know how to plug it in to my existing tree | 19:03 |
| *** thaytan <thaytan!~thaytan@199.7.70.115.static.exetel.com.au> has quit IRC | 19:03 | |
| davis | i'm thinking if I add the tree in my tree under meta-yocto-bsp perhaps I can select it via a prefered version sting or something | 19:03 |
| fray | that really isn't the right way, but it might work.. I don't know.. | 19:04 |
| davis | hmm. ok lets not do that then | 19:04 |
| fray | this is why the layer mechanism was created so you -never- had to hack on a repository.. | 19:04 |
| fray | you always just add to it, and the addition allows you to replace or amend existing work | 19:04 |
| davis | i'm trying to understand the layer idea | 19:04 |
| davis | he gave me a .bb and defconfig | 19:05 |
| davis | but since its not a layer, I know now I can not add it to my BBLAYERS variable | 19:05 |
| fray | At a minimum, a Yocto Project compliant layer has three things.. a README file, something (might be in the readme) that explains how to use it and contribute back fixes, and a 'conf/layer.conf' file | 19:05 |
| fray | For something that "works" w/ OE, you can skip the readme and contribution info.. | 19:05 |
| davis | this does not have a readme or a conf | 19:05 |
| *** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-arweptmpeeervist> has quit IRC | 19:06 | |
| fray | the conf/layer.conf is quite simple... look at meta-skeleton in your install for an exmaple.. | 19:06 |
| *** Biliogadafr <Biliogadafr!~User@37.44.102.241> has quit IRC | 19:06 | |
| fray | simply copy that.. and change references to 'skeleton' to whatever you want to name your layer | 19:06 |
| davis | so if i copy it, where do I copy it too? | 19:07 |
| fray | the BBFILES entry is the set of wildcards used to find the recipes and bbappends | 19:07 |
| fray | conf/layer.conf | 19:07 |
| fray | mkdir my-new-layer | 19:07 |
| fray | mkdir my-new-layer/conf | 19:07 |
| fray | cp meta-skeleton/conf/layer.conf my-new-layer/conf/. | 19:07 |
| davis | are you saying mkdir at top level? As a peer to meta, meta-yocto and meta-skeleton? | 19:08 |
| fray | <edit> my-new-layer/conf/layer.conf | 19:08 |
| fray | swap references to skeleton to "my-new-layer" | 19:08 |
| fray | make sure BBFILES path matches the layer and directory structure you have choosen for your layer.. | 19:08 |
| fray | thats it | 19:08 |
| fray | you can put it anywhere you want | 19:08 |
| davis | fray you are my hero | 19:08 |
| fray | the BBLAYERS= has the path to the layer | 19:08 |
| fray | (this is all in the Yocto Project manual on creating a layer BTW).. | 19:09 |
| davis | which one? the meta manual? | 19:10 |
| fray | mega manual, Chapter 5. "Common Tasks".. 5.1 Understandign and Creating Layers | 19:11 |
| fray | http://www.yoctoproject.org/docs/1.8/mega-manual/mega-manual.html | 19:11 |
| fray | http://www.yoctoproject.org/docs/1.8/mega-manual/mega-manual.html#understanding-and-creating-layers | 19:11 |
| fray | 'meta-' is a convention BTW for layer names, but not required.. a layer can be called anything that the filesystem allows.. | 19:12 |
| davis | fwiw, that layers.conf has BBFILE_COLLECTIONS +="skeleton" so that should be "my-new-layers" but it also has BBFILE_PATTERN_skeleton would that be BBFILE_PATTERN_my? | 19:12 |
| fray | all of them have to match | 19:13 |
| fray | and be unique within your configuration.. | 19:13 |
| fray | you can't have two layers with the same 'collections' name | 19:13 |
| davis | would you mind looking at a pastebin? | 19:14 |
| fray | I can | 19:14 |
| davis | http://pastebin.com/V8MiDmJt | 19:15 |
| fray | ya, as a minimum that works.. | 19:16 |
| fray | the BBFILES says that your new recipes will be installed into the layerdir/recipes-*/* | 19:16 |
| fray | and be called *.bb and *.bbappend | 19:16 |
| fray | if that is correct you are good.. if you want a different path breakup, you can change the wild cards.. | 19:17 |
| *** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has joined #yocto | 19:17 | |
| fray | the only other thing you might want to change: | 19:18 |
| fray | The BBFILE_PRIORITY variable then assigns a priority to the layer. Applying priorities is useful in situations where the same recipe might appear in multiple layers and allows you to choose the layer that takes precedence. | 19:18 |
| *** challinan <challinan!~chris@173-10-226-189-BusName-WestFlorida.hfc.comcastbusiness.net> has quit IRC | 19:18 | |
| fray | the higher the number the higher the priority.. | 19:18 |
| fray | so if you want to force your layer to have precedence, put it at 100 | 19:18 |
| fray | (or higher) | 19:18 |
| davis | sounds good, i made it 100 | 19:18 |
| fray | the priority only matters say if you have two recipes with the same name in multiple layers.. | 19:19 |
| davis | give me a second to catch up on your instructions | 19:19 |
| fray | (I'm always a little sketchy when it comes to the BBFILE_PRIORITY field.. it's not used all that often in reality) | 19:19 |
| davis | ok so i a tree which looks possibly correct | 19:21 |
| * kergoth has setup scripts that reorder his BBLAYERS by BBFILE_PRIORITY so his recipe priority is aligned with bbclass/conf priority.. need to add a new sub-command to bitbake-layers to do that | 19:21 | |
| *** vmesons <vmesons!~rmacleod@24-212-184-107.cable.teksavvy.com> has joined #yocto | 19:22 | |
| davis | http://pastebin.com/WVW386Qr | 19:22 |
| davis | and I've added it to my BBLAYERS variable | 19:23 |
| *** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has quit IRC | 19:24 | |
| fray | layer format looks fine | 19:24 |
| fray | kergoth, honestly I'm surprised we still have a BBFILE_PRIORITY.. and don't just use the BBLAYERS order | 19:24 |
| davis | i imagine, I need to edit that recipe I used which just completed building to specify the linux-beagleboard.org-4.1 kernel | 19:24 |
| davis | ie vi recipes/images/custom/jfd-image-recipe.bb | 19:25 |
| fray | this is where I don't know.. I don't do many kernel builds | 19:25 |
| fray | but I suspect there is only one 'linux-beagleboard.org' recipe on your system | 19:25 |
| fray | so either it needs to be formatted properly (having the right virtual provide) or you'll have to manually trigger it | 19:26 |
| davis | if I edit that file, it has a bunch of packages which I could enable/disable in hob. ie. kernel-module-libcrc32c, xauth, kernel-module-ppp-generic etc. | 19:26 |
| kergoth | fray: that's what i wanted when i responded to richard's original bblayers implementation, but he strongly felt it should be a variable, iirc. my original "collections" implementation controlled all priority via the order in the COLLECTIONS variable. | 19:26 |
| kergoth | http://git.openembedded.org/openembedded/tree/conf/collections.inc | 19:27 |
| fray | ya, and I'd rather it only be controlled by inclusion order.. ;) | 19:27 |
| davis | doing a search. nothing pops up as beaglebone | 19:27 |
| fray | I don't really like the priority value at all | 19:27 |
| fray | I could see a few cases where we automate the priority during including, and only specify it when necessary | 19:28 |
| kergoth | it was a matter of who owned the knowledge, he thought the layer owner would know better than the user on that, iirc | 19:28 |
| kergoth | but the problem with that is, they don't always know best, and priorities are only useful in context | 19:28 |
| davis | here is not the whole line, but here is where I just added it | 19:28 |
| davis | IMAGE_INSTALL = "linux-beagleboard.org-4.1 kernel-module-nf-conntrack-ipv4 ke | 19:29 |
| fray | kergoth, yup | 19:29 |
| kergoth | i end up overriding the meta-oe priority so it never overrides oe-core | 19:29 |
| fray | IMAGE_INSTALL requires package names, -not- recipe names.. | 19:29 |
| fray | there likely won't be a package named 'linux-beagleboard.org-4.1' | 19:29 |
| davis | cry | 19:30 |
| davis | it did not even get that far | 19:30 |
| davis | ERROR: Unable to parse /home/davis/progs/my-new-layer/conf/layer.conf: file /home/davis/progs/my-new-layer/conf/layer.conf not found | 19:30 |
| fray | verify the file is there at that exact path.. if not.. correct the BBLAYERS | 19:30 |
| davis | yeah, that was a typo | 19:31 |
| *** bongo <bongo!~bnogo@38.97.94.98> has quit IRC | 19:32 | |
| davis | so its not a package name not a recipe name. but maybe with priority it will be used? | 19:32 |
| *** thaytan <thaytan!~thaytan@199.7.70.115.static.exetel.com.au> has joined #yocto | 19:32 | |
| davis | i imaing this will fail but I can edit the jfd-image-recipe2 and remove it. I'm afraid to kill it while its trying to build since I'm afraid it might leave behind files | 19:33 |
| kergoth | interrupting a build is harmless. it'll pick up where it left off | 19:33 |
| davis | ahh, very good | 19:33 |
| davis | WARNING: No bb files matched BBFILE_PATTERN_my-new-layer '^/home/davis/progs/poky/my-new-layer/' | 19:33 |
| davis | NOTE: Resolving any missing task queue dependencies | 19:33 |
| fray | the the pattern listed in BBFILE_PATTERN is wrong.. make sure the pattern works using something like 'ls' and returns files | 19:35 |
| davis | i removed the entry from recipes/images/custom/jfd-image-recipe2.bb and the warning comes back no bb files matched BFILE_PATTERN_MY-new-layer | 19:35 |
| fray | cat your layer.conf.. and from the head of the directory specified in 'bblayers =' verify the pattern | 19:36 |
| davis | ls my-new-layer/recipes-kernel/linux/linux-beagleboard.org_4.1.bb | 19:36 |
| davis | is that what you mean? | 19:36 |
| fray | cd my-new-layer | 19:36 |
| fray | ls recipes-*/*/*.bb | 19:36 |
| fray | did you get a result? | 19:36 |
| fray | ls /recipes-*/*/*.bbappend | 19:36 |
| fray | again get a result? if not fix it | 19:36 |
| davis | yeah, that ls above is what I just did | 19:36 |
| fray | (second one remove leading '/' | 19:37 |
| davis | i just used tab completion | 19:37 |
| fray | kergoth both patterns don't have to match right, just one of them? | 19:37 |
| *** jimBaxter <jimBaxter!~jbaxter@jimbax.plus.com> has quit IRC | 19:37 | |
| davis | BBLAYES has /home/davis/progs/poky/my-new-layer | 19:38 |
| kergoth | yeah, as long as anything matches it'll shut it up | 19:38 |
| fray | so something si wrong.. | 19:38 |
| fray | ls /home/davis/progs/poky/my-new-layer/recipes-*/*/*.bb | 19:38 |
| fray | ls /home/davis/progs/poky/my-new-layer/recipes-*/*/*.bbappend | 19:38 |
| fray | one of those needs a match.. if it matches, I don't know | 19:38 |
| davis | i only have one bb file | 19:39 |
| fray | doesn't matter.. the pattern has to match.. it's globbed.. so a simple 'ls' with the path should show you if the glob is right or not | 19:39 |
| davis | it is my-new-layer/recipes-kernel/linux/linux-beagleboard.org_4.1.bb | 19:39 |
| davis | that appears to match to me | 19:40 |
| fray | well, the error is saying that the system didn't find anything matching the glob | 19:40 |
| fray | you'll have to figure out why | 19:40 |
| davis | i think this is key | 19:41 |
| davis | No bb files matched BBFILE_PATTERN_my-new-layer | 19:41 |
| fray | yes.. | 19:41 |
| davis | the original was of the form BBFILE_PATTERN_skeleton | 19:41 |
| fray | the system collections everything from BBFILES into a big list (or pathnames based on globs) | 19:41 |
| davis | yet it was meta-skeleton | 19:41 |
| fray | it then looks at BBFILE_PATTERN_<collection> and matches that pattern against the overall file list | 19:41 |
| fray | "^${LAYERDIR}/" | 19:41 |
| fray | that says that at least ONE file found must start with the path to the layer directory'/' | 19:42 |
| fray | the error is saying that no files were found that match that pattern.. | 19:42 |
| fray | LAYERDIR is the immediate directory of the layer as specified by BBLAYERS = when processing.. it's evaluated immediately not not stored as "LAYERDIR", but as the evaluated value | 19:43 |
| davis | if I take the error message and copy and paste it, it shows the conf and recipes-kernel dir | 19:43 |
| fray | pastebin it then | 19:43 |
| davis | the error says no bb file matched | 19:43 |
| davis | the bb file is in the recipes-kernel subdir and not at that level | 19:43 |
| davis | i'll pastebin it | 19:43 |
| davis | http://pastebin.com/kWb5uRAW | 19:44 |
| fray | that doesn't show the error | 19:45 |
| davis | one sec ill generate it again | 19:46 |
| davis | http://pastebin.com/3m2TyE7Y | 19:47 |
| fray | the warning is saying.. that after processing BBFILES, the pattern listed (regex) was NOT found | 19:48 |
| fray | thus no bb files from your "/home/davis/progs/poky/my-new-layer/" were foiund by the system | 19:48 |
| fray | they're found by the globbing in BBFILES | 19:48 |
| fray | you can try bitbake -e , then search the result for 'BBFILES' and see what it was looking for, and verify that something starting with that shows up when you look for globs. | 19:49 |
| *** bongo <bongo!~bnogo@38.97.94.98> has joined #yocto | 19:49 | |
| fray | i.e. | 19:49 |
| fray | BBFILES=" /home/mhatle/git/oss/oe-core/meta/recipes-*/*/*.bb" | 19:49 |
| fray | [mhatle@msp-dhcp23 build]$ ls /home/mhatle/git/oss/oe-core/meta/recipes-*/*/*.bb | wc -l | 19:49 |
| fray | 883 | 19:49 |
| fray | BBFILE_PATTERN_core="^/home/mhatle/git/oss/oe-core/meta/" | 19:50 |
| fray | so we have 883 items that match the 'core' layer pattern.. so I don't get a warning | 19:50 |
| davis | ok | 19:50 |
| davis | lol, i am so lost. omg | 19:51 |
| fray | bitbake -e is like typing 'env' in a shell.. you get everything that is set in the environment.. | 19:51 |
| fray | just pipe it to less and search for 'BBFILES=' | 19:51 |
| fray | you will see all of the BBFILES += ... lines from your layers conf/layer.conf expanded there.. | 19:52 |
| davis | ok bitbake -e | less and then search for my | 19:52 |
| davis | i see /all the .conf files in that tree | 19:53 |
| *** sameo <sameo!samuel@nat/intel/x-yrxuinuhmmwiuxwk> has quit IRC | 19:53 | |
| fray | ignore the lines starting with '#'. These are debug info on how the variable was constructed | 19:53 |
| davis | i see this /home/davis/progs/poky/my-new-layer/recipes-*/*/*.bb | 19:53 |
| davis | and if I use that at prompt like so, ls /home/davis/progs/poky/my-new-layer/recipes-*/*/*.bb | 19:54 |
| fray | that is glob that you should be able to check if it expect | 19:54 |
| davis | i see the linux-beagleboard.orgxxxx.bb file | 19:54 |
| fray | I don't know then.. | 19:54 |
| davis | same here | 19:55 |
| fray | the system it telling you it didn't find it.. | 19:55 |
| fray | bitbake -DDDDDD might show you way more then you want | 19:55 |
| fray | you should be able to watch it evaluate everything | 19:56 |
| davis | do i need to resource the script? | 19:57 |
| *** bongo <bongo!~bnogo@38.97.94.98> has quit IRC | 19:57 | |
| fray | no.. just add -DDDDD to your bitbake call | 19:57 |
| fray | (each -D adds more debugging) | 19:57 |
| *** bongo <bongo!~bnogo@38.97.94.98> has joined #yocto | 19:57 | |
| fray | it wouldn't surprise me if it was something like the '.' in the name that wasn't allowed.. | 19:58 |
| *** adelcast <adelcast!~adelcast@130.164.62.82> has joined #yocto | 19:58 | |
| davis | hmm. it says debug:exclude form world a bunch of times and then parsing complete and then warning, no bb files matched BBFILE_PATTERN_my-new-layer | 19:59 |
| davis | at top it says DEBUG: Adding layer /home/davis/progs/poky/my-new-layer | 20:00 |
| *** afxez0r <afxez0r!afxez0r@nat/intel/x-byzlogofhzlpdrga> has quit IRC | 20:01 | |
| davis | it seems to be it wants a .bb file in the root of my-new-layer | 20:01 |
| fray | add -s | 20:01 |
| davis | but poky/meta does not ahve a .bb file | 20:02 |
| fray | doesn't matter.. you are providing your own | 20:02 |
| fray | adding -s will also show you everything it did find | 20:02 |
| davis | same thing. WARNING: No bb files matched BBFILE_PATTERN_my-new-layer '^/home/davis/progs/poky/my-new-layer/' | 20:05 |
| *** nighty^ <nighty^!~nighty@hokuriku.rural-networks.com> has quit IRC | 20:06 | |
| davis | that message means its literally not finding the dir, right? | 20:07 |
| fray | yes | 20:08 |
| fray | but since your conf/layer.conf was loaded it found the dir, but not the recipe(s) inside the dir.. | 20:08 |
| davis | im comparing the my-new-layer and meta-skeleton | 20:08 |
| fray | just on a wild change, rename the recipe and get rid of the beagleboard.org piece.. call it something like linux-beagleboard_4.1.bb | 20:09 |
| davis | both have a conf/layer.conf | 20:09 |
| davis | but have a recipes-kernel | 20:09 |
| davis | as a peer to conf dir | 20:09 |
| davis | only diff is in that recipes-kernel the dirs/filenames inside differ in form | 20:10 |
| davis | linux/linux-yocto-cutom and linux/linux-yocot-custom.bb vs linux-beagleboard.org_4.1 | 20:11 |
| davis | maybe I sould rename it to linux-beagleboard.bb | 20:11 |
| fray | recipe filenaems are: <recipe name>_<recipe version>.bb | 20:12 |
| fray | the _<recipe version> is optional | 20:12 |
| fray | so the way it's currently named "linux-beagleboard.org" is the name.. and I'm wondering if the '.' isn't allowed.. | 20:12 |
| davis | the one with custom.bb has a . in it | 20:13 |
| davis | i wonder if the recipe name must have my-new-layer in it | 20:15 |
| fray | no it shouldn't | 20:17 |
| davis | hmm | 20:20 |
| davis | i noticed a naming convention error | 20:20 |
| *** RP <RP!~richard@192.55.54.60> has joined #yocto | 20:21 | |
| *** afxez0r <afxez0r!afxez0r@nat/intel/x-zmdrudlqtwelmduz> has joined #yocto | 20:21 | |
| davis | arc linux-beagleboard.org-4.1 linux-beagleboard.org-4.1.bb | 20:21 |
| davis | i made it so that the .bb file had the same pattern as the dir | 20:21 |
| davis | the original had a _ in one and a - in the other | 20:22 |
| davis | however that did not fix the problem | 20:22 |
| davis | WARNING: No bb files matched BBFILE_PATTERN_my-new-layer '^/home/davis/progs/poky/my-new-layer/' | 20:22 |
| davis | i don't get it. i can literraly copy and paste that string excluding the leading ^ and I see the layer | 20:22 |
| davis | and the subdir pattern matches the meta-skeleton path | 20:23 |
| *** jjmb <jjmb!~jjmb@50-204-55-34-static.hfc.comcastbusiness.net> has joined #yocto | 20:33 | |
| fray | I've replicated your problem here.. | 20:34 |
| *** afxez0r <afxez0r!afxez0r@nat/intel/x-zmdrudlqtwelmduz> has quit IRC | 20:40 | |
| *** psnsilva <psnsilva!~psnsilva@94.60.92.31> has joined #yocto | 20:42 | |
| fray | ok.. I've verified inside of bitbake, it never loaded the recipe.. | 20:44 |
| fray | now to figure out why | 20:44 |
| fray | BINGO | 20:48 |
| fray | I know what the problem was! the item (I was testing with) was broken.. so the system was ignoring it intentionally | 20:48 |
| fray | when I did 'bitbake linux-yocto-custom' I get a reasonable eror: | 20:49 |
| fray | ERROR: Nothing PROVIDES 'linux-yocto-custom' | 20:49 |
| fray | ERROR: linux-yocto-custom was skipped: We shouldn't have multilib variants for the kernel | 20:49 |
| fray | ERROR: linux-yocto-custom was skipped: incompatible with machine qemumips64 (not in COMPATIBLE_MACHINE) | 20:49 |
| fray | ERROR: linux-yocto-custom was skipped: We shouldn't have multilib variants for the kernel | 20:49 |
| fray | on your system try bitbake linux-beagleboard.org | 20:49 |
| fray | see if you get an error like above.. | 20:49 |
| fray | if so, the recipe doesn't work, so it was being ignored.. which is why the warning was being issued.. | 20:49 |
| fray | (I'd say there is a bug in the warning then.. it shouldn't kick the warning if it loaded something, even if it was disabled) | 20:50 |
| kergoth | huh, interesting | 20:50 |
| fray | ya.. that explains the problem.. but confusing as hell | 20:50 |
| *** bongo <bongo!~bnogo@38.97.94.98> has quit IRC | 20:54 | |
| *** bongo <bongo!~bnogo@38.97.94.98> has joined #yocto | 20:54 | |
| kergoth | yep | 20:56 |
| *** bongo <bongo!~bnogo@38.97.94.98> has quit IRC | 20:56 | |
| *** bongo <bongo!~bnogo@38.97.94.98> has joined #yocto | 20:56 | |
| davis | sorry i was in a meeting | 20:58 |
| davis | i'm back | 20:58 |
| *** bongo <bongo!~bnogo@38.97.94.98> has quit IRC | 20:59 | |
| kergoth | Hmmm, not sure if I'll be able to implement shallow clones without enhancing the fetcher core, since I want to try fetching a shallow tarball and then fall back to trying to fetch a normal git tarball, and there's only one field of the urldata for the tarball filename/path, not a list of them | 20:59 |
| * kergoth ponders | 20:59 | |
| davis | davis@yoshi:~/progs/poky/build$ bitbake linux-beaglebone.org | 20:59 |
| davis | gives same error as before | 20:59 |
| *** bongo <bongo!~bnogo@38.97.94.98> has joined #yocto | 20:59 | |
| davis | WARNING: No bb files matched BBFILE_PATTERN_my-new-layer '^/home/davis/progs/poky/my-new-layer/' | 20:59 |
| davis | and then | 20:59 |
| davis | ERROR: Nothing PROVIDES 'linux-beaglebone.org'. Close matches: | 21:00 |
| davis | ahh, typo | 21:00 |
| davis | ERROR: linux-beagleboard.org-4.1 was skipped: incompatible with machine beaglebone (not in COMPATIBLE_MACHINE) | 21:01 |
| fray | davis no there ya go.. | 21:01 |
| davis | beagleboard not beaglebone | 21:01 |
| fray | it DID read it.. the recipe is missing stuff.. so the item was skipped because it was broken | 21:01 |
| fray | so same thing I found here.. | 21:01 |
| davis | ahh | 21:01 |
| fray | so there is likely a bug (or something) in the WARNING.. but the recipe was loaded and the layer was generated properly | 21:01 |
| davis | compatible machine in the new .bb file is ti33x|ti43x|omap.. etc | 21:03 |
| davis | but at top level, my layers.conf is beaglebone | 21:03 |
| fray | ya, I have no idea at this point.. I don't do kernel work normally | 21:03 |
| davis | so is that the problem? | 21:03 |
| fray | probably.. the MACHINE setting in layers.conf and the kernel recipe must match as to what is supported, or it will disable the configuration | 21:04 |
| davis | i just added beaglebone to the list of ORs | 21:04 |
| davis | and it went to next step which failed for parsing the hit | 21:05 |
| *** bongo <bongo!~bnogo@38.97.94.98> has quit IRC | 21:05 | |
| *** mago_ <mago_!~mago@88.131.56.168> has quit IRC | 21:05 | |
| davis | Invalid protocol - if you wish to fetch from a git repository using http, you need to instead use the git:// prefix with protocol=http | 21:06 |
| davis | i tweaked that up a bit. at least it seems to be doing a pull | 21:10 |
| *** benjamirc <benjamirc!besquive@nat/intel/x-wezjqeraflhhuwvj> has quit IRC | 21:12 | |
| davis | fray, what is your address? i'll send you a postcard. I appreciate your help immensely | 21:13 |
| *** bongo <bongo!~bnogo@38.97.94.98> has joined #yocto | 21:18 | |
| *** afxez0r <afxez0r!~afxez0r@134.134.139.70> has joined #yocto | 21:24 | |
| *** dlerner <dlerner!~dlerner@50-198-55-145-static.hfc.comcastbusiness.net> has joined #yocto | 21:29 | |
| *** sameo <sameo!~samuel@192.55.54.36> has joined #yocto | 21:44 | |
| *** paulg <paulg!~paulg@72.1.195.9> has quit IRC | 21:59 | |
| *** afxez0r <afxez0r!~afxez0r@134.134.139.70> has quit IRC | 21:59 | |
| *** bfederau <bfederau!~quassel@service.basyskom.com> has quit IRC | 22:01 | |
| *** bfederau <bfederau!~quassel@service.basyskom.com> has joined #yocto | 22:01 | |
| *** tsramos_ <tsramos_!tsramos@nat/intel/x-vewiwxkyfwdzlzry> has joined #yocto | 22:07 | |
| *** tsramos <tsramos!tsramos@nat/intel/x-pfrzhvxkpsblbyeo> has quit IRC | 22:10 | |
| *** roxell <roxell!~roxell@linaro/roxell> has quit IRC | 22:11 | |
| *** tsramos_ <tsramos_!tsramos@nat/intel/x-vewiwxkyfwdzlzry> has quit IRC | 22:11 | |
| *** roxell <roxell!~roxell@linaro/roxell> has joined #yocto | 22:18 | |
| *** dv__ is now known as dv_ | 22:18 | |
| *** dlerner <dlerner!~dlerner@50-198-55-145-static.hfc.comcastbusiness.net> has left #yocto | 22:23 | |
| *** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has quit IRC | 22:24 | |
| *** psnsilva <psnsilva!~psnsilva@94.60.92.31> has joined #yocto | 22:28 | |
| *** jjmb <jjmb!~jjmb@50-204-55-34-static.hfc.comcastbusiness.net> has quit IRC | 22:37 | |
| *** benjamirc <benjamirc!~besquive@134.134.137.73> has joined #yocto | 22:47 | |
| *** RP <RP!~richard@192.55.54.60> has quit IRC | 23:00 | |
| *** lamego <lamego!~lamego@134.134.139.70> has quit IRC | 23:03 | |
| *** mago_ <mago_!~mago@88.131.56.168> has joined #yocto | 23:05 | |
| *** sameo <sameo!~samuel@192.55.54.36> has quit IRC | 23:06 | |
| *** bongo <bongo!~bnogo@38.97.94.98> has quit IRC | 23:10 | |
| *** benjamirc <benjamirc!~besquive@134.134.137.73> has quit IRC | 23:11 | |
| *** miandonmenmian_ <miandonmenmian_!~miandonme@210.22.153.182> has quit IRC | 23:15 | |
| *** sjolley <sjolley!sjolley@nat/intel/x-ttywhbdqgjkqshlv> has quit IRC | 23:16 | |
| *** miandonmenmian_ <miandonmenmian_!~miandonme@210.22.153.182> has joined #yocto | 23:17 | |
| *** madisox <madisox!~madison@64-71-1-115.static.wiline.com> has quit IRC | 23:27 | |
| *** fitzsim <fitzsim!~user@2001:420:284a:1300:6e0b:84ff:fe09:4e9f> has quit IRC | 23:31 | |
| *** fitzsim` <fitzsim`!~user@2001:420:284a:1300:6e0b:84ff:fe09:4e9f> has joined #yocto | 23:31 | |
| *** ntl <ntl!~ntl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has quit IRC | 23:42 | |
| *** sjolley <sjolley!~sjolley@134.134.137.71> has joined #yocto | 23:45 | |
| *** ntl <ntl!~ntl@99-127-51-4.lightspeed.austtx.sbcglobal.net> has joined #yocto | 23:55 | |
Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!