Tuesday, 2016-01-26

*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has quit IRC00:16
*** sameo <sameo!~samuel@> has quit IRC00:18
*** alimon1 <alimon1!~alimon@> has quit IRC00:20
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has joined #yocto00:20
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC00:26
*** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has joined #yocto00:27
*** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has quit IRC00:27
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto00:27
*** ant_home <ant_home!~ant__@host48-23-dynamic.14-87-r.retail.telecomitalia.it> has quit IRC00:28
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has quit IRC00:28
*** sgw_ <sgw_!~sgw_@75-136-2-98.static.jcsn.tn.charter.com> has joined #yocto00:36
yann|workI'm puzzled by the lack of a cortexa7hf-neon-vfpv3 (or even cortexa7hf-vfp-neon) tuning that would seem suitable for Allwinner H3 - and just attempting to define it by cut'n'paste yields a strange "does not contain TUNE_PKGARCH (${ARMPKGARCH_tune-cortexa7hf-neon-vfpv3}hf-vfp-vfpv3-neon)", what am I missing ?00:40
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has joined #yocto00:41
yann|workhm, "neon" seems to imply simple "vfp", at least00:41
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has quit IRC00:54
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has joined #yocto00:55
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has quit IRC01:04
*** paulg_ <paulg_!~paulg@198-84-239-75.cpe.teksavvy.com> has quit IRC01:05
*** aratiu <aratiu!~adi@> has quit IRC01:06
*** aratiu <aratiu!~adi@> has joined #yocto01:07
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has joined #yocto01:09
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has quit IRC01:16
*** ajtag <ajtag!~ajtag@cpc10-lee211-2-0-cust124.7-1.cable.virginm.net> has quit IRC01:25
*** fledermaus <fledermaus!~vivek@pakora.collabora.co.uk> has quit IRC01:32
*** slips <slips!~slips@> has quit IRC01:35
*** slips <slips!~slips@> has joined #yocto01:37
*** SoylentYellow <SoylentYellow!~SoylentYe@207-114-172-147.static.twtelecom.net> has quit IRC02:02
nerdboyyann|work: the tune files could probably be tuned better in some cases02:17
nerdboythe definitions are mostly there; what does your build output say?02:17
nerdboyif you're thinking of flags like neon-vfpv4, fpv5-d16, or even vfpv3xd-fp16, then you need to hack it in02:18
nerdboycat just ran in the house with a twitching gopher in her mouth...02:21
nerdboyolder son (the zooligist) is "handling" it02:21
nerdboyendless fun at my house...02:22
*** dreyna4529 <dreyna4529!~dreyna@unknown-216-203.windriver.com> has quit IRC02:28
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC02:31
*** geheimnis` <geheimnis`!~geheimnis@> has quit IRC03:08
*** geheimnis` <geheimnis`!~geheimnis@> has joined #yocto03:10
*** dreyna4529 <dreyna4529!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto03:14
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto03:28
smurrayIt looks like https://www.yoctoproject.org/documentation/active is out of date, should be pointing at 1.8.1, 1.7.3, 1.6.3 not 1.7.2, 1.6.3, 1.5.4...03:34
*** caiortp <caiortp!~caiortp@189-83-1-39.user.veloxzone.com.br> has joined #yocto03:52
*** behanw <behanw!~behanw@2001:470:b26c:0:e4b8:d724:1476:2f70> has joined #yocto04:13
*** caiortp <caiortp!~caiortp@189-83-1-39.user.veloxzone.com.br> has quit IRC04:35
*** dreyna4529 <dreyna4529!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has quit IRC05:26
*** hamis_lt_u <hamis_lt_u!~irfan@> has joined #yocto05:58
*** aehs29 <aehs29!~aehernan@> has quit IRC06:23
*** denix <denix!~denix@pool-100-15-86-14.washdc.fios.verizon.net> has quit IRC06:39
*** denix0 <denix0!~denix@pool-100-15-86-14.washdc.fios.verizon.net> has joined #yocto06:39
*** denix0 is now known as denix06:39
*** pohly <pohly!~pohly@p57A56B97.dip0.t-ipconnect.de> has joined #yocto06:50
*** marek_ <marek_!~marek@> has joined #yocto07:00
*** Mylene <Mylene!~Mylene@204.ip-51-254-215.eu> has joined #yocto07:08
*** frsc <frsc!~frsc@> has joined #yocto07:20
*** b00^wk2 <b00^wk2!~dry@port-92-196-110-20.dynamic.qsc.de> has joined #yocto07:23
*** joshuagl <joshuagl!~joshuagl@> has joined #yocto07:32
*** yann|work <yann|work!~yann@nan92-1-81-57-214-146.fbx.proxad.net> has quit IRC07:38
*** morphis <morphis!~morphis@pD9ED7EFB.dip0.t-ipconnect.de> has joined #yocto07:38
frscHas someone got a solution for this: https://community.freescale.com/thread/382912 ?07:42
*** mckoan|away is now known as mckoan07:42
*** raykinsella78 <raykinsella78!~rkinsell@> has joined #yocto07:43
frscIm experiencing the same error when building linux-fslx-mx6 within Yocto07:43
*** raykinsella78 <raykinsella78!~rkinsell@> has left #yocto07:46
*** csanchezdll <csanchezdll!~user@galileo.kdpof.com> has joined #yocto07:53
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-jeoftigvtxryicmw> has joined #yocto07:56
*** jbrianceau_away is now known as jbrianceau07:56
*** belen <belen!~Adium@> has joined #yocto08:00
*** t0mmy <t0mmy!~tprrt@> has joined #yocto08:04
*** fl0v0 <fl0v0!~fvo@p5DDC5481.dip0.t-ipconnect.de> has joined #yocto08:05
*** raykinsella78 <raykinsella78!~rkinsell@> has joined #yocto08:07
*** AndersD <AndersD!~anders@h83-209-191-235.dynamic.se.alltele.net> has joined #yocto08:08
*** townxelliot <townxelliot!~ell@> has joined #yocto08:10
*** raykinsella78 <raykinsella78!~rkinsell@> has left #yocto08:11
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto08:13
*** belen <belen!~Adium@> has quit IRC08:13
*** belen <belen!Adium@nat/intel/x-odivdplwcyiztpxb> has joined #yocto08:13
*** belen <belen!Adium@nat/intel/x-odivdplwcyiztpxb> has quit IRC08:20
*** AndersD <AndersD!~anders@h83-209-191-235.dynamic.se.alltele.net> has quit IRC08:24
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has joined #yocto08:25
*** diego_r <diego_r!~diego@> has joined #yocto08:26
mckoanfrsc: what did you do between git clone and make imx_v7_defconfig ?08:29
*** grma <grma!~gruberm@> has joined #yocto08:32
mckoanfrsc: I added a comment to that post thread08:34
frscmckoan: I'm not building for mx7d, but for mx6s and I'm using 3.14-1.1.x-mx6 branch from linux-fslc. Also I'm using the Yocto-recipes to build.08:36
*** belen <belen!~Adium@> has joined #yocto08:41
nerdboydid anyone submit an snmp patch for jethro yet?08:44
*** maxin <maxin!~maxin@> has joined #yocto08:46
mckoanfrsc: it works08:46
*** yann|work <yann|work!~yann@LFbn-1-1026-146.w86-247.abo.wanadoo.fr> has joined #yocto08:48
*** vdehors_ <vdehors_!~vdehors@bob75-2-81-56-46-209.fbx.proxad.net> has quit IRC08:49
*** heliocastro is now known as helio|afk08:51
*** sameo <sameo!~samuel@> has joined #yocto08:53
*** vdehors <vdehors!~vdehors@> has joined #yocto08:56
nerdboythat's right, the patch file was there but it was never applied in jethro08:56
*** helio|afk is now known as heliocastro08:57
* nerdboy has a slightly more flexible/comprehensive patch for jethro08:58
yann|worknerdboy: with http://pastebin.com/rNVBHdEN the exact error is http://pastebin.com/MSHSGqh108:59
nerdboyapparently you're doing it wrong09:02
* nerdboy is nothing if not observant and helpful09:02
nerdboyi had to play with it a bit to get the rpi tuning i wanted09:03
nerdboyall i can say is trace the includes and find the right place to modify it09:03
* nerdboy does a lot of custom flags and there are lots of combinations that work09:04
nerdboyiirc it should default to softfp with the tuning it thinks is correct for your machine09:05
nerdboyit depends on bsp tune config, rpi started out kinda basic09:05
nerdboyit looks like you have an extra vfp- in there09:06
nerdboyhard to tell sometimes with all the variable substitution and include files09:07
* nerdboy still tired from 4 days of scale...09:08
*** roccof <roccof!~roccof@93-51-177-218.ip268.fastwebnet.it> has joined #yocto09:10
yann|workwell, I did trace the includes to find something roughly comparable to use as a base, but will apparently have to dig more to find out which variable is botched:)09:14
*** aragua <aragua!~flahouder@2a01:6600:8083:4700:206:5bff:fe9d:9d11> has joined #yocto09:16
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has quit IRC09:16
yann|workwell, in fact the H3 supports vfpv4, so the but won't impact me anyway, I'll just for hunt it later :)09:19
CTtpollardyann|work: renesas h3?09:21
*** aragua <aragua!~flahouder@2a01:6600:8083:4700:206:5bff:fe9d:9d11> has quit IRC09:22
yann|workno, allwinner h309:22
CTtpollardah, cool09:24
*** TobSnyder <TobSnyder!~schneider@ip923450f2.dynamic.kabel-deutschland.de> has joined #yocto09:28
*** jku <jku!~jku@d804tyxzqsj--98wl3k-3.rev.dnainternet.fi> has joined #yocto09:29
frscmckoan: it doesn't work for me. I exactly followed your steps from the nxp thread, also using the jethro toolchain...09:30
*** Biliogadafr <Biliogadafr!~User@nat2-minsk-pool-46-53-195-225.telecom.by> has joined #yocto09:32
*** ant_work <ant_work!~ant__@> has joined #yocto09:32
*** aragua <aragua!~flahouder@2a01:6600:8083:4700:206:5bff:fe9d:9d11> has joined #yocto09:33
aratiuI'm getting this error while building gcc-4.9.2 "libgcc/gthr.h:148:26: fatal error: gthr-default.h: No such file or directory"09:34
aratiuif I symlink the gthr-posix.h to gthr-default.h the build works09:34
aratiusomehow the ghtr-default.h is not generated automatically09:34
aratiuany ideas?09:34
*** edbart <edbart!ebartosh@nat/intel/x-vnpfdkpcmzssppdo> has joined #yocto09:35
*** aragua <aragua!~flahouder@2a01:6600:8083:4700:206:5bff:fe9d:9d11> has quit IRC09:44
*** csanchezdll <csanchezdll!~user@galileo.kdpof.com> has quit IRC09:46
*** aragua <aragua!~flahouder@2a01:6600:8083:4700:206:5bff:fe9d:9d11> has joined #yocto09:49
*** matteo <matteo!~matteo@openwrt/developer/matteo> has joined #yocto09:50
*** Crofton <Crofton!~balister@> has quit IRC09:52
*** grma <grma!~gruberm@> has quit IRC09:54
*** matteo <matteo!~matteo@openwrt/developer/matteo> has quit IRC09:56
*** grma <grma!~gruberm@> has joined #yocto09:57
*** matteo <matteo!~matteo@openwrt/developer/matteo> has joined #yocto09:58
*** nighty^ <nighty^!~nighty@s229123.ppp.asahi-net.or.jp> has left #yocto10:01
*** Dilebo is now known as ftoulemon10:03
*** jonathanmaw <jonathanmaw!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has joined #yocto10:04
*** toscalix <toscalix!~agustinbe@> has joined #yocto10:13
*** rburton <rburton!~Adium@> has joined #yocto10:14
*** Crofton <Crofton!~balister@echelon.c-base.org> has joined #yocto10:17
mckoanfrsc: please pastebin your output of : arm-poky-linux-gnueabi-gcc -v10:20
frscmckoan: http://paste.ubuntu.com/14670927/10:23
*** kjokinie1 <kjokinie1!~kjokinie@> has quit IRC10:29
*** aratiu <aratiu!~adi@> has quit IRC10:30
mckoanfrsc: shoud be Target: arm-poky-linux-gnueabi10:30
*** aratiu <aratiu!~adi@> has joined #yocto10:30
mckoanfrsc: you have Target: arm-exceet-linux-gnueabi10:30
frscmckoan: I use a custom distro config "exceet", but it's not much different from poky10:31
mckoanfrsc: looks like that is the only difference, thus the cause10:32
frscmckoan: might be, I'll investigate. Thanks nevertheless!10:32
*** jku <jku!~jku@d804tyxzqsj--98wl3k-3.rev.dnainternet.fi> has quit IRC10:33
*** jku <jku!~jku@d804tyxzqsj--98wl3k-3.rev.dnainternet.fi> has joined #yocto10:33
*** kjokinie <kjokinie!~kjokinie@> has joined #yocto10:35
*** morphis <morphis!~morphis@pD9ED7EFB.dip0.t-ipconnect.de> has quit IRC10:38
*** morphis <morphis!~morphis@pD9ED7EFB.dip0.t-ipconnect.de> has joined #yocto10:45
*** toscalix <toscalix!~agustinbe@> has quit IRC10:48
*** clopez <clopez!~tau@neutrino.es> has quit IRC10:49
*** berton <berton!~fabio@> has joined #yocto10:52
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC11:01
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC11:04
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto11:04
*** belen <belen!~Adium@> has quit IRC11:06
*** belen <belen!~Adium@> has joined #yocto11:06
*** belen <belen!~Adium@> has quit IRC11:11
*** belen <belen!~Adium@> has joined #yocto11:11
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC11:11
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto11:13
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has joined #yocto11:21
*** dreyna4529 <dreyna4529!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto11:23
*** fl0v01 <fl0v01!~fvo@p5DDC5387.dip0.t-ipconnect.de> has joined #yocto11:23
*** fl0v0 <fl0v0!~fvo@p5DDC5481.dip0.t-ipconnect.de> has quit IRC11:26
*** dreyna4529 <dreyna4529!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has quit IRC11:27
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has quit IRC11:31
*** edbart <edbart!ebartosh@nat/intel/x-vnpfdkpcmzssppdo> has quit IRC11:40
*** blueness <blueness!~blueness@gentoo/developer/blueness> has quit IRC11:41
*** igor1 <igor1!~Igor_Stop@> has quit IRC11:42
*** igor1 <igor1!~Igor_Stop@> has joined #yocto11:43
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has joined #yocto11:46
*** ant_work <ant_work!~ant__@> has quit IRC11:49
*** matteo__ <matteo__!~matteo@93-57-16-194.ip162.fastwebnet.it> has joined #yocto11:52
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has quit IRC11:52
*** matteo__ <matteo__!~matteo@93-57-16-194.ip162.fastwebnet.it> has quit IRC11:52
*** matteo__ <matteo__!~matteo@openwrt/developer/matteo> has joined #yocto11:52
*** matteo is now known as Guest9438711:53
b00^wk2are recipes written in Python in Yocto?11:54
*** matteo__ is now known as matteo11:54
b00^wk2BitBake parses basically Python scripts, or python like scripts ..?11:54
*** Guest94387 <Guest94387!~matteo@openwrt/developer/matteo> has quit IRC11:54
*** ant_work <ant_work!~ant__@> has joined #yocto11:55
*** psnsilva <psnsilva!~psnsilva@193-126-29-154.net.novis.pt> has quit IRC11:56
jkub00^wk2: recipes are collection of metadata with its own syntax. they can contain both python and shell functions11:58
*** psnsilva <psnsilva!~psnsilva@193-126-29-154.net.novis.pt> has joined #yocto11:59
b00^wk2jku, ok  thanks12:00
*** belen <belen!~Adium@> has quit IRC12:00
*** belen <belen!~Adium@> has joined #yocto12:00
b00^wk2err, what's the difference between a metadata and a recipe .. ?12:01
b00^wk2if i'm writing say a config to how to customize my u-boot, is that a recipe?12:01
b00^wk2and can that recipe contain python12:01
*** Crofton <Crofton!~balister@echelon.c-base.org> has quit IRC12:02
*** blueness <blueness!~blueness@gentoo/developer/blueness> has joined #yocto12:06
*** Guest92149 <Guest92149!~vivek@pakora.collabora.co.uk> has joined #yocto12:11
*** fl0v01 <fl0v01!~fvo@p5DDC5387.dip0.t-ipconnect.de> has quit IRC12:14
*** fl0v0 <fl0v0!~fvo@p5DDC5387.dip0.t-ipconnect.de> has joined #yocto12:15
b00^wk2can i have with Yocto to automatically generate say 2 different hw system images?12:21
b00^wk2so that, i don't go first, generate say qemu image, genreate now x86 image, generate arm12:22
b00^wk2if i know that i always need 3 images for different boards, can i put it into my yocto config ?12:22
b00^wk2and can it do all in same yocto root directory ..12:22
CTtpollardb00^wk2: could you not just 3 bitbake processes, and have them share download dir sstate cache etc12:24
b00^wk2i hope so12:24
b00^wk2or asking if one can12:25
CTtpollardyou can do that12:25
b00^wk2CTtpollard, but you have to specially configure this, its not automatically supported in some magic 'default' setup with  > 1 hw target ?12:28
b00^wk2another question :12:28
b00^wk2Also, can you use distributed building with Yocto?  distcc12:28
rburtonit's currently hardcoded that MACHINE is set to one value in each bitbake run12:29
rburtonso if you want to build for multiple machines, run bitbake more than once12:29
b00^wk2rburton, but you can do what CTtpollard suggests, no ?12:30
b00^wk2(3 instances of bitbake, with shared stuff )12:30
rburtonthe yocto autobuilder does that for ~10 machines12:30
b00^wk2ok, and distcc ?12:31
b00^wk2is that option possible12:31
rburtonthere's an icecc class12:31
b00^wk2ok, i have one more question12:32
rburtonthe win isn't as great as you'd expect as it won't spread configure, and that's about 30% of your build time12:32
b00^wk2oh i see12:32
b00^wk2one more question: does Yocto support RFS customization script and RFS overlay12:34
*** Crofton <Crofton!~balister@echelon.c-base.org> has joined #yocto12:42
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has quit IRC12:57
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has joined #yocto12:59
hanthingsHello. How can I restrict a recipe to build only for a specific MACHINE13:01
joshuaglCOMPATIBLE_MACHINE http://www.yoctoproject.org/docs/2.0/ref-manual/ref-manual.html#var-COMPATIBLE_MACHINE13:02
hanthingsjoshuagl, Thanks :)13:03
*** rocsorva <rocsorva!~arnold@> has quit IRC13:06
*** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has quit IRC13:07
*** rocsorva <rocsorva!~arnold@> has joined #yocto13:07
*** aratiu <aratiu!~adi@> has quit IRC13:07
*** aratiu <aratiu!~adi@> has joined #yocto13:08
*** fsdun <fsdun!~fsdun@> has joined #yocto13:10
fsdunmoin. Is it possible to exclude all LGPL* licensed -staticdev packages from packaging?13:11
b00^wk2from where the sources of packages are downloaded from?13:15
b00^wk2does Yocto maintain a big source repo of the soft that goes into images?13:16
CTtpollardb00^wk2: the recipe for the package will list the source13:16
rburtonb00^wk2: wherever the upstream source is13:16
rburtonwe have a mirror in case upstream falls off the internet13:16
rburtoncough directfb cough13:16
b00^wk2is the main source then  / upstream a Yocto source server ?13:16
b00^wk2so its not like many many different URLs from which all different sources are pulled from13:17
rburtonthat's exactly what it is13:17
b00^wk2is that safe ? :)13:17
rburtonyou want gcc, downloads from gnu.org13:17
rburtonthere's checksums to make sure you get what you wanted13:17
*** edbart <edbart!ebartosh@nat/intel/x-pscpaddkbnwxmynz> has joined #yocto13:18
b00^wk2rburton, what is say, after 5 years that url is not valid ? :)13:21
rburtonb00^wk2: then there's the mirrors, and we update stable branches in case URLs change13:21
fsdunand you can create your own mirrors if your product lifetime will exceed the lifetime of yocto's mirrors13:24
b00^wk2fsdun, i know, i was just asking ..13:24
b00^wk2in case :)13:24
b00^wk2(Timesys provide their cloud like service seems, they have all sources that go into factory)13:25
b00^wk2I would mirror it anyway, yocto or not13:25
aratiuyou can just save your downloads dir and move it between builds, mine now is only about 25 gigs13:26
*** csanchezdll <csanchezdll!~user@galileo.kdpof.com> has joined #yocto13:26
rburtonawww mine is only 13G13:26
aratiuyeah I need to clean that13:26
rburtonkernels only go back to 3.16 so i must have pruned at some point13:27
fsdunsourcers: 23G, cached-binaries: 42G13:28
fsdunin < 1 month13:28
rburtonthis is a fun game!13:28
rburtonmy /data is 866G, which is where i do my builds13:28
rburton(616G of sstate)13:29
aratiurburton: no inherit rm_work?13:29
rburtonthe tmp/ doesn't actually last that long13:30
aratiumy poor ssd will cry if I don't rm_work13:30
rburtonget more ram and do builds in tmpfs!13:31
fsdunrburton, do you expereince some issues with tcl/expect using your sstate cache?13:31
rburtonfsdun: literally never knowingly built tcl13:31
rburton(because it's the devil's language)13:31
fsdunI know. but I added ltp which requires tcl13:32
fsdunand I had an issue I'm trying to reproduce while sharing sstate between 2 cortexa15 machines13:33
fsdunit's hard to reproduce, because poky's machines do not share OVERRIDES13:34
*** lamego <lamego!~jose@> has joined #yocto13:35
*** vmeson <vmeson!~rmacleod@> has joined #yocto13:38
*** Guest92149 is now known as fledermaus13:43
*** berton_ <berton_!~fabio@> has joined #yocto13:45
*** psnsilva <psnsilva!~psnsilva@193-126-29-154.net.novis.pt> has quit IRC13:47
*** berton <berton!~fabio@> has quit IRC13:48
*** psnsilva <psnsilva!~psnsilva@193-126-29-154.net.novis.pt> has joined #yocto13:49
*** clopez <clopez!~tau@neutrino.es> has joined #yocto13:58
*** berton_ <berton_!~fabio@> has quit IRC14:00
*** berton <berton!~fabio@> has joined #yocto14:00
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has quit IRC14:05
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has joined #yocto14:06
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has joined #yocto14:08
*** marek_ <marek_!~marek@> has quit IRC14:08
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has quit IRC14:12
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has quit IRC14:13
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has joined #yocto14:13
*** sameo <sameo!~samuel@> has quit IRC14:20
b00^wk2<fsdun> sourcers: 23G, cached-binaries: 42G14:21
b00^wk2yoh !14:21
*** alimon1 <alimon1!~alimon@> has joined #yocto14:22
*** marek_ <marek_!~marek@> has joined #yocto14:23
*** sujith_h <sujith_h!~toaster@kde/developers/sujithh> has joined #yocto14:23
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has joined #yocto14:26
b00^wk2anyone wants to add to my Yocto pros list:  1) Yocto is Open Source, 2) Support for major  CPU and SOC vendors, 3) Better build core (build tools, vs old make, KConfig); 4) support multiple target/ scale well within same project14:29
*** nighty^ <nighty^!~nighty@s229123.ppp.asahi-net.or.jp> has joined #yocto14:30
CTtpollardb00^wk2: are you studying different systems?14:30
b00^wk2comparing vs Timesys Factory14:31
aratiumaybe doing a presentation for management, more likely :) a study would look a lot less dull14:31
b00^wk2ironically to me Timesys is listed as one of members of Yocto14:31
fsdunb00^wk2, can add more packages by adding layers14:31
b00^wk2aratiu, sure, im time limited too :P14:31
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has quit IRC14:31
b00^wk2fsdun, but you can add packages to TS Factory too14:31
b00^wk2with Kconfig way ..14:32
*** mihai <mihai!~mihai@> has joined #yocto14:32
b00^wk2at least I beleive you can , i haven't done it14:32
fsdunb00^wk2, poky is just the core. you cann add more layers for machines/packges/features: http://layers.openembedded.org/layerindex/branch/master/layers/14:32
*** ka6sox is now known as zz_ka6sox14:32
rburtonlooks like Timesys are moving to yocto14:32
rburton"A future release of LinuxLink will be able to encompass both Factory and Yocto build systems, enabling customers to choose which path they want to take."14:33
b00^wk2rburton, i think, they will dump their pet eventually ..14:33
*** zz_ka6sox is now known as Guest754614:33
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has quit IRC14:34
aratiui suspect a lot more companies are in the process of dumping their pets in favor of Yocto14:34
*** mattsm <mattsm!uid128834@gateway/web/irccloud.com/x-rkrjmadnpmgomopz> has quit IRC14:34
b00^wk2rburton, i saw that, and i was just thinking, what is there to LinuxLink except for Factory and Yocto..14:34
b00^wk2aratiu, nice14:34
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has joined #yocto14:34
*** berton <berton!~fabio@> has quit IRC14:34
b00^wk2hey, that UI tool Yocto has, Hob, that is being developed, right?14:34
rburtonhob? not really.  toaster is the replacment.14:35
*** mattsm <mattsm!uid128834@gateway/web/irccloud.com/x-dsvrcorgzbirjhzs> has joined #yocto14:35
aratiuToaster (never actually used it)14:35
* rburton is a shell+emacs man though14:35
b00^wk2ok, but its as user friendly as Hob .. ?14:35
b00^wk2(i used Hob once, looked at it)14:35
b00^wk2for a quick check14:35
aratiurburton: emacs + eshell14:35
rburtonhob was user friendly?14:35
b00^wk2it was all select select select press generate14:36
b00^wk2without knowing really much about configs :)14:36
b00^wk2may be Toaster will let you select all possible Yocto options :)14:36
*** aehs29 <aehs29!~aehernan@> has joined #yocto14:38
*** edbart <edbart!ebartosh@nat/intel/x-pscpaddkbnwxmynz> has quit IRC14:38
*** sameo <sameo!~samuel@> has joined #yocto14:39
*** hamis_lt_u <hamis_lt_u!~irfan@> has quit IRC14:41
*** ant_work <ant_work!~ant__@> has quit IRC14:41
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has joined #yocto14:42
*** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has joined #yocto14:42
*** sjolley <sjolley!~sjolley@> has quit IRC14:44
b00^wk2fsdun, are you here ? :)14:48
*** sjolley <sjolley!sjolley@nat/intel/x-gtmluqyfjrzzrbmr> has joined #yocto14:50
b00^wk2fsdun, wanted to interrogate you a bit more, on why layers in Yocto would allow you to add more packages vs another build system - Timesys Factory14:50
fsdunI never used timesys14:50
fsdune.g. you can add meta-qt5 to get full qt support14:51
fsdunwhich isn't in poky "core"14:51
fsdunyou want a browser -> meta-browser is your friend14:51
b00^wk2fsdun,  on other words, you add 'meta', and it adds all that is required to get qt support14:51
b00^wk2which is alike , package, and old its dependencies14:51
fsdunnot all the dependecies, but if it require external layers it's normally stated in the readme14:52
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has quit IRC14:52
fsdunsometimes without revision to use (HEAD is not a revision)14:52
rburtonqt4 isn't part of oe-core anymore14:53
b00^wk2but now that did give me a point. Timesys has a few pre-selections or templates, but those are probably too few, way below yocto's available layers14:54
b00^wk2so you can start off faster with Yocto, i guess, by not spending time selecting all dependencies, if timesys hasn't done it ..14:54
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has joined #yocto14:59
t0mmy# Anybody would it what is the best solution to add Linux capabilities to a binary file for a recipe ?15:00
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has quit IRC15:05
Ulfalizeri remember hearing something about a script for checking that a package compiles standalone, regardless of what the current sysroot contents from previous builds happens to be. does anyone know what i'm talking about?15:14
Ulfalizeri'm only aware of the manual method that involves (temporarily) throwing away tmp/15:14
*** berton <berton!~fabio@> has joined #yocto15:15
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has quit IRC15:16
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has joined #yocto15:18
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has joined #yocto15:18
*** jku <jku!~jku@d804tyxzqsj--98wl3k-3.rev.dnainternet.fi> has quit IRC15:19
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC15:20
b00^wk2can Yocto folder which already contains a build be just c&p from one Linux machine to another, and be used same on another machine?15:24
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has quit IRC15:24
kergothb00^wk2: unlikely, no. much of the native software (Tools that run on the build machine) aren't relocatable. possibly if the path to the directory is the same, and the build arch is the same, and the build distro is the same (otherwise the binaries might be incompatible)15:25
b00^wk2yea this is what i found with timesys factory too15:28
b00^wk2paths as a minimum must match15:28
b00^wk2kergoth, i thought, OE 's one target is to be less dependent on host's OS & paths :)15:29
b00^wk2is that possible to get a silent failure of a build of some sort, with Yocto?15:31
b00^wk2probably very stupid question, of course if my layer is full of bugs, that can do anything15:31
b00^wk2but does Yocto have some stronger checks of what goes into BitBake, to minimize build errors15:32
b00^wk2seems all is upto me testing my meta-bla to make sure my bla doesn't screw up things15:33
kergothall shell tasks run with set -e, if that's what you mean15:36
kergothany failed process will fail the task15:36
kergothoe builds upstream projects. lif those upstream projects hardcode build paths into their binaries, well, then that's what they do. we cant' fix everything everywhere15:36
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has joined #yocto15:37
kergothto clarify15:37
kergothyou can mov ea build dir, just not its tmpdir15:37
kergothand you can use an sstate cache from one machine on another, so most of it will come from the cache rather than building from scratch15:37
*** marek_ <marek_!~marek@> has quit IRC15:37
b00^wk2i see15:38
b00^wk2err, kergoth what is "ea" ?15:38
kergoththat would be what we call a typo15:38
kergothmov ea = move a15:39
t0mmy# Is it possible to set capabilities on files by calling setcap for example into a recipe ?15:39
t0mmyIs it possible to set capabilities on files by calling setcap for example into a recipe ? I tried to call setcap to add permitted and effective caps but in a do_install_append function and I obtain the message below "unable to set CAP_SETFCAP effective capability: Operation not permitted"15:43
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has quit IRC15:44
kergothnot sure if pseudo supports capabilities or not. maybe check with seebs15:45
t0mmysorry, for spam, it due to a miss click15:45
*** belen <belen!~Adium@> has quit IRC15:51
t0mmykergoth: thanks you, I will keep looking while15:51
*** egavinc <egavinc!~egavinc@43.Red-2-139-180.staticIP.rima-tde.net> has quit IRC15:51
ryansturmerBack to my question about layer priority15:52
ryansturmerif I do bitbake-layers show-layers15:52
ryansturmerThe numeric layer priorities specified there are pretty much the priorities that are going to be used - is that right?15:53
ryansturmeris there anything else that affects layer priority?15:53
*** realBigfoot <realBigfoot!~realBigfo@> has joined #yocto15:53
*** realBigfoot is now known as bottazzini15:54
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has joined #yocto15:57
b00^wk2say i got some yocto core configuration , with some default or core layers, right, then I created my layers on top, to customize,fix,etc on top15:57
b00^wk2then next year say yocto updated all core configurations, packages, etc .  and now my layers are not layering properly15:58
b00^wk2i still have to fix all my local layers, right? with yocto changes15:59
kergothgenerally people maintain branches that align with yocto branches. each major release gets a branch, and same-named branches are compatible15:59
kergothbut yes, when you go to update, you'd have to adjust the layer appropriately. how much work that is depends on how much yo're doing in the layer, and what that is15:59
*** belen <belen!Adium@nat/intel/x-slpjuxbzeiyqhunq> has joined #yocto15:59
b00^wk2ok, so main benefit of layering, vs say , patching ..16:00
b00^wk2im not sure16:00
b00^wk2im just reading on layering as great huge concept in yocto, im trying to really get it16:00
kergothif you'd ever had to maintain a patch series over a long period of time, you'd already know the answer to that16:00
kergothlayers can be easily mixed and matched, added and removed, used in any number of projects. reorder two patches and watch them explode if they touch the same content..16:01
*** olivier___ <olivier___!5c91045d@gateway/web/freenode/ip.> has joined #yocto16:05
*** belen <belen!Adium@nat/intel/x-slpjuxbzeiyqhunq> has quit IRC16:05
*** egavinc <egavinc!~egavinc@43.Red-2-139-180.staticIP.rima-tde.net> has joined #yocto16:06
*** aragua <aragua!~flahouder@2a01:6600:8083:4700:206:5bff:fe9d:9d11> has quit IRC16:07
b00^wk2.. When a new release of Yocto/Poky comes out, you no longer need to recreate your changes and modifications: you simply update the lower layers, then check over your customisation layer for validity post-update (see fig 1b).16:07
b00^wk2doesn't sound right, or is this right .16:07
kergoththat's pretty much accurate16:08
b00^wk2kergoth, once sec :P16:08
kergothif you override any classes, you'll have to update them, and any version specific appends may need updating to newer recipe versions, etc16:08
kergothas i said earlier, how much work it is depends on what's in your layer16:08
*** sujith_h <sujith_h!~toaster@kde/developers/sujithh> has quit IRC16:09
b00^wk2yea, but way i understand above, you never had to even check your layer is still valid16:09
kergothideally, any general fixes should go upstream to the core layers as soon as possible, so your layer only carries what's truly specific to what functionality that layer provides16:09
*** benjamirc <benjamirc!~besquive@> has joined #yocto16:09
b00^wk2what if, in my layer, say, i assumed u-boot version fixed = x, but yocto now moves to y in update16:09
b00^wk2then my layer is scrwed up16:09
b00^wk2i have to check that16:09
b00^wk2not simple replace & play16:09
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has quit IRC16:09
b00^wk2kergoth, looks like some great skill in layring needed ? :)16:10
kergoththe thing you just quoted says specifically that layers have to be checked for validity post-update16:10
*** sujith_h <sujith_h!~toaster@> has joined #yocto16:10
*** sujith_h <sujith_h!~toaster@kde/developers/sujithh> has joined #yocto16:10
kergothbitabke will error as soon as it sees you have an append that applies to a missing recipe. you rename it to the new version and make sure your patches still apply16:11
kergothbut that's no different than any other project where you're patching a specific version of something and it gets updated16:11
b00^wk2kergoth, but it says before that, "you no longer need to re-create your changes .. "16:11
kergothbuildroot, etc, or even desktop distros16:11
b00^wk2i thought kinda, no longer have to modify anything .. :)16:11
kergothyou don't re-create them, you update them as appropriate16:11
b00^wk2expecting magic here ..16:11
olivier___Hello everyone.16:12
olivier___I have a question concerning a bootarg I need to set.16:12
olivier___For the moment, I'm setting a 'linux.bootargs.video' variable direclty from my barebox command line.16:12
olivier___I would like to insert it into my Yocto layer.16:12
olivier___I found a 'linux.bootargs.base' file in the BSP layer; should I create a new one in my layer with the same path?16:12
olivier___Or should I do it another way?16:12
*** frsc <frsc!~frsc@> has quit IRC16:17
ryansturmerIt really depends on how your BSP sets the bootargs, I would think.16:18
ryansturmerIt's possible you can bbappend in your layer and add args to the file, it just depends on how your bootloader is getting installed16:19
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has joined #yocto16:20
*** joshuagl <joshuagl!~joshuagl@> has quit IRC16:22
*** adelcast <adelcast!~adelcast@> has left #yocto16:23
*** joshuagl <joshuagl!joshuagl@nat/intel/x-qsfixrmnilavdovw> has joined #yocto16:23
olivier___ryansturmer: What do you mean by that? What should I look for to see how it's installed?16:26
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has quit IRC16:26
ryansturmerWhat board are you building for.  (I'm new to this stuff too, but might be able to help)16:27
ryansturmerThat file is most likely in the recipe for your bootloader in the BSP layer - is that correct?16:27
*** dreyna4529 <dreyna4529!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has joined #yocto16:29
olivier___I guesss yes16:30
*** fl0v0 <fl0v0!~fvo@p5DDC5387.dip0.t-ipconnect.de> has quit IRC16:30
*** benjamirc1 <benjamirc1!~besquive@> has joined #yocto16:30
olivier___ryansturmer: I just need to create a bbappend file16:30
ryansturmerLook at the recipe file, and it may reveal how that file is incorporated into the bootloader - you can then write a bbappend that modifies that recipe16:30
olivier___ryansturmer: Ok; thanks, I'll try that!16:30
ryansturmerIt may be as simple as making a bbappend file that just tacks your arguments onto the end of that file - easy peasy, but I'd take a look at the recipe that calls on that file, just to make sure what you're doing makes sense.16:31
olivier___ryansturmer: Ok; I'll check it carefully.16:31
*** olivier___ <olivier___!5c91045d@gateway/web/freenode/ip.> has quit IRC16:31
*** adelcast <adelcast!~adelcast@> has joined #yocto16:32
t0mmykergoth: I found the solution, I use "setfattr -n security.capability -v <CAP>" instead of setcap <CAP>. Thanks again16:35
*** sjolley <sjolley!sjolley@nat/intel/x-gtmluqyfjrzzrbmr> has quit IRC16:35
*** sjolley <sjolley!sjolley@nat/intel/x-jjljvrrdhfmhtbjx> has joined #yocto16:36
kergothah, interesting16:37
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has joined #yocto16:39
*** sjolley <sjolley!sjolley@nat/intel/x-jjljvrrdhfmhtbjx> has quit IRC16:40
*** Guest94003 <Guest94003!~quassel@> has quit IRC16:44
*** wenzong <wenzong!~wfan@> has quit IRC16:44
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has quit IRC16:44
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has joined #yocto16:47
abelloniah ouais16:48
ryansturmerIs there a way to printout a recipe after all appends have been applied?16:48
*** TobSnyder <TobSnyder!~schneider@ip923450f2.dynamic.kabel-deutschland.de> has quit IRC16:49
kergothryansturmer: bitbake -e recipename shows you the metadata of a recipe after all parsing, including appends16:49
*** Jackie_huang <Jackie_huang!~quassel@> has joined #yocto16:51
*** wenzong <wenzong!~wfan@> has joined #yocto16:52
*** csanchezdll <csanchezdll!~user@galileo.kdpof.com> has quit IRC16:53
*** bluelightning <bluelightning!~paul@2406:e007:44a7:1:5e51:4fff:febb:401d> has joined #yocto16:53
*** bluelightning <bluelightning!~paul@2406:e007:44a7:1:5e51:4fff:febb:401d> has quit IRC16:53
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto16:53
ryansturmerkergoth: Do you have any suggestions for the situation where my bbappend order does not seem to be following my layer priority?16:54
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has quit IRC16:54
ryansturmerappends to my base-files recipe are clearly happening in the wrong order, no matter what I set my layer priority to16:55
ryansturmer(confirmed now with bitbake -e base-files)16:55
*** maxin <maxin!~maxin@> has quit IRC16:57
*** diego_r <diego_r!~diego@> has quit IRC16:57
*** _valle_ <_valle_!~valle@195-198-200-72.customer.telia.com> has joined #yocto16:58
*** sjolley <sjolley!sjolley@nat/intel/x-xwdfdjkfreztklea> has joined #yocto17:01
ryansturmerMaybe the way that I'm doing this altogether is incorrect - I wonder if someone here might have an insight.17:02
ryansturmerI simply want to modify the /etc/fstab that is laid down by my BSP layer.  The BSP layer has a bbappend file that modifies the base-files recipe and replaces the /etc/fstab with its own.17:02
kergothby layer priority, you do mean LAYER_PRIORITY_* in the layer.conf, correct? an dyou're confirming the behavior by looking at the info about which files were parsed in the bitbake -e, not just the variables' value?17:02
ryansturmerI mean BBFILE_PRIORITY ?17:03
kergothyeah, all you should need to do for that is have a layer higher priority than the bsp layer17:03
ryansturmerHigher priority == higher number?17:03
ryansturmer(I have tried both, in either case)17:03
ryansturmerWhat I do in my append, is just use sed to modify the file that the underlying layer already laid down.17:04
ryansturmersed -r 's:rootfs\s+/\s+auto\s+:&ro,errors=remount-ro,:' < ${D}${sysconfdir}/fstab > ${D}${sysconfdir}/fstab17:05
ryansturmer(Make the root filesystem read-only)17:05
ryansturmerif I say bitbake-layers show-appends | grep base-files, should that give me the appends in appended order?  or is it just random order?17:06
*** igor4 <igor4!~Igor_Stop@> has joined #yocto17:06
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has joined #yocto17:07
*** igor1 <igor1!~Igor_Stop@> has quit IRC17:07
*** behanw <behanw!~behanw@2001:470:b26c:0:e4b8:d724:1476:2f70> has quit IRC17:07
*** aehs29 <aehs29!~aehernan@> has quit IRC17:07
*** behanw <behanw!~behanw@d75-157-25-181.bchsia.telus.net> has joined #yocto17:07
*** aehs29 <aehs29!~aehernan@> has joined #yocto17:07
bluelightningmorning all17:08
bluelightningryansturmer: should be appended order17:08
ryansturmerYeah, no change in my BBFILE_PRIORITY variable (in conf/layer.conf) in my layer has any impact on the order that is represented there17:09
*** mckoan is now known as mckoan|away17:09
ryansturmereven though I can bitbake-layers show-layers and see that the priority number changes17:10
*** radzy_lunch <radzy_lunch!~radzy@unknown-216-89.windriver.com> has quit IRC17:10
*** radzy_lunch <radzy_lunch!~radzy@unknown-216-89.windriver.com> has joined #yocto17:10
ryansturmeris this something that was likely fixed recently?  or has this worked forever and ever.  This is the build that ships with the Intel Edison, so it's back a bit, revision wise.17:10
ryansturmerseems kind of fundamental to be a bug at this stage - gotta be something silly I'm doing here17:11
kergothare both appends using versions ,or both using %?17:12
kergothif one is versioned and the other is wildcard, the order was non-deterministic until relatively recently17:12
kergothrichard fixed that bug a while back17:12
kergothwell, short while17:12
_valle_yocto/hmi/poky/build/tmp/sysroots/x86_64-linux/usr/lib/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.9.2/include/stdint.h:9:26: fatal error: stdint.h: No such file or directory17:12
*** morphis <morphis!~morphis@pD9ED7EFB.dip0.t-ipconnect.de> has quit IRC17:13
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has quit IRC17:13
bluelightning_valle_: how are you invoking the compiler? are you using $CC ?17:14
kergoththough, i think that was order within a layer, not between, now that i think about it17:14
* kergoth shrugs17:14
bluelightningI can't even find that patch :/17:14
ryansturmerOne of the appends is with a version17:15
ryansturmerand the other is with %17:15
ryansturmerwould I be better off with the version in there?17:15
_valle_bluelightning: Yes, EXTRA_OEMAKE += "'CC=${CC}' 'LD=${LD}' 'STRIP=${STRIP}' 'CROSS_COMPILE=${TARGET_SYS}-' 'HOSTCC=${CC}'"17:16
kergothryansturmer: see 3cb87724a5b21550e99c18e97b665d6604bb2fa9 in poky, which is f980f060cd0d1e7fe5011f3c325c1b254f05eccf in the bitbake repo. you could try applying that if you don't already have it on the branch you're using.17:16
kergothnot sure if it'll help, but worth checking17:16
*** jbrianceau_ <jbrianceau_!uid10952@gateway/web/irccloud.com/x-lwzzctphymrjnfld> has joined #yocto17:17
*** belen <belen!Adium@nat/intel/x-kpqlbvctkrocrymx> has joined #yocto17:18
*** lamego1 <lamego1!jose@nat/intel/x-afnfgxuymhgapxqx> has joined #yocto17:18
*** jku <jku!~jku@d804tyxzqsj--98wl3k-3.rev.dnainternet.fi> has joined #yocto17:18
_valle_bluelightning: Then oe_runmake env17:19
*** yann|work <yann|work!~yann@LFbn-1-1026-146.w86-247.abo.wanadoo.fr> has quit IRC17:20
*** jbrianceau <jbrianceau!uid10952@gateway/web/irccloud.com/x-jeoftigvtxryicmw> has quit IRC17:20
*** lamego <lamego!~jose@> has quit IRC17:20
*** jbrianceau_ is now known as jbrianceau17:20
*** SoylentYellow <SoylentYellow!~SoylentYe@207-114-172-147.static.twtelecom.net> has joined #yocto17:20
bluelightning_valle_: hmm, ok... not sure what to suggest17:22
*** Crofton <Crofton!~balister@echelon.c-base.org> has quit IRC17:22
*** toscalix <toscalix!~agustinbe@> has joined #yocto17:23
ryansturmerThat did it.17:24
ryansturmerWell, it changed the order reported by bitbake-layers17:25
ryansturmerrebuilding now to see how it goes.17:25
ryansturmerFriggin frig.17:25
ryansturmerI ran into this issue on another recipe17:25
ryansturmerand I didn't understand how I fixed it.17:25
ryansturmerThis is how.17:25
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has joined #yocto17:26
_valle_bluelightning: http://pastebin.com/hYPUwB9q17:28
*** seezer <seezer!quassel@quassel/developer/seezer> has quit IRC17:28
*** Hauke <Hauke!~Hauke@hauke-m.de> has quit IRC17:30
*** seezer <seezer!quassel@quassel/developer/seezer> has joined #yocto17:30
*** caiortp <caiortp!~inatel@> has joined #yocto17:30
*** belen <belen!Adium@nat/intel/x-kpqlbvctkrocrymx> has quit IRC17:30
*** belen <belen!Adium@nat/intel/x-lpcxmxvcpzwkmffs> has joined #yocto17:31
*** obsrwr_ <obsrwr_!~obsrwr@> has joined #yocto17:34
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has quit IRC17:35
*** belen <belen!Adium@nat/intel/x-lpcxmxvcpzwkmffs> has quit IRC17:35
*** Hauke <Hauke!~Hauke@hauke-m.de> has joined #yocto17:36
*** armpit <armpit!~akuster@2601:202:4000:1239:f0f5:a917:60f2:fe2> has quit IRC17:40
*** jku <jku!~jku@d804tyxzqsj--98wl3k-3.rev.dnainternet.fi> has quit IRC17:41
seebsno capabilities yet, no.17:41
seebsin pseudo.17:41
*** roccof <roccof!~roccof@93-51-177-218.ip268.fastwebnet.it> has quit IRC17:41
seebsI didn't even know that was a thing until I read the question.17:41
*** egavinc <egavinc!~egavinc@43.Red-2-139-180.staticIP.rima-tde.net> has quit IRC17:42
nerdboynot a bad idea tho...17:46
*** sjolley <sjolley!sjolley@nat/intel/x-xwdfdjkfreztklea> has quit IRC17:59
*** sjolley <sjolley!sjolley@nat/intel/x-mumrlvwtmpnjssrm> has joined #yocto17:59
*** jonathanmaw <jonathanmaw!~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk> has quit IRC18:04
*** t0mmy <t0mmy!~tprrt@> has quit IRC18:05
*** Guest78650 is now known as moto-timo18:08
*** moto-timo <moto-timo!ttorling@fsf/member/moto-timo> has joined #yocto18:08
*** jbrianceau is now known as jbrianceau_away18:10
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has joined #yocto18:17
*** mihai <mihai!~mihai@> has quit IRC18:17
*** dvhart <dvhart!~dvhart@> has joined #yocto18:20
seebsI poked a bit at setcap documentation, and it looks like it's pretty pointless right now. And/or not entirely in place; most of the systems I've checked on have references to man pages they don't actually have, and I found one man page claiming that there's only a single capability bit, so either everything is permitted or nothing is.18:26
seebsBut we could probably fake it.18:26
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has quit IRC18:28
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has joined #yocto18:36
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has quit IRC18:42
nerdboythat doesn't sound right...18:54
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has joined #yocto18:54
nerdboyseebs: i see libcap and libcap-ng18:55
nerdboymaybe the former is deprecated?18:56
nerdboythey're both installed/pulled in by caps use flag18:57
*** pohly <pohly!~pohly@p57A56B97.dip0.t-ipconnect.de> has quit IRC18:57
nerdboyi take that back, most stuff still depends on libcap18:58
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:8ff:f279:59ff:fe64:3a8> has quit IRC19:01
seebsThe man page I found had a footnote about how the capability things were all fundamentally represented by a single bit, so if you enabledanything, you got everything. Surprised me a bit, but I guess it *is* the historical model.19:05
*** AndersD <AndersD!~anders@h83-209-191-235.dynamic.se.alltele.net> has joined #yocto19:11
*** AndersD <AndersD!~anders@h83-209-191-235.dynamic.se.alltele.net> has quit IRC19:16
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has joined #yocto19:16
*** sujith_h <sujith_h!~toaster@kde/developers/sujithh> has quit IRC19:20
*** joshuagl <joshuagl!joshuagl@nat/intel/x-qsfixrmnilavdovw> has quit IRC19:31
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:ae3:f279:59ff:fe64:3a8> has joined #yocto19:38
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:ae3:f279:59ff:fe64:3a8> has quit IRC19:44
*** paulg_ <paulg_!~paulg@> has joined #yocto19:49
*** townxelliot <townxelliot!~ell@> has quit IRC19:50
*** sjolley <sjolley!sjolley@nat/intel/x-mumrlvwtmpnjssrm> has quit IRC19:54
*** sjolley <sjolley!~sjolley@> has joined #yocto19:56
-YoctoAutoBuilder- build #629 of nightly-x86-64-lsb is complete: Failure [failed BuildImages Running Sanity Tests BuildImages_1] Build details are at http://autobuilder.yoctoproject.org/main/builders/nightly-x86-64-lsb/builds/62919:59
nerdboyseebs: that still doesn't sound right20:02
nerdboyeg, you should be able to get filecaps20:02
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:ae3:f279:59ff:fe64:3a8> has joined #yocto20:03
*** toscalix <toscalix!~agustinbe@> has quit IRC20:04
seebsThe docs could be wrong or out of sync.20:05
*** dreyna4529 <dreyna4529!~dreyna@c-24-5-28-247.hsd1.ca.comcast.net> has quit IRC20:05
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:ae3:f279:59ff:fe64:3a8> has quit IRC20:09
*** yann|work <yann|work!~yann@nan92-1-81-57-214-146.fbx.proxad.net> has joined #yocto20:09
*** armpit <armpit!~akuster@> has joined #yocto20:12
*** vmeson <vmeson!~rmacleod@> has quit IRC20:13
*** JaMa <JaMa!~martin@ip-86-49-34-37.net.upcbroadband.cz> has quit IRC20:15
*** berton <berton!~fabio@> has quit IRC20:15
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-lwzzctphymrjnfld> has quit IRC20:16
nerdboyi see "fcaps cap_net_admin /path/to/foo"20:16
nerdboylooks fairly granular/specific20:16
nerdboyin qemu post_inst20:17
nerdboytarget file has no read perms except root20:18
nerdboylooks it should depend on what capabilities you need to set20:19
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:af4:f279:59ff:fe64:3a8> has joined #yocto20:22
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:af4:f279:59ff:fe64:3a8> has quit IRC20:29
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:af4:f279:59ff:fe64:3a8> has joined #yocto20:31
*** belen <belen!Adium@nat/intel/x-deyqsfpmxavfbsfv> has joined #yocto20:31
*** Biliogadafr <Biliogadafr!~User@nat2-minsk-pool-46-53-195-225.telecom.by> has quit IRC20:35
*** Biliogadafr <Biliogadafr!~User@nat2-minsk-pool-46-53-195-225.telecom.by> has joined #yocto20:37
*** Biliogadafr <Biliogadafr!~User@nat2-minsk-pool-46-53-195-225.telecom.by> has quit IRC20:41
*** caiortp <caiortp!~inatel@> has quit IRC20:41
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:af4:f279:59ff:fe64:3a8> has quit IRC20:47
*** clopez <clopez!~tau@neutrino.es> has quit IRC20:48
*** radhus <radhus!~radhus@sevh.radhuset.org> has quit IRC20:49
*** igor4 <igor4!~Igor_Stop@> has quit IRC20:53
*** Hairy <Hairy!~textual@host81-151-229-210.range81-151.btcentralplus.com> has joined #yocto20:55
*** igor1 <igor1!~Igor_Stop@> has joined #yocto20:58
*** clopez <clopez!~tau@neutrino.es> has joined #yocto20:59
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:af4:f279:59ff:fe64:3a8> has joined #yocto20:59
*** Hairy <Hairy!~textual@host81-151-229-210.range81-151.btcentralplus.com> has quit IRC21:00
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:af4:f279:59ff:fe64:3a8> has quit IRC21:05
*** Hairy <Hairy!~textual@host81-151-229-210.range81-151.btcentralplus.com> has joined #yocto21:08
*** ant_home <ant_home!~ant__@host48-23-dynamic.14-87-r.retail.telecomitalia.it> has joined #yocto21:14
*** vmeson <vmeson!~rmacleod@24-212-184-107.cable.teksavvy.com> has joined #yocto21:18
*** sgw_ <sgw_!~sgw_@75-136-2-98.static.jcsn.tn.charter.com> has quit IRC21:20
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-rfagqmygfmldyvhv> has joined #yocto21:25
*** jbrianceau_away is now known as jbrianceau_home21:25
*** SoylentYellow <SoylentYellow!~SoylentYe@207-114-172-147.static.twtelecom.net> has quit IRC21:25
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:af4:f279:59ff:fe64:3a8> has joined #yocto21:31
*** sgw_ <sgw_!~sgw_@75-136-2-98.static.jcsn.tn.charter.com> has joined #yocto21:35
*** ajtag <ajtag!~ajtag@cpc10-lee211-2-0-cust124.7-1.cable.virginm.net> has joined #yocto21:35
*** SoylentYellow <SoylentYellow!~SoylentYe@207-114-172-147.static.twtelecom.net> has joined #yocto21:38
*** AndersD <AndersD!~anders@213-64-219-84-no126.business.telia.com> has quit IRC21:40
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:af4:f279:59ff:fe64:3a8> has quit IRC21:40
*** bottazzini <bottazzini!~realBigfo@> has quit IRC21:43
*** ap0 <ap0!~ap0@HSI-KBW-109-193-154-042.hsi7.kabel-badenwuerttemberg.de> has joined #yocto21:49
*** ap0 <ap0!~ap0@HSI-KBW-109-193-154-042.hsi7.kabel-badenwuerttemberg.de> has quit IRC21:49
*** sjolley <sjolley!~sjolley@> has quit IRC22:02
*** IvanSB <IvanSB!~IvanSB@> has joined #yocto22:02
*** paulg_ <paulg_!~paulg@> has quit IRC22:03
*** sjolley <sjolley!sjolley@nat/intel/x-dekookzrhrxqvuem> has joined #yocto22:03
*** benjamirc1 <benjamirc1!~besquive@> has quit IRC22:04
*** aehs29 <aehs29!~aehernan@> has quit IRC22:05
*** aehs29 <aehs29!~aehernan@> has joined #yocto22:06
*** sjolley <sjolley!sjolley@nat/intel/x-dekookzrhrxqvuem> has quit IRC22:09
*** obsrwr_ <obsrwr_!~obsrwr@> has quit IRC22:14
*** IvanSB <IvanSB!~IvanSB@> has quit IRC22:19
*** belen <belen!Adium@nat/intel/x-deyqsfpmxavfbsfv> has quit IRC22:22
*** roccof <roccof!~rocco@> has joined #yocto22:25
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:af4:f279:59ff:fe64:3a8> has joined #yocto22:31
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:af4:f279:59ff:fe64:3a8> has quit IRC22:33
*** sjolley <sjolley!~sjolley@> has joined #yocto22:34
*** grma <grma!~gruberm@> has quit IRC22:37
*** rburton <rburton!~Adium@> has quit IRC22:40
wyrmSo, hey. I'm trying to build the cross-development qt5 SDK. The old-and-busted way is to use `bitbake meta-toolchain-qt5`. The new-hotness way is to just use `bitbake -c populate_sdk <main_image>`.22:46
*** Crofton <Crofton!~balister@> has joined #yocto22:46
wyrmThe old way builds both the nativesdk-packagegroup-qt5-toolchain-host and packagegroup-qt5-toolchain-target targets, while the new way only seems to want to build the ...-target one.22:48
wyrmAnd I specifically notice that the new way doesn't provide a qmake to run on the development box, but it does provide one to run on the destination platform, which seems off.22:49
wyrmSo, what am I likely doing wrong?22:49
*** aehs29 <aehs29!~aehernan@> has quit IRC22:56
*** benjamirc1 <benjamirc1!~besquive@> has joined #yocto22:56
*** aehs29 <aehs29!~aehernan@> has joined #yocto22:56
*** bfederau <bfederau!~quassel@service.basyskom.com> has quit IRC23:01
*** fmeerkoetter <fmeerkoetter!~quassel@> has quit IRC23:01
*** fmeerkoetter <fmeerkoetter!~quassel@service.basyskom.com> has joined #yocto23:01
*** bfederau <bfederau!~quassel@service.basyskom.com> has joined #yocto23:01
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC23:08
*** lamego1 <lamego1!jose@nat/intel/x-afnfgxuymhgapxqx> has quit IRC23:10
*** Crofton <Crofton!~balister@> has quit IRC23:11
*** sgw_ <sgw_!~sgw_@75-136-2-98.static.jcsn.tn.charter.com> has quit IRC23:16
*** obsrwr <obsrwr!~otp-amois@> has quit IRC23:26
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:af4:f279:59ff:fe64:3a8> has joined #yocto23:27
*** bluelightning <bluelightning!~paul@2406:e007:44a7:1:5e51:4fff:febb:401d> has joined #yocto23:30
*** bluelightning <bluelightning!~paul@2406:e007:44a7:1:5e51:4fff:febb:401d> has quit IRC23:30
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto23:30
*** sjolley <sjolley!~sjolley@> has quit IRC23:31
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:af4:f279:59ff:fe64:3a8> has quit IRC23:41
*** clopez <clopez!~tau@neutrino.es> has quit IRC23:41
*** ant_home <ant_home!~ant__@host48-23-dynamic.14-87-r.retail.telecomitalia.it> has quit IRC23:45
*** sameo <sameo!~samuel@> has quit IRC23:46
*** clopez <clopez!~tau@neutrino.es> has joined #yocto23:47
*** sjolley <sjolley!~sjolley@> has joined #yocto23:47
*** Hairy <Hairy!~textual@host81-151-229-210.range81-151.btcentralplus.com> has quit IRC23:52
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:af4:f279:59ff:fe64:3a8> has joined #yocto23:53
*** IvanSB <IvanSB!~IvanSB@2a01:2000:2000:af4:f279:59ff:fe64:3a8> has quit IRC23:59

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