Thursday, 2013-08-29

*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto00:00
*** mulhern <mulhern!> has joined #yocto00:05
*** davest <davest!~Adium@> has quit IRC00:09
*** _Lucretia_ <_Lucretia_!~munkee@pdpc/supporter/active/lucretia> has joined #yocto00:09
*** mebrown <mebrown!> has quit IRC00:13
*** mebrown <mebrown!> has joined #yocto00:13
*** _julian <_julian!> has joined #yocto00:16
*** _julian_ <_julian_!> has quit IRC00:19
*** mulhern <mulhern!> has quit IRC00:30
*** carlos001_ <carlos001_!b5c1011a@gateway/web/freenode/ip.> has quit IRC00:40
*** andyross <andyross!> has quit IRC00:53
*** mulhern <mulhern!> has joined #yocto01:05
pidgeRP: yes, that was me. I killed a bunch of builds01:07
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto01:30
*** Net147 <Net147!> has joined #yocto01:36
*** mulhern <mulhern!> has quit IRC01:51
*** Jefro <Jefro!> has quit IRC01:51
*** mitz__ <mitz__!> has joined #yocto02:01
*** mitz <mitz!> has quit IRC02:02
*** silviof <silviof!~silviof@unaffiliated/silviof> has quit IRC02:04
*** silviof <silviof!~silviof@unaffiliated/silviof> has joined #yocto02:10
*** scot <scot!~scot@> has joined #yocto02:38
*** scot <scot!~scot@> has quit IRC02:45
*** lpapp_ <lpapp_!~lpapp@kde/lpapp> has left #yocto03:02
*** andyross <andyross!> has joined #yocto03:17
*** ka6sox-farfarawa is now known as ka6sox03:18
-YoctoAutoBuilder- build #274 of nightly-ppc is complete: Success [build successful] Build details are at
*** lpapp_ <lpapp_!~lpapp@kde/lpapp> has joined #yocto03:31
lpapp_hi, why are there native packages?03:32
*** musdem <musdem!> has quit IRC03:36
sgw_lpapp_: your up late, the -native packages are to ensure a consistent and reproducible build environment and not rely on the host's tools which may be either older or newer.03:39
lpapp_sgw_: why would I?03:42
lpapp_it is already 5 pm here soon.03:42
sgw_lpapp_: then your up early!03:43
lpapp_sgw_: why? This is the best time for meditating. :)03:43
lpapp_rather than the tiring evenings.03:43
lpapp_I guess it is just the matter of when one goes to sleep. :)03:44
sgw_You have an interesting viewpoint if you are meditating on IRC ;-)03:44
lpapp_no, I am already done with that.03:44
lpapp_sgw_: there is for instance qtbase-native, but I am not yet sure why.03:45
lpapp_sgw_: qt5 is meant to be buildable easily for host, or target.03:45
lpapp_but I see this situation for other packages, too.03:45
sgw_lpapp_: is qtbase part of qt5?  There might be some tool that is needed to help build qt5, so these are built first and then qt5 will use that tool03:46
lpapp_sgw_: yes, there is a bootstrap, but how is that related?03:49
lpapp_(it is not a qt5 specific problem btw)03:50
lpapp_JaMa: any of the qt5 changes meant to be upstreamed?03:56
*** Net147 <Net147!> has quit IRC03:58
*** vicky <vicky!~vicky@> has joined #yocto04:02
vickyHi yocto. I added linux-firmware in my image file. It compiled fine. But i m getting the licence problem of rtlwifi. My log at
*** Jefro <Jefro!> has joined #yocto04:10
*** Jefro <Jefro!> has quit IRC04:14
*** _alex_kag_ <_alex_kag_!~alex_kag@> has quit IRC04:29
*** andyross <andyross!> has quit IRC04:54
*** _alex_kag_ <_alex_kag_!~alex_kag@> has joined #yocto04:54
*** Satrukaan <Satrukaan!> has joined #yocto05:14
*** Satrukaan <Satrukaan!> has quit IRC05:19
*** Jefro <Jefro!> has joined #yocto05:21
*** tor <tor!> has joined #yocto05:22
*** smartin <smartin!> has joined #yocto05:24
*** smartin_ <smartin_!> has quit IRC05:25
*** zecke <zecke!> has joined #yocto05:25
JaMalpapp_: you mean .patch files in meta-qt5?05:28
JaMasome has Upstream-Status..05:28
lpapp_JaMa: yes, those05:45
lpapp_JaMa: like external host dir05:45
lpapp_JaMa: I was trying the update to 5.1.1 but patches are failing05:47
lpapp_JaMa: and I was thinking of asking the upstreamability...05:47
lpapp_even qtbase has many patches.05:47
lpapp_JaMa: I removed 2 integrated, and there are few inappropriate, and the rest is pending...05:51
*** jeremiah <jeremiah!> has joined #yocto05:59
*** jeremiah <jeremiah!> has quit IRC06:03
*** zecke <zecke!> has quit IRC06:14
*** swex__ <swex__!~swex@> has joined #yocto06:14
*** swex_ <swex_!~swex@> has quit IRC06:15
*** mihai <mihai!~mihai@> has joined #yocto06:18
*** B4gder <B4gder!> has joined #yocto06:26
*** melonipoika <melonipoika!> has joined #yocto06:36
*** jeremiah <jeremiah!> has joined #yocto06:45
*** panda84kde <panda84kde!> has joined #yocto06:46
*** zeeblex <zeeblex!~apalalax@> has joined #yocto06:49
*** seebs <seebs!> has quit IRC06:53
*** florian_kc is now known as florian06:56
*** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has joined #yocto07:04
*** slaine <slaine!~slaine@> has joined #yocto07:04
*** dany <dany!> has quit IRC07:06
*** seebs <seebs!> has joined #yocto07:06
*** eballetbo <eballetbo!> has joined #yocto07:07
*** dany <dany!~Thunderbi@> has joined #yocto07:08
*** elmi82 <elmi82!> has joined #yocto07:14
*** ant_work <ant_work!> has joined #yocto07:15
*** volker <volker!> has joined #yocto07:17
*** zeeblex1 <zeeblex1!apalalax@nat/intel/x-cpqsonphydbwyywn> has joined #yocto07:34
*** zeeblex <zeeblex!~apalalax@> has quit IRC07:36
*** OlivierG <OlivierG!> has left #yocto07:41
*** kbart <kbart!~KBart@> has joined #yocto07:44
*** mitz__ <mitz__!> has quit IRC07:51
*** bluelightning <bluelightning!~paul@> has joined #yocto07:51
*** bluelightning <bluelightning!~paul@> has quit IRC07:51
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto07:51
*** mitz__ <mitz__!> has joined #yocto07:52
JaMalpapp_: you can see qtbase repo in meta-qt5 org on github, that's what I'm using to rebase patches for new releases08:02
JaMalpapp_: I've discussed external-dir-host with ossi on IRC, but in the end I'm not so happy about how it works, so I haven't submitted it upstream in the end08:03
*** seebs <seebs!> has quit IRC08:09
*** seebs <seebs!> has joined #yocto08:10
bluelightningmorning all08:11
*** sameo <sameo!~samuel@> has joined #yocto08:12
lpapp_JaMa: well, there are a few inappropriate things in there.08:14
lpapp_like the oe-g++ mkspcs.08:14
*** melonipoika_ <melonipoika_!> has joined #yocto08:14
*** melonipoika <melonipoika!> has quit IRC08:15
gabyHi, How can I change the PYTHON executable in a recipe in order to use python-native ?08:18
*** lpapp_ <lpapp_!~lpapp@kde/lpapp> has quit IRC08:19
*** JimBaxter <JimBaxter!> has joined #yocto08:24
*** honschu <honschu!~honschu@shackspace/j4fun> has joined #yocto08:31
*** honschu_ <honschu_!~honschu@shackspace/j4fun> has quit IRC08:35
*** lpapp <lpapp!~lpapp@> has joined #yocto08:38
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto08:38
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto08:43
tfgaby: inherit the python-native class08:45
tfthat should have been pythonnative08:46
*** belen <belen!~Adium@> has joined #yocto08:47
*** dany <dany!~Thunderbi@> has quit IRC08:47
*** dany <dany!> has joined #yocto08:51
lpappJaMa: what did ossi suggest instead of the external host dir?08:53
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC09:00
*** vicky <vicky!~vicky@> has quit IRC09:03
*** vicky <vicky!~vicky@> has joined #yocto09:03
JaMalpapp: there isn't any replacement for that09:06
lpappJaMa: what is the problem with bootstrapping09:06
lpappJaMa: as far as I read that, it seems to grab tools from a prebuilt external location09:07
lpappso, what is the problem with boostrapping, rather than doing so?09:07
JaMaah I see where you're going09:07
JaMathe goal with OE is to build native tools just once09:08
JaMaand then reuse the same tools for different target builds09:08
lpappJaMa: yeah, so why not have a native package?09:08
lpappwhich are building the tools?09:08
lpappand that native package is bootstrapped.09:08
JaMalpapp: that's what qtbase-native is09:09
lpappJaMa: yeah, so what is the purpose of that change?09:09
lpappyou can use the native tools if they are in the path.09:10
JaMano it will try to bootstrap them again09:10
JaMaexternal-host-bin is switch to disable bootstraping and forcing build to use binaries from qtbase-native09:11
lpappthis looks like a configure flag09:11
JaMait is configure flag09:12
lpappJaMa: I am not sure I understand this use case.09:14
lpappJaMa: if qtbase changes, it might be that the tools changed, and they need to be rebuilt.09:15
lpappand they are only rebuilt during the qtbase rebuild.09:15
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto09:16
lpappperhaps it external stuff cannot be found, it makes sense to bootstrap even then though, yeah.09:17
lpappJaMa: if native tools cannot be found in the path, it might make sense to rebuilt them.09:20
lpappif they, then perhaps not, although the installed might be outdated.09:20
*** blloyd <blloyd!> has joined #yocto09:21
*** OlivierG <OlivierG!> has joined #yocto09:24
*** blloyd <blloyd!> has quit IRC09:27
*** OlivierG <OlivierG!> has left #yocto09:27
*** blloyd <blloyd!> has joined #yocto09:29
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC09:30
JaMalpapp: that's why recipes using them have qtbase-native in DEPENDS09:30
lpappthe only problem I see is that tools might be outdated.09:31
lpappand IMO it should be rebuilt when qtbase is rebuilt09:31
lpappin which case, the change has not much addition09:31
JaMawhy should be, if there is newer qtbase-native it will be upgraded before qtbase is built09:31
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC09:31
*** blloyd_ <blloyd_!> has joined #yocto09:33
*** lpapp <lpapp!~lpapp@> has joined #yocto09:33
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto09:33
*** blloyd <blloyd!> has quit IRC09:33
JaMalpapp: as long as qtbase-native signature is valid, then aren't outdated09:34
JaMalpapp: and qtbase-native can be reused from sstate-cache09:34
JaMaso this addition is needed (I don't know how to explain it better for you to see it)09:34
lpappwell, the source has to be checksum'd and compared09:36
lpappif it is not what is installed, it has to be rebuilt... so in that case, the one time build is kinda moot.09:37
lpappif it is the same, it does not have to rebuild.09:37
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC09:38
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto09:39
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto09:42
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC09:46
JaMarburton: ping09:54
*** zecke <zecke!~ich@> has joined #yocto09:56
*** melonipoika <melonipoika!> has joined #yocto09:57
bluelightningJaMa: he's away I think09:57
bluelightningJaMa: anything I can help with?09:57
JaMait was about libmatchbox, but I'll handle it different09:57
*** melonipoika_ <melonipoika_!> has quit IRC09:57
JaMabluelightning: you can help me with something else.. I have 20 patches for oe-core and 80 for meta-oe for deterministic dependencies, I'm still testing them so I haven't sent them for review yet09:58
*** lpapp <lpapp!~lpapp@> has joined #yocto09:59
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto09:59
JaMabut when is the last option to get them in 1.5?09:59
bluelightningJaMa: wow, ok...09:59
bluelightningJaMa: well, I can't guarantee they will get in but if they're bugfixes and not too impactful then they should be OK; we'd better have them soon though10:00
JaMabluelightning: this is the libmatchbox change I wanted to ask rburton about (if he wants to fix missing include instead)
bluelightningIMO it would be really great to have most dependency issues nailed down for 1.510:00
JaMaI know only about handful yet unresolved deps after this patchset but verification builds get always broken by some other change, so I haven't got complete world for some time..10:01
bluelightningJaMa: that fix looks reasonable to me; I'd say fixing the png-disabled case can be handled later, but rburton may have other ideas being the maintainer10:01
JaMayes that why I was asking him10:02
JaMabluelightning: btw were you interested in qcanobserver? or do I remember it incorrectly?10:08
bluelightningJaMa: not personally... I don't yet have a device here with a CAN bus to test, although I do have a minnowboard on order; but still nothing CAN-equipped to connect to it other than my car which I don't really want to tinker with at that level ;)10:11
JaMaoki, it's broken for long time, so I'm looking for someone who was using it or plans to use it10:12
bluelightningI wonder if anyone in the minnowboard community might be interested if they're playing around with CAN10:14
bluelightningI can ask in #minnowboard later10:14
JaMait's broken since some qt4 upgrade IIRC, so I'm not sure if it needs someone with CAN knowledge - except for motivation to fix it of course :)10:16
JaMahmm last build error looks like just missing include.. I'll probably fix it in next round10:17
JaMaah there is also problem with sourceforge layout change for svn repos10:22
*** zecke <zecke!~ich@> has quit IRC10:27
*** Anusko <Anusko!~anusko@> has joined #yocto10:32
*** dRp3pP3r <dRp3pP3r!d5bf22ee@gateway/web/freenode/ip.> has joined #yocto10:35
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC10:37
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto10:38
dRp3pP3rhi experts, i have a little problem: my build always fails at xserver-xorg, do_package_wirte_rpm due to a change in $PV. i tried to 'bitbake -c clean xserver-xorg' and rebuild but it doesnt help. i noticed that the explicit funtion to fail is read_subpackage_metadata. since xserver-xorg does have subpackages (a few -extension packets) i guess i would have to rebuild them because they were build with another PV10:38
bluelightningJaMa: right, we discussed that last week I think; someone really needs to go and submit a sourceforge infrastructure bug report to get them to put in working redirects for the old layout10:39
bluelightningJaMa: is that something you'd be prepared to do?10:39
dRp3pP3rbut i do not know how, because bitbake says 'nothing provides xserver-xorg-extension-*' with * being any of the extensions provided by xserver-xorg.10:39
JaMabluelightning: not now as I would like to finish those dependencies in time10:40
*** sakoman <sakoman!> has quit IRC10:44
bluelightningJaMa: right, fair enough10:47
*** Anusko <Anusko!~anusko@> has quit IRC10:47
*** Anusko <Anusko!~anusko@> has joined #yocto10:48
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC10:49
*** volker <volker!> has quit IRC10:54
*** mebrown <mebrown!> has quit IRC10:56
*** mebrown <mebrown!> has joined #yocto10:57
*** joseppc <joseppc!> has joined #yocto10:57
dRp3pP3ranyone any ideas?11:05
dRp3pP3rplease :)11:05
bluelightningndec: given we discussed it earlier in #oe would you be able to submit a sourceforge infrastructure bug report to get working redirects added for the old svn layout?11:09
bluelightningdRp3pP3r: xserver-xorg is the recipe that produces those packages, but they are packages and thus you can't specify them as names on the bitbake command line11:11
bluelightningdRp3pP3r: it sounds more like a bug to me11:11
dRp3pP3rbluelightning: thats my problem. deleting all files under work/ didn't help too...11:12
*** dRp3pP3r_ <dRp3pP3r_!d5bf22ee@gateway/web/freenode/ip.> has joined #yocto11:14
dRp3pP3r_so, what do i do?11:15
bluelightningdRp3pP3r_: you should never delete tmp/work/ on its own, that's probably trashed your TMPDIR11:15
dRp3pP3r_seemed like the only way to get rid of the subpackages with the wrong PV, but the error stays...11:15
bluelightning(although just deleting tmp/work/...../recipe/version wouldn't be a problem if you subsequently cleaned)11:15
dRp3pP3r_that's what i did....11:16
bluelightningok, no worries on that front then11:16
bluelightningbut you should never get tracebacks or obscure errors like that, if you are it's a bug11:16
*** dRp3pP3r <dRp3pP3r!d5bf22ee@gateway/web/freenode/ip.> has quit IRC11:16
dRp3pP3r_the exact one is: ERROR: Recipe xserver-xorg is trying to change PV from '1.14.0' to '1.11.4'. This will cause do_package_write_* failures since the incorrect data will be used and they will be unable to find the right workdir.11:17
bluelightningah right11:18
bluelightninghave you tried bitbake -c cleansstate xserver-xorg ?11:18
dRp3pP3r_not yet, mom11:19
bluelightningI have to step out for a sec but that should get around the problem11:19
dRp3pP3r_k thx11:19
*** sameo <sameo!~samuel@> has quit IRC11:21
*** zecke <zecke!~ich@> has joined #yocto11:23
*** Corneliu <Corneliu!c0c6972b@gateway/web/freenode/ip.> has joined #yocto11:27
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has joined #yocto11:28
*** sakoman <sakoman!> has joined #yocto11:28
*** sameo <sameo!~samuel@> has joined #yocto11:34
dRp3pP3r_bluelightning: for the record: didn't work. read_subpackage_metadata again.11:37
JaMadRp3pP3r_: read especially last comment with "find" command11:37
yoctiBug 4102: normal, Medium+, 1.5 M2, richard.purdie, RESOLVED FIXED, Incremental builds do not work well when renaming recipes or changing architecture.11:37
*** sakoman <sakoman!> has quit IRC11:38
*** walters <walters!> has quit IRC11:39
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC11:40
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto11:41
dRp3pP3r_JaMa: thanks, worked (the find command)11:47
dRp3pP3r_i suppose the mentioned patch 2/2 is implemnted in 1.5M2?11:47
dRp3pP3r_right. thanks again. :)11:49
dRp3pP3r_i'm off... hava a nice day u all :)11:50
*** dRp3pP3r_ <dRp3pP3r_!d5bf22ee@gateway/web/freenode/ip.> has quit IRC11:50
*** mulhern <mulhern!> has joined #yocto11:51
*** Saur <Saur!pkj@nat/axis/x-nhsscovcpjdsetmh> has joined #yocto11:54
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC11:59
*** Saur <Saur!pkj@nat/axis/x-nhsscovcpjdsetmh> has quit IRC12:00
*** Stygia <Stygia!> has joined #yocto12:01
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto12:02
StygiaHeya. If I make a bbappend that contains a file named exactly like the one in the original recipe, with the intend to use the file I provide instead of the original one, will the original file be "overwritten" in D and used by do_install()? (The do install in the main recipe - I don't want one if I don't need it in my bbappend).12:02
StygiaIf not, I assume I can just do a do_install_append and install on top of the old one.12:02
*** cfo215 <cfo215!> has joined #yocto12:04
StygiaAnd on another note, this line here: PRINC := "${@int(PRINC) + 1}" This increments package revision by one, right?12:04
cfo215Morning everyone... to those involved with my problem... here are the results of the core-minimal sdk build.12:06
JaMaStygia: what you mean by "bbappend that contains a file named exactly like the one" ?12:06
JaMaStygia: are you talking about some file referenced from SRC_URI?12:07
*** sakoman <sakoman!> has joined #yocto12:07
StygiaJaMa, Yes exactly. The original recipe has a hosts file in SRC_URI, and I want to ensure that the file from my bbappend is used instead.12:07
StygiaJaMa, Sorry if I was unclear.12:07
StygiaCould I assume that, if I do a bbappend with a SRC_URI +=, that the file from my bbappend is what'll be used in the statement something like "install hosts ${D}/etc" ?12:09
tfStygia: you don't need to modify the SRC_URI12:11
tfjust provide the file and do the usual preppend on the path12:11
Stygiatf, Oh? I just do FILESEXTRAPATH_prepend and add it in?12:11
Stygiatf, Ah exactly. Cool. :)12:11
Stygiatf, Presumably I'd still need to increment the package revision, though, right?12:12
tfyes, I think so12:12
Stygiatf, Alright, cool. Seems simple enough.12:13
JaMaStygia: yes, but it uses your file in WORKDIR, then it's back on base recipe what it will do with it (to install it in $D or something else)12:17
StygiaJaMa, Exactly, that's what I want. :)12:18
StygiaJaMa, This is netbase, and we need to use our own hosts file to workaround a crazy bug we couldn't track down... so that's exactly what I want. Just to do the normal things with my file instead of the original.12:19
lpappWARNING: Host distribution "Debian-GNU-Linux-7" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.12:19
lpappdebian stable is unsupported? How come?12:19
JaMaStygia: understood, it just wasn't clear from that question what do you expect12:20
StygiaJaMa, Alright, sorry.12:20
StygiaJaMa, But that is exactly what I expected, so all good.12:21
cfo215update:  works from Makefile.  Environment probably needs tweaked.12:21
*** el_robin <el_robin!~el_robin@2a01:e0b:1:124:8c9e:801c:5ccb:6bdf> has quit IRC12:22
Crofton|workcfo215, weird, not dyn linker failure?12:22
cfo215Crofton|work, I thought you were going rafting today?12:23
Crofton|workI am just trying to get cuaght up b4 loading the car12:23
*** el_robin <el_robin!> has joined #yocto12:24
cfo215Crofton|work,  I'm jealous!  Anyhow.  the pastebin has everything I did and the results.  I can pastebin my env if that will help.12:24
*** scot <scot!~scot@> has joined #yocto12:26
Crofton|workI am annoyed the otehr problem went away12:27
Crofton|worksoemthing really funny is up12:27
Crofton|workI need to stop caring long enough to get out the door12:28
cfo215Crofton|work, I feel you.  I just want to compile my Qt app for ARM.  So frustrated at this point.12:29
Crofton|workwe want this to work12:30
Crofton|workis it "easy" for you install Fedora?12:30
cfo215I understand.  I want it to work to.  It will surely be better in the long run.  Beats having to do everything from scratch.12:30
Crofton|workalso, did you get anywhere with the touchscreen?12:31
*** e8johan <e8johan!> has joined #yocto12:31
*** drasko_ <drasko_!> has quit IRC12:31
cfo215Nowhere on the touchscreen yet.  -qws doesn't play with it.  I thought Qt was compiled with touchscreen support built in.12:32
*** Net147 <Net147!> has joined #yocto12:32
cfo215Crofton|work, can i "upgrade" my Ubuntu to fedora?  Or do I need to rebuild my system?12:33
Crofton|workis your app "big" you can compile on the bone12:33
Crofton|workI was hoping you had an extra box around12:33
cfo215That's what I thought.  I'll ask the IT peeps here if they have anything.12:34
cfo215What version of Fedora?12:34
*** ericben <ericben!> has quit IRC12:34
Crofton|workF19 is what I used12:34
lpappanyone knows why Debian stable is not supported anymore?12:34
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has quit IRC12:34
cfo215I can compile it on the bone.  I tried opkg qt4, and qt4-embedded but it couldn't find those.  I'll search the *.ipks for the correct name.12:35
cfo215I just "happen" to have that version on DVD sitting on my desk...12:35
*** zecke <zecke!~ich@> has quit IRC12:35
*** ericben <ericben!> has joined #yocto12:35
cfo215Do you use 32bit or 64bit?12:36
*** e8johan <e8johan!> has quit IRC12:37
cfo215I believe this is the correct file: packagegroup-qte-toolchain-target_1.0-r7.0_all.ipk12:40
cfo215to install on the BBB that is.12:40
Crofton|worktry it :)12:40
cfo215working on it... ;)12:41
*** zecke <zecke!~ich@> has joined #yocto12:41
*** Anusko <Anusko!~anusko@> has quit IRC12:42
*** Anusko <Anusko!~anusko@> has joined #yocto12:42
Crofton|workcan someone try endorsing me for OpenEmbedded and "Yocto Project" on linkedin12:42
*** B4gder <B4gder!> has quit IRC12:42
Crofton|workyes, I know the endorsement stuff is bs12:42
Crofton|workalso, I would to get the number of times I have been endorsed for trolling up :)12:43
* RP likes his Cat Herding skiil12:44
cfo215Crofton|work, if I get a machine for Fedora, I should be able to just move my files over, or am I going to have to start from scratch again?12:46
ant_workyou can move the downloads ;)12:46
cfo215that works...12:47
ant_workafter the time for changing distro a run of bitbake isn't so bad...12:47
RPCrofton|work: I can't see Yocto Project and OpenEmbedded on there :/12:47
cfo215I thought they are "interchangeable" for the most part.12:49
ant_workCrofton|work: I've noticed Fedora* and Ubuntu* distros seem suffering now and then. Trust me (and JaMa): with Gentoo we never had any issue apart one obscure binutils thing years ago12:49
bluelightningcfo215: in the way some people use the term Yocto Project, certainly12:50
Crofton|workI use Fedora, so problems get fixed :)12:50
bluelightningcfo215: strictly speaking the Yocto Project is an umbrella project and one (major) sub-project under that umbrella is to enhance BitBake and OE-Core12:50
bluelightningcfo215: so strictly speaking the build system is OpenEmbedded12:51
ant_workCrofton|work:  it may sound strange but I'd suggest Gentoo to newcomers12:51
Crofton|workI suggest what I use :)12:51
ant_workah, golden rule...12:51
bluelightningfor least pain on a headless build server I use CentOS ;)12:52
bluelightningthere has been some fun with python there but buildtools solves that12:53
bluelightningfor master that is, dylan needs no additional help12:54
bluelightningdylan and earlier12:54
RPthe idea is that the buildtools-tarball should solve the various distro related problems we were seeing12:54
ant_workhe he.. it was already foreseen: OE builds OE12:55
bluelightningwell, an OE "SDK" (since buildtools-tarball is effectively an SDK) supports the build of OE ;)12:56
ant_workRP: by the way, is the issue of /usr still popular?12:56
bluelightningbut of course OE will build under an OE-built OS as well :)12:56
RPant_work: most of the userbase still use it12:57
RPant_work: the buildappliance is an OE image which can then run OE12:58
ant_workRP: wrt /usr -> /  I'm hearing opinions like "let those distros sink into oblivion"12:59
RPant_work: I think it makes sense to maintain configurability with the project so I'd certainly not support that13:00
ant_workRP: I was planning to build a small image with meta-micro but I'm still exitating13:02
ant_work*hesitating fwiw13:03
lpapp3: linux-yocto-3.4.59+gitAUTOINC+f36797c2df_cdd7a54692-r4.5 do_install (pid 29353) -> why is it getting stuck in here?13:03
*** tomz <tomz!> has joined #yocto13:07
*** tomz is now known as Guest8979213:07
Crofton|workRP, I endiorsed you for OpenEmbedded and tried "Yocto Project" in "'s13:08
*** jeremiah <jeremiah!> has quit IRC13:09
*** vicky <vicky!~vicky@> has quit IRC13:09
*** smartin_ <smartin_!> has joined #yocto13:14
*** smartin <smartin!> has quit IRC13:15
*** Anusko <Anusko!~anusko@> has quit IRC13:35
cfo215Crofton|work, hopefully I won't run out of space on the BBB.  Also, I rather do my development on my PC not the target.  Kind of defeats the purpose.13:35
*** Anusko <Anusko!~anusko@> has joined #yocto13:35
cfo215bluelightning, thanks for the clarification.13:36
*** Net147 <Net147!> has quit IRC13:36
Crofton|worksure, but you need something that works, having multiple paths to success is always a good idea13:39
lpappwhat is the best practice to handle SOURCE_MIRROR_URL ?= "file://source_mirror/sources/" for in repository state and downloads stuff?13:44
lpappfile://${TOPDIR}/build/ etc or something else?13:44
*** zenlinux <zenlinux!> has quit IRC13:44
lpappJaMa: so what did you not like about the external host bin change13:58
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-ueyhznoqgepgzgxi> has quit IRC14:01
lpappbluelightning: is there a download dir variable that can be used in local.conf?14:02
*** thesignal <thesignal!~deadbot@> has quit IRC14:02
bluelightninglpapp: DL_DIR?14:02
*** thesignal <thesignal!~deadbot@> has joined #yocto14:02
lpappbluelightning: is that accessible for local.conf?14:03
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-hzrsnrtkwjyrcyur> has joined #yocto14:03
*** michael_e_brown_ <michael_e_brown_!> has joined #yocto14:04
*** mebrown <mebrown!> has quit IRC14:06
*** michael_e_brown_ <michael_e_brown_!> has quit IRC14:09
*** mebrown <mebrown!> has joined #yocto14:10
bluelightninglpapp: absolutely14:11
JaMalpapp: that I had to modify also other qt5 modules in order to support it (and similar changes are needed for cmake support)14:15
lpappJaMa: well, cmake is just following qmake.14:17
lpappyes, that is bad if other modules require it because it should be a one-shot action in qtbase.14:18
RPCrofton|work: it didn't show up :/14:18
Crofton|workth eOE one did?14:18
lpappbluelightning: ok, thanks so I need to use that for this?
Crofton|workwe need to work on our linkedin gaming14:18
lpappi.e. is it enough?  INHERIT += "own-mirrors"14:18
lpappor, I also need, SOURCE_MIRROR_URL ?= "file://${DL_DIR}"?14:19
JaMalpapp: see
*** _alex_kag_ <_alex_kag_!~alex_kag@> has quit IRC14:19
lpappluckily, v8 is history soon.14:20
lpappso is qtjsbackend14:20
*** michael_e_brown_ <michael_e_brown_!> has joined #yocto14:21
*** mebrown <mebrown!> has quit IRC14:21
JaMaI must admit that I don't follow qt5 so closely to know that, but still it's something which doesn't work with simple -external-host-dir out-of-the-box14:21
lpappwhy not14:22
lpapphmm, I need to add uthash in my layer for now.14:25
lpappwhich recipes-foo subsystem should I choose for that?14:25
lpappthe project ships 4 header files, that is all ... it is only for development.14:25
lpappbut "devtools" sounds wrong for this as this is not a tool.14:25
lpappbluelightning: ^14:26
lpappmaybe recipes-extended14:26
* bluelightning doesn't know what uthash is14:26
lpappC preprocessor implementations of a hash table and a linked lis14:26
bluelightningrecipes-support or recipes-devtools I would think14:27
lpappit is not a tool14:27
bluelightningbut ultimately it's your layer and the system doesn't care what directory it's in...14:27
lpappit is 4 header files.14:27
lpappwell, I plan to propose it back later tonight to some layer14:27
lpappok, I am fine with recipes-support14:28
*** zecke <zecke!~ich@> has quit IRC14:28
*** mebrown <mebrown!> has joined #yocto14:32
lpappbluelightning: right, so what is the best way not to run any confiure, make whatsoever?14:33
*** michael_e_brown_ <michael_e_brown_!> has quit IRC14:33
lpappjust install the four headers in the tarball downloaded?14:33
lpappdo I even need to mention the installationo f them explicitly?14:33
lpappinstallation of them*14:33
bluelightningdepends if it supports "make install"14:33
bluelightningwell actually14:33
bluelightningif it's not autotooled you need to write your own do_install14:33
lpappbluelightning: ls src14:34
lpapputarray.h  uthash.h  utlist.h  utstring.h14:34
lpappthat is all14:34
lpappno makefiles, no configure, whatsoever.14:34
lpapptests folder is full of c test sources.14:34
lpappbut I do not need that one.14:34
lpappthere is a makefile in there.14:34
bluelightningright, then you'll need to install them in your own do_install with install -m 0644 ...14:35
lpappright, thanks.14:35
*** Anusko <Anusko!~anusko@> has quit IRC14:37
*** scot_ <scot_!~scot@> has joined #yocto14:37
*** mebrown <mebrown!> has quit IRC14:37
*** Anusko <Anusko!~anusko@> has joined #yocto14:37
*** scot <scot!~scot@> has quit IRC14:38
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has joined #yocto14:39
lpappbluelightning: this, right? install -m 0644 ${S}/src/*.h ${D}${includedir}14:40
bluelightninglpapp: looks OK14:41
*** mebrown <mebrown!> has joined #yocto14:41
lpappthanks.. also, there is a one-command syntax for this repetitive pattern: bitbake foo -c clean && bitbake foo14:41
*** scot_ <scot_!~scot@> has quit IRC14:43
*** kbart <kbart!~KBart@> has quit IRC14:45
lpappbluelightning: install: target `/home/lpapp/Projects/Yocto/poky-dylan-9.0.1/build/tmp/work/armv5te-linux-gnueabi/uthash/1.9.7-r1/image/usr/include' is not a directory14:45
lpappI need to create that explicitly?14:46
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has quit IRC14:51
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has joined #yocto14:52
lpappyeah, apparently..14:52
lpappor is there a nicer way?14:53
lpappother than:     install -m 755 ${D}${includedir}14:53
lpapp    install -m 0644 ${S}/src/*.h ${D}${includedir}14:53
*** mebrown <mebrown!> has quit IRC14:54
lpappinstall -dm755 ${D}${includedir}*14:54
*** mebrown <mebrown!> has joined #yocto14:54
*** scot_ <scot_!~scot@> has joined #yocto14:56
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has quit IRC14:58
*** michael_e_brown_ <michael_e_brown_!> has joined #yocto15:00
*** davest <davest!~Adium@> has joined #yocto15:01
*** jeremiah <jeremiah!> has joined #yocto15:01
*** mebrown <mebrown!> has quit IRC15:01
*** andyross <andyross!> has joined #yocto15:05
*** jeremiah <jeremiah!> has quit IRC15:06
*** zecke <zecke!> has joined #yocto15:06
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has joined #yocto15:08
*** ant_work <ant_work!> has quit IRC15:10
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has quit IRC15:12
lpapphmm, I just realized stuff is not stripped by default15:13
lpappis there a yocto catch up setting for that to strip everything possible?15:13
bluelightningit does strip binaries as part of packaging15:15
bluelightningsymbols are split out to the -dbg packages and then stripped from the binaries15:15
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has quit IRC15:16
lpappah, as part of the packaging, thanks.15:17
*** jeremiah <jeremiah!> has joined #yocto15:20
*** _alex_kag_ <_alex_kag_!~alex_kag@> has joined #yocto15:20
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-hzrsnrtkwjyrcyur> has quit IRC15:21
*** zecke <zecke!> has quit IRC15:21
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-anxffqtbhjymbcdt> has joined #yocto15:22
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-iugkuafcqvstdoff> has joined #yocto15:23
*** jeremiah <jeremiah!> has quit IRC15:25
*** Crofton <Crofton!> has quit IRC15:28
*** zenlinux <zenlinux!> has joined #yocto15:34
*** slaine <slaine!~slaine@> has quit IRC15:35
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-iugkuafcqvstdoff> has quit IRC15:37
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-ncxdbbiiuscpvmld> has joined #yocto15:37
*** joseppc <joseppc!> has quit IRC15:38
*** mihai <mihai!~mihai@> has quit IRC15:39
*** ezekieljams <ezekieljams!> has joined #yocto15:42
*** eballetbo <eballetbo!> has quit IRC15:43
lpappbluelightning: so I should not check anything in, inside the downloads folder which starts with "git2"?15:44
bluelightningpersonally I wouldn't put downloads into a VCS but if you feel you must, the answer is yes exclude those15:45
*** ezekieljams is now known as embeddedZ15:47
lpappbluelightning: thanks15:51
*** zecke <zecke!> has joined #yocto15:55
*** belen <belen!~Adium@> has quit IRC15:57
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto15:59
StygiaThe last 10 minutes really make me wish I'd either unsubbed from oe-devel@ or taken the time to set up mail sieve.... :P But good on Martin Jansa, whoever that is.15:59
lpappStygia: /whois JaMa16:00
*** belen <belen!~Adium@> has joined #yocto16:00
StygiaIf you've no idea what I'm on about, check your email.16:00
*** zecke <zecke!> has quit IRC16:01
kergothdefinitely sounds like you need to setup some filtering16:01
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC16:01
* lpapp feels the time to unsubscribe from oe-devel. :p16:01
*** zecke <zecke!> has joined #yocto16:01
*** Anusko <Anusko!~anusko@> has quit IRC16:02
* kergoth didn't even notice16:02
*** Anusko <Anusko!~anusko@> has joined #yocto16:02
lpappI think the other one was worse with 18016:02
JaMaStygia: you shouldn't read your e-mail on android phone or where do you read it16:03
*** acidfu <acidfu!~nib@> has joined #yocto16:03
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has joined #yocto16:03
JaMaStygia: 1000 e-mails per hours and mutt isn't even shown in htop :)16:03
lpappis there a pattern deletion option on the gmail webinterface?16:04
lpappwhen someone sends so many changes?16:04
StygiaJaMa, Hah it's not that it's performance-heavy, it's that I've neglected to actually implement the filter, so I got a shitton of mails all at once.16:04
StygiaJaMa, And it's not an issue really, I just didn't see 30+ emails at once coming anytime soon. :P16:05
kergothi use gmail, but i filter so patches are auto-archived, and use a separate patch review saved search, so only non-patch-review discussions hit the inbox16:05
kergothget used to it :)16:05
kergothso, turns out i have no immodules in gtk+3 because whoever added gtk+3 didn't pull forward a required patch from gtk+216:06
* JaMa is using filters on gmail to split the flow into 30+ labels with auto-archive, then isync to get them in local maildir and mutt to read them from local storage16:06
* kergoth rolls eyes and submits patch16:06
JaMamost annoying part on this setup is that in order to delete some e-mail from "All mail" folder I have to locally move it to trash and push it with isync back to gmail16:07
kergothi have fond memories of procmail+mutt16:09
kergothgood times16:09
kergothAnyone else playing around with using buildtools-tarball to build on old distros?16:10
erenshould I cross post yocto and oe-dev for general question?16:10
erenI mean, CCing lists16:10
*** Stygia <Stygia!> has quit IRC16:10
lpappJaMa: I still have these,
lpappeven with BB_GENERATE_MIRROR_TARBALLS = "1"16:11
kergothreally depends on what the discussion is about16:11
* eren uses mutt + offlineimap. didn't even notice the performance problem :)16:11
JaMalpapp: that's what you want isn't it?16:11
erenkergoth: it's about an image creation process for a new BSP layer16:11
lpappJaMa: I want to avoid git in favor of tarballs.16:11
*** elmi82 <elmi82!> has quit IRC16:12
JaMalpapp: fetcher will unpack tarballs into git2/ folder16:12
JaMalpapp: tarballs are only for transfer between your mirror and builder16:12
lpappJaMa: I wanna check in stuff in downloads and sstate16:13
lpappand I do not wanna have git in there, only tarballs.16:13
*** johnsoga <johnsoga!4542f923@gateway/web/freenode/ip.> has joined #yocto16:13
lpappunfortunately, BB_GENERATE_MIRROR_TARBALLS = "1" do not seem to help with this.16:15
*** Jefro <Jefro!> has joined #yocto16:15
JaMayes it only generates mirror tarballs :)16:15
lpappso, I was then right on the mailing list, it is N/A for my case.16:16
lpappnot sure what that is supposed to mean.16:17
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has quit IRC16:18
JaMabitbake needs to unpack them in order to checkout some revison to WORKDIR16:18
*** Stygia <Stygia!> has joined #yocto16:18
JaMaif you don't want to see unpacked tarballs then you cannot build anything16:18
lpappI do not wanna see .git16:19
lpappI wanna see tarballs.16:19
lpappbut fwiw, putting that variable in generates the same downloads folder as without16:19
lpappI cannot see the difference.16:19
*** Corneliu <Corneliu!c0c6972b@gateway/web/freenode/ip.> has quit IRC16:19
JaMarsync has nice option to exclude .done, svn/, git2/ in order to sync downloads directory to some PREMIRROR server16:19
*** munch <munch!> has joined #yocto16:20
lpappwe do not wanna have a mirror server16:20
lpappdownloads is pretty convenient for everyone involved.16:20
lpappalso, we do not have time for a lot of extra work.16:20
JaMaI probably don't understand your use-case, because for me it works fine and rsync call isn't a lot of extra work16:22
*** bluelightning_ is now known as bluelightning16:22
lpappyou need to host the mirror etc ...16:23
lpappyou need to configure server, etc etc16:23
Crofton|workheh, turning off email computer really help me get out of here :)16:23
lpappit is a lot of additional work for no apparent gain.16:23
lpappat least for me..16:23
JaMalpapp: and your plan is to share downloads directory on floppy disks or what?16:23
lpappgit add ./downloads && git push -> would be simpler16:23
lpappJaMa: ?16:23
lpappno, check the mailing list16:23
*** Krz <Krz!c0c6972b@gateway/web/freenode/ip.> has joined #yocto16:23
lpappI described that 1-2 weeks ago16:24
KrzHi guys I want to do something unusual, don't shoot16:24
JaMaand what prevents you from git add && git push? just add unwanted directories into .gitignore16:24
lpappJaMa: that it does not work.16:24
KrzI want to place tarball with sources of my app inside a Yocto layer16:24
lpappJaMa: it is trying to fetch stuff from git.16:24
lpappJaMa: which fails due to upstream unreliability.16:24
lpappso CI continuously fails.16:24
Krzis it as easy as pointing SRC_URI to "./my-tarball.tgz"  ?16:24
lpappwhich stops the integration.16:24
JaMalpapp: are you using tag= in SRC_URI?16:25
lpappKrz: yes16:25
lpappKrz: file://my-tarball.tgz16:25
Krzlpapp: has anybody done that before? is that really bad?16:25
JaMalpapp: that's the only place where it runs git ls-remote upstream-site16:25
lpappKrz: no, I do the same for our own softwares.16:25
lpappKrz: in our bsp/distro layer.16:25
Krzlpapp: ok, that's grand, thanks16:25
lpappof course, it would be nicer to have download url for the release etc, but meh16:26
JaMaand how is "git2/" removal going to help with 18:25:58 < lpapp> JaMa: which fails due to upstream unreliability.16:26
lpappJaMa: these are poky packages. I use whatever Yocto uses.16:26
lpappJaMa: I have the same downloads folder generated w/ and w/o BB_GENERATE_MIRROR_TARBALLS16:27
*** Stygia <Stygia!> has quit IRC16:27
JaMaare you 100% sure that you had BB_GENERATE_MIRROR_TARBALLS disabled?16:27
JaMawell you can have the tarballs there if they were downloaded from some MIRROR16:28
lpappJaMa: there are a few packages fetching stuff from git, even for the Yocto releases.16:29
JaMaBB_GENERATE_MIRROR_TARBALLS only ensures that tarballs are generated on your machine everytime do_fetch finds new source16:29
lpappJaMa: which means the Yocto releases will not work for people with CI etc due to upstream repo unreliabilities.16:29
lpappof course, you can solve it with an external mirror, etc, but I think it would be simpler for many, including us, if those tarballs are generated in downloads by an option when building the repository.16:30
lpappand then downloads are checked in, and when it is checked out by someone it just works, including the CI16:30
JaMahave you ever seen ?16:30
JaMayes that's what BB_GENERATE_MIRROR_TARBALLS does16:31
lpappJaMa: no, but we cannot trust that either.16:31
lpappwe would like to solve it ourselves rather than putting our business on someone's potential unreliability.16:31
lpappok, so where are the mirror tarballs generated?16:32
lpappdownloads is the same as without that variable.16:32
JaMagit tarballs in your downloads directory are probably downloaded from here (like
lpappgrep -rn BB_GENERATE_MIRROR_TARBALLS ./conf/local.conf16:32
JaMause bitbake -e16:32
lpappI have that u-boot tarball even without BB_GENERATE_MIRROR_TARBALLS16:32
JaMaI'm not surprised so much is in default MIRRORS16:33
*** acidfu <acidfu!~nib@> has joined #yocto16:34
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has joined #yocto16:34
lpappso BB_GENERATE_MIRROR_TARBALLS=1 is the default?16:34
lpappor something else by default doing its/similar job?16:35
JaMa18:29:42 < JaMa> well you can have the tarballs there if they were downloaded from some MIRROR16:35
* lpapp has done a git rm -r downloads/git216:35
lpappbut if the tarballs are downloaded from mirrors16:36
lpappwhy is bitbake trying to use the git version when the tarballs are there?16:36
lpappgit has some preference over the tarballs when both present?16:36
JaMahave you read the bug report about versioned snapshots?16:37
lpappI skimmed through, so not in details, no.16:37
JaMa18:19:40 < JaMa> bitbake needs to unpack them in order to checkout some revison to WORKDIR16:37
JaMait downloads tarball with compressed git checkout just to skip git clone from unreliable and possibly slower upstream site16:38
lpappI would not like to have SRCVER check.16:38
lpappas I do not wanna use VCS at all.16:38
lpappIOW, I wanna have tarballs without .git inside.16:39
JaMathat's what that bug is about16:39
lpappI am fine without version tracking.16:39
lpappas it is not critical here.16:39
lpappone version is fine without an explicit version number16:39
lpappwe do not get more than one from poky, and when do it is a major upgrade, so everything would be rewritten.16:39
*** _alex_kag_ <_alex_kag_!~alex_kag@> has quit IRC16:40
lpapplet us see if "git rm -r ./downloads/git2 && git commit ./downloads/git2" fixes the CI16:40
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto16:42
*** eren` <eren`!~eren@unaffiliated/eren> has joined #yocto16:45
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC16:45
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto16:45
*** eren <eren!~eren@unaffiliated/eren> has quit IRC16:48
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto16:48
*** belen <belen!~Adium@> has quit IRC16:49
*** pidge <pidge!> has quit IRC16:49
*** belen <belen!~Adium@> has joined #yocto16:51
lpappJaMa: now, I read through in details. It is what I thought it is.16:51
lpappJaMa: basically sane mirror creation, and gpl compliance help.16:52
lpappbut if you need only one version, this is not necessary.16:52
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC16:53
*** zeeblex1 <zeeblex1!apalalax@nat/intel/x-cpqsonphydbwyywn> has left #yocto16:55
cfo215Anyone have any experience with Sato on Beaglebone Black?16:56
cfo215last time I tried it I came up with the display "mirrored" on the lcd cape7.  e.g. if you were to look at it in a mirror then it would look correct.16:57
kergothHmm, could be interesting to set up autocreation of DISTRO_FEATURE_<feature> for each distro feature, to make dependency on distro features less brittle. instead of depending on the full value, we'd just depend on the existance or nonexistance of the particular features we care about, so random distro feautre changes woudln't affect you, making the checksums less brittle16:57
kergothRP, bluelightning_: thoughts on something like that?16:57
*** sakoman <sakoman!> has quit IRC16:58
*** belen <belen!~Adium@> has quit IRC16:59
KrzI created additional layer17:01
RPkergoth: hmm, its an interesting idea17:01
bluelightning_kergoth: yes, intriguing17:01
*** bluelightning_ is now known as bluelightning17:01
lpappthe image file is copyrightable?17:01
Krzspecified in mylayer/conf/layer.conf BBFILE_COLLECTIONS += "abc"17:01
RPkergoth: my other though was to teach the python parser about base_contains()17:01
Krzand now my build fails saying ERROR: BBFILE_PATTERN_abc not defined17:02
bluelightningRP: or, have a different in-language construct to replace it17:02
RPbluelightning: yes, although I have thought about ans struggled to come up with that17:02
bluelightningKrz: have you defined that?17:02
bluelightningcfo215: I didn't get my original bb to start X at all, so you're already further17:03
kergothteaching the parser to be smart about base_contains could be rather ugly.. currently we only really support dependency on other variables, not dependency on a segment of another variable :) might need internal temporary vars17:03
RPkergoth: did you see the cookerdata patches? I was wondering about droping the direct usage of bitbake.conf and requiring a bblayers.conf file17:03
BCMMi made what i thought was a trivial change to a recipe, and a whole lot of dependencies appear to have been pulled in. can anybody help me with getting a dependency graph to work out what happened?17:03
RPkergoth: we left it in whilst we experimented with bblayers but I think that is making sense and here to stay now17:04
BCMMi'm trying to use the output of bitbake -g, but i've never used graphviz before, and it's making *very* wide, short graphs that are basically illegible17:04
*** sakoman <sakoman!> has joined #yocto17:04
cfo215bluelightning, bb or bbb?17:04
*** smartin <smartin!> has joined #yocto17:04
RPkergoth: I think that was the issue I ran into last time I tried to look at such a thing, yes :/17:05
cfo215I use a beaglebone black (bbb)17:05
bluelightningcfo215: bb (original) in my case17:05
Krzbluelightning: ok I did now, I had a look at other layers. They use this funny variables like BBFILE_PATTERN_<myname> etc.17:05
Krzbluelightning: thanks17:05
cfo215err... trying to use...17:05
*** smartin_ <smartin_!> has quit IRC17:05
lpappis there an option for bitbake to query the available images in the layers rather than looking for them manually?17:06
bluelightninglpapp: bitbake-layers show-recipes "*image*"17:09
bluelightningof course that's just a query by name17:10
tfBCMM: have you tried -g -u depexp ?17:11
BCMMtf: thanks, just discovered that using google. man page doesn't really mention what it's for17:11
lpappbluelightning: got a clue?
BCMMtf: "reverse depends" is the thing that causes the selected package to be installed right?17:12
lpappbluelightning: trying to use my first image...17:12
bluelightninglpapp: looks like you've upgraded from denzil to dylan; tasks were renamed to packagegroups17:13
bluelightninglpapp: it's in the migration notes in the manual17:13
cfo215it seems as if meta-toolchain-qte is not building Qt with -qt-gfx-transformed option turned on.. I'm getting "transformed: driver not found" on my BBB.  Who handles/supports open-embedded core recipes?17:13
lpappbluelightning: this is my image file,
lpapp -> ok.17:14
tfBCMM: yes17:14
*** mulhern <mulhern!> has quit IRC17:14
BCMMtf: why are their packages that have only themselves as a reverse dep?17:14
bluelightningcfo215: the Qt4 recipes are maintained by me, as it happens17:14
bluelightningcfo215: that is odd17:15
cfo215bluelightning,  afaik, it's supposed to be included by default during the bitbake.17:15
tfBCMM: no idea17:15
tfBCMM: perhaps a bug the depexp app17:15
BCMMor maybe some cached information is broken17:16
tfBCMM: no, I don't think so, it's always been like that in the list17:16
BCMMare there specific steps i should take if i "git pull" layers i'm using between builds?17:16
tfBCMM: it really depends on the nature of the changes that come in17:17
bluelightningcfo215: that's what I would have thought too17:17
tfBCMM: mostly you should be able to just run a build again17:18
lpappbluelightning: so my image is supposed to build what image-core-minimal builds?17:18
tfbut sometimes it is necessary to wipe out the tmp dir17:18
BCMMtf: heh, it looks like i might have called my bbappend file ".bb" instead of ".bbappend"... that's probably where the deps came from, somehow17:20
kergothBCMM: if it's accounting for runtime dependencies, that can easily explain a self referene. any given recipe emits multiple binary packages, and they depend on one another17:21
BCMMkergoth: you mean the stuff that only rdepends from itself?17:21
kergothI dont understand the question17:22
kergothagain, a recipe's binary packages depend on one another. e.g. -dev usually depends on the main package17:22
bluelightninglpapp: see Task Recipes17:22
kergoththat doesnt' mean thats all they depend on, many runtime dependencies are generated at build time17:22
bluelightninglpapp: if it helps you can always look at the dylan version of core-image-minimal17:22
*** ant_home <ant_home!> has joined #yocto17:23
lpappbluelightning: refman?17:23
bluelightninglpapp: yes17:24
lpappbluelightning: ah, you mean, the porting. That is fixed already.17:24
lpappbluelightning: I am just asking in general as I inherited that image file.17:24
lpappand what I basically need is core-image-minimal + a couple of custom softwares.17:24
lpappso I would like to extend core-image-minimal17:24
bluelightninglpapp: I always recommend copy and modify for image recipes17:25
lpappbluelightning: the image built successfully, but I am not sure what it was supposed to build, at least not exactly anyway.17:25
*** Anusko <Anusko!~anusko@> has quit IRC17:32
*** Anusko <Anusko!~anusko@> has joined #yocto17:32
*** eren` <eren`!~eren@unaffiliated/eren> has quit IRC17:32
BCMMam i right in saying that, if I have a .bb recipe with the same filename in two different layers, the one that comes later in bblayers.conf is used and the other one ignored totally?17:36
kergothorder in bblayers.conf affects .conf/.bbclass priority17:37
kergothrecipe priority is controlled byt eh priorities defiend in the layer.conf files17:37
BCMMkergoth: ah, thanks17:38
BCMMkergoth: how to bbappends work? can a .bbappend effect the interpretation of a .bb from a higher-priority layer?17:38
kergothbbappends are appended to the recipe17:39
kergothnot unlike concatenating the files17:39
bluelightningand they are applied in layer priority order17:39
*** mulhern <mulhern!> has joined #yocto17:39
*** mulhern <mulhern!> has quit IRC17:40
*** zecke <zecke!> has quit IRC17:44
BCMMare higher or lower numbers high priority?17:45
bluelightningBCMM: higher17:46
*** Anusko <Anusko!~anusko@> has quit IRC17:49
*** Anusko <Anusko!~anusko@> has joined #yocto17:49
*** Anusko <Anusko!~anusko@> has joined #yocto17:51
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC17:53
*** panda84kde <panda84kde!> has quit IRC17:53
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC17:53
*** johnsoga <johnsoga!4542f923@gateway/web/freenode/ip.> has quit IRC17:54
*** mihai <mihai!~mihai@> has joined #yocto17:56
*** _alex_kag_ <_alex_kag_!~alex_kag@> has joined #yocto18:01
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC18:01
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto18:02
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC18:04
*** behanw <behanw!> has quit IRC18:04
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto18:04
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC18:04
*** Krz <Krz!c0c6972b@gateway/web/freenode/ip.> has quit IRC18:06
*** walters <walters!walters@nat/redhat/x-aarbrfctrifcibqx> has joined #yocto18:10
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto18:20
BCMMkergoth: can you direct me to some sort of documentation about setting priorities? i'm clearly done something wrong, but can't work out how18:21
BCMMi know my recipe can be found, because if i move the other layer's recipe, mine gets used18:21
BCMMbut if i leave the other layer's one in place, it does not18:22
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto18:23
Garibaldi|workHi folks, I'm building an image for mips and it's using the o32 ABI, but I need the n32 ABI.  Where's the knob to change that?18:32
lpappJaMa: do you know if Joe still actively maintains meta-networking?18:33
lpapp(or if it is better to fork)18:33
JaMayes, he is actively maintaining it18:34
lpappthen I do not understand why he has replied to my change.18:35
Garibaldi|workI guess TUNE_FEATURES = "mips64-32"18:35
Garibaldi|workor DEFAULTTUNE18:37
zibrijama: heh, i was about to send the same change for the xbmc recipe (libmad dep). nice work :)18:37
sgw_lpapp: possibly on vacation, I think he will be back after the US Long weekend (next week sometime)18:39
JaMazibri: it still fails, but at least a bit later in do_compile (like it always did) xbmc/utils/MathUtils.h:101:28: error: impossible constraint in 'asm'18:39
zibrihum, i got different failures.18:40
JaMathis one is repeated in every "State of bitbake world" update...18:40
zibrioptional deps (swig, java) causing fatal errors. and some other stuff18:40
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto18:40
lpappsgw_: right, I was looking for some vacation message on the mailing list...18:41
zibrinot sure if adding swig-native dep is the correct solution, even more hesitant about adding java deps :/18:41
zibriand even if i do, it fails somewhere else anyways :)18:41
kergothI really hate it when people post patch series without [PATCH] or equivalent18:49
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has quit IRC18:54
*** brm <brm!da653619@gateway/web/freenode/ip.> has joined #yocto19:00
brmAnyone know if the beaglebone black linux 3.8.13 kernel can have the RT-linux patches applied?19:00
*** Anusko <Anusko!~anusko@> has quit IRC19:03
*** Anusko <Anusko!~anusko@> has joined #yocto19:03
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC19:09
*** [simar|on] <[simar|on]!~simar@> has joined #yocto19:10
*** tor <tor!> has quit IRC19:12
brmIs it as simple as setting LINUX_KERNEL_TYPE to pre-emtive-rt in the kernel recipe file ..?19:12
zeddiiif you are using linux-yocto, it's the linux-yocto-rt recipe.19:12
zeddii(which sets that variable). if you have extra board patches, that I don't have in that tree, you can add them via a layer.19:13
*** acidfu <acidfu!~nib@> has joined #yocto19:20
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has joined #yocto19:20
brmzeddii: I am using the linux-mainline source19:25
zeddiithen you need to apply everything yourself.19:25
brmhow do i go about that?19:25
zeddiibut if you are on 3.8.x, then linux-yocto-3.8 has everything you need already.19:25
brmI am on 3.8, are you saying it has the kernel patched allreaty for RT19:26
zeddiithe linux-yocto kernel has branches for different features standard/preempt-rt/base has it already applied.19:27
brmMy kernel is linux-mainline-3.8.1319:27
*** _alex_kag_ <_alex_kag_!~alex_kag@> has quit IRC19:27
zeddiiin that case, you need to grab the patches, and add them to the SRC_URI, just like any recipe does.19:28
brmSo I have to grab the patches from linux-yocto-3.8 and apply then to linux-mainline-3.8.13 in my layer?19:29
brmzeddii: Is that correct?19:32
zeddiiyou could, but I'd have to ask why :)19:32
zeddiisince they are already applied.19:32
zeddiior you can to go the upstream project and grab the -rt patch and apply it that way.19:33
brmWhat do you mean? Why I want real-time?19:33
zeddiino, I mean why yank patches out of a 3.8 linux-yocto recipe and apply them to another 3.8 kernel tree.19:33
zeddiiyou can of course do whatever you need to do, but there may be a faster way to do it.19:33
brmCause I don't know where to find the upstream patches?19:33
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has quit IRC19:34
*** bluelightning <bluelightning!> has joined #yocto19:35
*** bluelightning <bluelightning!> has quit IRC19:35
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto19:35
brmzeddii: I thought you said the patches were allready applied to linux-yocto-3.8.x not linuc-mainline-3.8.x?? Confused19:36
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has quit IRC19:36
zeddiii.e. I'm not sure where you are getting your linux-mainline-3.8.x, I assume it is a recipe you created ?19:37
brmyep what?19:37
zeddiiall of the patches I apply to linux-yocto can either be dumped from the tree, or found in git://
zeddiiI did say that the patches were on linux-yocto-3.8, branch standard/preempt-rt/base19:38
brmNo, linux-mainline is in the BBB receipe ... I am building images from meta-pansenti layer19:38
zeddiiok. so you can always go an try to extract my patches, or hit the linux-rt wiki (google will find it with that), and you'll find the upstream patches.19:39
brmwhat do you mean "your patches" did you create the linux-yocto ones?19:40
*** _alex_kag_ <_alex_kag_!~alex_kag@> has joined #yocto19:42
*** cfo215 <cfo215!> has quit IRC19:45
zeddiibrm. yes, I've merged all of the core support for the linux-yocto* trees.19:45
zeddiicreate is too strong a work, integrated is more accurate :)19:46
*** AndersD <AndersD!> has joined #yocto19:46
zeddiiI've been porting and using preempt-rt since 2.6.12 though :)19:46
brmcool .. :)19:46
brmSo still strugling to find the patches for linux-mainline19:47
zeddiisec. let me post a gitweb link19:47
*** AndersD <AndersD!> has quit IRC19:48
zeddiiwarning, this will be a large patch:
brmIs this the correct place?
*** embeddedZ <embeddedZ!> has quit IRC19:48
zeddiiI have all my upstream sources in the commit logs19:49
zeddiiMerging patch-3.8.4-rt2 from:
zeddii(is what was in my log)19:49
brmOk, so I have a look at one of your merges, then do a similar thing on linux-mainline ...19:50
*** JimBaxter <JimBaxter!> has quit IRC19:53
brmGot to go thanks ..:)19:53
*** brm <brm!da653619@gateway/web/freenode/ip.> has quit IRC19:53
*** ant_home <ant_home!> has joined #yocto19:57
*** another_andy <another_andy!> has quit IRC20:02
*** seebs <seebs!> has quit IRC20:04
*** seebs <seebs!> has joined #yocto20:07
*** seebs <seebs!> has joined #yocto20:08
*** seebs <seebs!> has joined #yocto20:11
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC20:21
*** YoctoAutoBuilder <YoctoAutoBuilder!~YoctoAuto@> has joined #yocto20:21
*** embeddedZ <embeddedZ!> has joined #yocto20:24
*** mbroadst <mbroadst!~mbroadst@kde/developer/mbroadst> has left #yocto20:26
ant_homezeddii: around?20:47
zeddiiant_home, for a few more mins. yep. did I break something ? ;)20:54
ant_homesent mail about qemumips vs. 3.10 headers20:55
zeddiioh interesting. I can patch linux-libc-headers again to fix it up.20:56
Garibaldi|workfolks, I'm trying to build a minimal image for mips32 with DEFAULTTUNE = "mips64-n32", and I get a failure while trying to build busybox.  mips64-poky-linux-gnu32-ld:  applets/applets.o: file class ELFCLASS32 incompatible with ELFCLASS6420:57
Garibaldi|workany idea what I may have done wrong?20:57
-YoctoAutoBuilder- build #272 of nightly-x86-64-lsb is complete: Exception [exception interrupted] Build details are at
-YoctoAutoBuilder- build #278 of nightly-x86-lsb is complete: Exception [exception interrupted] Build details are at
Garibaldi|workdoes mips64-ciscovs-linux-gnun32-ld need the -mabi=n32 parameter that gcc uses?21:09
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has quit IRC21:09
*** brm <brm!da653619@gateway/web/freenode/ip.> has joined #yocto21:12
brmNeed some advice in applying a real-time patch to linux-mainline-3.8.13-r23a kernel21:13
brmpath upstream is called 3.8.13-rt15.patch and doesn't path cleanly ..21:13
brm5 files error ourt21:14
Garibaldi|workmips64-poky-linux-gnun32-ld: Attempt to do relocatable link with elf32-ntradbigmips input and elf64-tradbigmips output21:14
*** smartin_ <smartin_!> has joined #yocto21:14
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has joined #yocto21:18
Garibaldi|workI think no one is home21:23
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has quit IRC21:27
*** swex__ <swex__!~swex@> has quit IRC21:27
*** swex__ <swex__!~swex@> has joined #yocto21:28
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has joined #yocto21:36
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC21:42
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto21:43
brmI think you are right21:45
*** cfo215 <cfo215!> has joined #yocto21:52
bluelightningbrm: all files or just some files referred to in the patch?22:01
*** walters <walters!walters@nat/redhat/x-aarbrfctrifcibqx> has quit IRC22:01
*** Tartarus <Tartarus!> has joined #yocto22:03
*** Tartarus <Tartarus!> has left #yocto22:03
*** smartin_ <smartin_!> has quit IRC22:10
brmbluelightning: just some files in the patch .. 5 of them22:12
brmIt doesn't patch correttly in Yocto, it does work if I patch the kernel outside yocto22:13
brmI am using the linux-mainline kernel heavily patched in meta-beagleboard and trying to apply a RT patch22:14
brmkernel version is linux-mainline-
brmI think the meta-beagleboard patches are conflicting with the RT patches for the base kernel22:22
brmhow do I fix this?22:22
*** sakoman <sakoman!> has quit IRC22:30
*** sakoman <sakoman!> has joined #yocto22:32
*** cfo215 <cfo215!> has quit IRC22:35
bluelightningbrm: I don't know I'm afraid22:37
bluelightningbrm: the fact that some files don't match up suggests that either there is a conflict or the patch you're trying to apply wasn't meant for the version of the kernel you're applying it to22:38
brmlooks like I will have to merge the patch sets somehow22:38
brmThe beaglebone patches are definetely conflicting with the RT patch set ..22:39
bluelightningprobably easiest to do that externally in a separate git tree, at least that's the way I would do it22:39
bluelightningfrankly it would be easiest if everyone just got their stuff upstream22:39
brmI agree ..22:41
brmThere is something like 150 beaglebone patches to the kernel!!22:41
brmmake that 650 patches22:42
bluelightninghmm, that is quite a lot22:44
*** [simar|on] <[simar|on]!~simar@> has quit IRC22:44
*** zenlinux <zenlinux!> has quit IRC22:46
*** ericben <ericben!> has quit IRC22:52
*** ericben <ericben!> has joined #yocto22:59
mranostayJefro: going to troll my talk? :)23:09
*** cetola <cetola!> has joined #yocto23:12
*** blloyd_ <blloyd_!> has quit IRC23:18
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC23:32
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC23:33
*** musdem <musdem!> has joined #yocto23:39
*** ant_home <ant_home!> has quit IRC23:45
*** seebs <seebs!> has quit IRC23:46
*** munch <munch!> has quit IRC23:47
*** seebs <seebs!> has joined #yocto23:48
kergothHmm, we need to improve the ruby handling to be on per with perl/python23:50
*** andyross <andyross!> has quit IRC23:50
seebsI would not mind that at all. I get along with Ruby.23:50
kergothI never got around to learning it.. seems like once you know either ruby or python, the need to learn the other drops down, since they tend to overlap in where they're useful23:51
kergoththough ruby does have better support for DSLs23:51
seebsI mostly just like it better. Easier for me to read/write.23:54
*** eren <eren!~eren@unaffiliated/eren> has quit IRC23:57

Generated by 2.11.0 by Marius Gedminas - find it at!