Thursday, 2015-06-04

*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC00:01
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto00:01
*** OutOfNoWhere <OutOfNoWhere!~rpb@> has joined #yocto00:07
*** sjolley <sjolley!~sjolley@> has joined #yocto00:23
*** paulg_ <paulg_!> has quit IRC00:53
*** jmleo <jmleo!> has quit IRC00:53
*** alimon1 <alimon1!> has quit IRC01:06
*** paulg_ <paulg_!> has joined #yocto01:12
*** dlan_ is now known as dlan01:15
*** mcfrisk_ <mcfrisk_!> has joined #yocto01:21
*** mcfrisk <mcfrisk!mcfrisk@> has quit IRC01:22
*** thaytan <thaytan!> has quit IRC01:22
*** thaytan <thaytan!> has joined #yocto01:23
*** berton <berton!~fabio@> has quit IRC01:26
*** jmleo <jmleo!> has joined #yocto01:30
*** ntl <ntl!> has quit IRC01:33
*** thaytan <thaytan!> has quit IRC01:35
*** thaytan <thaytan!> has joined #yocto01:36
*** ryoshu <ryoshu!~kamil@unaffiliated/ryoshu> has quit IRC01:40
*** ntl <ntl!> has joined #yocto01:45
*** tomz <tomz!trz@nat/intel/x-qmdncirgfijpkowa> has quit IRC01:47
*** staylor <staylor!> has joined #yocto01:57
*** vdehors <vdehors!> has quit IRC02:06
*** vdehors <vdehors!> has joined #yocto02:06
*** tomz <tomz!trz@nat/intel/x-mwomvspsunlbrwyu> has joined #yocto02:28
-YoctoAutoBuilder- build #316 of nightly-arm-lsb is complete: Success [build successful] Build details are at
*** [Sno] <[Sno]!> has quit IRC03:11
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC03:24
*** paulg_ <paulg_!> has quit IRC03:28
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto03:37
*** irontia <irontia!d4178ac2@gateway/web/freenode/ip.> has quit IRC03:53
*** gabrbedd <gabrbedd!> has quit IRC03:55
*** smartin_ <smartin_!> has quit IRC03:57
*** smartin_ <smartin_!> has joined #yocto03:59
*** gabrbedd <gabrbedd!> has joined #yocto04:08
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC04:08
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto04:08
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC04:12
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto04:13
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC04:17
parrotwhat's the env variable that holds the location of file:// in a recipe?05:07
*** AndersD <AndersD!> has joined #yocto05:11
*** ntl <ntl!> has quit IRC05:33
*** roric <roric!~roric@> has joined #yocto05:44
*** staylor <staylor!> has quit IRC05:45
*** niteshnarayanlal <niteshnarayanlal!~niteshnar@fedora/niteshnarayanlal> has joined #yocto05:46
*** ntl <ntl!> has joined #yocto05:47
niteshnarayanlalrecently I had added few things to the rootfs05:47
niteshnarayanlaland now at the time of linux boot up I am getting05:47
niteshnarayanlalKernel panic - not syncing: No init found.  Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.05:47
niteshnarayanlalany help05:47
niteshnarayanlaldoes it something to do with the rootfs size ?05:48
niteshnarayanlalwhich is been modified after I have packaged extra things05:48
*** [Sno] <[Sno]!> has joined #yocto05:57
*** dvhart_ <dvhart_!~dvhart@> has joined #yocto06:01
AndersDniteshnarayanlal, normally not, though if you're using initramfs there might be an issue.06:05
AndersDniteshnarayanlal, it's more likely that something else has screwed up.06:05
AndersDDo you have any init in you're rootfs?06:05
*** hitlin37 <hitlin37!uid16371@gateway/web/> has joined #yocto06:06
*** hamis <hamis!~irfan@> has joined #yocto06:20
parrothow do I specify git cloning https repo in my recipe?06:24
*** DanielAdolfsson <DanielAdolfsson!> has joined #yocto06:28
*** mckoan|away is now known as mckoan06:50
mckoangood morning06:51
*** araldit <araldit!> has joined #yocto06:51
*** DanielAdolfsson <DanielAdolfsson!> has quit IRC07:06
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has joined #yocto07:06
*** jbrianceau_away is now known as jbrianceau07:06
*** tmpsantos <tmpsantos!> has joined #yocto07:12
*** diego_r <diego_r!> has joined #yocto07:17
AlexVaduvagood morning guys07:18
*** jku <jku!jku@nat/intel/x-pczeddqpbecsogtp> has joined #yocto07:19
*** sameo <sameo!~samuel@> has joined #yocto07:22
*** DanielAdolfsson <DanielAdolfsson!> has joined #yocto07:22
*** [Sno] <[Sno]!> has quit IRC07:28
*** [Sno] <[Sno]!> has joined #yocto07:31
*** Noor <Noor!~noor@> has left #yocto07:44
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto08:02
*** ant_work <ant_work!> has joined #yocto08:04
*** ant__ <ant__!> has joined #yocto08:04
bluelightningmorning all08:06
*** ant__ <ant__!> has quit IRC08:07
*** ant__ <ant__!> has joined #yocto08:08
*** JaMa <JaMa!> has joined #yocto08:12
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto08:16
*** skfax <skfax!> has joined #yocto08:17
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC08:22
*** belen <belen!Adium@nat/intel/x-qtdyekewetjvdrsl> has joined #yocto08:24
*** jimBaxter <jimBaxter!> has joined #yocto08:24
*** jchonig <jchonig!> has quit IRC08:30
*** rburton <rburton!> has joined #yocto08:42
*** manuel_ <manuel_!> has quit IRC08:49
*** RP <RP!> has quit IRC08:56
aralditI have a major problem, which perhaps some of you know how to deal with. Im  trying to build my own custom image based on the arago distro, but as I compile some QT5 packages I get a linker error: x86_64-arago-linux-g++: error: unrecognized command line option '-fuse-ld=gold' . Anyone know how I can resolve this09:00
*** RP <RP!> has joined #yocto09:06
abelloniarago for an x86 platform ?09:12
abelloniwhat a weird choice :)09:12
bluelightningaraldit: I'd assume the toolchain has been built without support for the gold linker09:22
aralditI honestly dont know - im digging into that right now09:23
bluelightningaraldit: depending on what you want to do, you could either enable it, or find how that -fuse-ld=gold is getting into the compiler command line and stop it09:23
bluelightningor... hmm, could it be that the version of gcc being used simply doesn't support -fuse-ld ?09:24
aralditbluelightning: It could be that.09:24
aralditbluelightning: Im using 4.709:25
bluelightninggranted that was qt4, but still09:25
aralditbluelightning: Im currently trying to remove the gold linker through in my file by adding LDGOLD = "" and DISTRO_FEATURES_remove = " ld-is-gold"09:27
*** LocutusOfBorg1 <LocutusOfBorg1!> has quit IRC09:28
bluelightningaraldit: that's not going to work09:28
aralditbluelightning: why is that?09:28
aralditI mean im bulding the sdk by usiing bitbake image -c populate_sdk09:29
bluelightningaraldit: the first problem is that you cannot set a variable read in one recipe or read at the global level from within another recipe09:29
*** manuel_ <manuel_!> has joined #yocto09:29
bluelightningif you want to remove ld-is-gold from DISTRO_FEATURES you will need to do so at the configuration level09:30
aralditbluelightning: I did this because i found this line in binutils: oe-core/meta/recipes-devtools/binutils/ ?= "${@base_contains('DISTRO_FEATURES', 'ld-is-gold', '--enable-gold=default --enable-threads', '', d)}"09:30
bluelightningright, I get that09:30
aralditbluelightning: Ok, what do you mean by at the configuration level09:30
bluelightningbut then there's the question of whether that will actually result in -fuse-ld=gold not being passed to the compiler in the qt build, I can't immediately tell if this will actually influence that09:31
aralditI can - It didn't work :-)09:31
*** tmcguire <tmcguire!~tmcguire@> has quit IRC09:31
bluelightningaraldit: effectively I mean in local.conf, although when you are changing things like this you should consider whether it would be better to create your own distro config09:32
bluelightningaraldit: ok, well I guess it's an academic point then09:32
bluelightningaraldit: I think you'd need to patch the Qt source as hinted by that Qt bug I linked above09:33
bluelightningassuming that -fuse-ld=gold is coming in from the Qt build process itself as it appears to be there09:33
aralditbluelightning: K, thanks for the advise. I will try to do that.09:33
*** tmcguire <tmcguire!~tmcguire@> has joined #yocto09:35
*** LocutusOfBorg1 <LocutusOfBorg1!> has joined #yocto09:40
skfaxHow can I expand upon a .bbappend defined in one layer X from another layer Y?09:53
*** tmcguire <tmcguire!~tmcguire@> has quit IRC09:53
*** tmcguire <tmcguire!~tmcguire@> has joined #yocto09:55
*** belen <belen!Adium@nat/intel/x-qtdyekewetjvdrsl> has quit IRC09:58
*** belen <belen!Adium@nat/intel/x-wksivxfubtdtaynn> has joined #yocto10:00
*** grma <grma!> has quit IRC10:03
*** grma <grma!> has joined #yocto10:03
jku skfax: all bbappends should get applied, in layer priority order. Does that answer the question?10:24
*** belen1 <belen1!~Adium@> has joined #yocto10:25
skfaxjku: yes. i guess i've just made some mistake when naming the new bbappend files or something10:26
*** abbu <abbu!6e5dd462@gateway/web/freenode/ip.> has joined #yocto10:26
*** belen <belen!Adium@nat/intel/x-wksivxfubtdtaynn> has quit IRC10:27
rburtonskfax: bitbake -e is your friend in this situation10:27
skfaxrburton: i tried it for the image i'm building now; but the file is massive10:27
skfaxdoing some searching now to see if i can figure it out :)10:28
bluelightningskfax: you can also try bitbake-layers show-appends10:29
skfaxwell the "-e" gave me 21k lines. this option gave me 71. easier :D10:30
bluelightningif your bbappend isn't listed there, either it's not matched by BBFILES in your layer's layer.conf (in wrong location or BBFILES isn't set up to match .bbappend files); or the layer itself isn't actually enabled10:30
skfaxit is listed, but there is a warning showing which might be relevant: "WARNING: missing append for preferred version"10:31
bluelightningah right, yes10:32
skfaxdoes the "show-appends" command show all bbappend files found within the active layers? or does it show all bbappend files which successfully match an available recipe?10:33
skfaxsorry, i misread the file. yes it does the latter10:35
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC10:46
*** OutOfNoWhere <OutOfNoWhere!~rpb@> has quit IRC10:50
likewiseJaMa: thanks for updating meta-qt5 to match 4.5.x. Did you test this against a certain platform?10:51
JaMalikewise: qemux86(-64) and couple ARM devices10:52
likewiseJaMa: Did you test the QtWebEngine? I have trouble getting it to work on i.MX6.10:54
JaManot much, we haven't integrated it fully yet10:55
likewiseJaMa: There is this bugfix, that is now in the 5.5 branch, but I'm not sure if it applied to the 5.4.x branch:
*** ryoshu <ryoshu!~kamil@unaffiliated/ryoshu> has joined #yocto10:57
likewiseJaMa: Also, in the I had to add "-qpa eglfs" to the PACKAGECONFIG[gles2] entry in order to use the new QPA EGLFS. Otherwise it would fall back to xcb, which however I didn't have. (removed x11 and wayland DISTRO_FEATURES).10:58
JaMatru I should probably revisit qpa in PACKAGECONFIGs, we're using:10:59
JaMameta-luneui/recipes-qt/qt5/qtbase_git.bbappend:EXTRA_OECONF += "-qpa wayland-egl"10:59
ryoshuwhat to do if I need an external toolchain to build packages for my platform?11:00
ryoshuit consist of libc, gcc, binutils, gdb..11:01
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has quit IRC11:01
likewiseJaMa: are you testing on i.MX6 as well?11:01
likewiseryoshu: Look for bitbake meta-toolchain and variants11:02
ryoshulikewise: thanks!11:05
likewiseJaMa: ok, thanks. I will build master first, see where that gets me, then also build against the 5.4.x update.11:07
*** belen1 <belen1!~Adium@> has quit IRC11:19
*** pohly <pohly!> has joined #yocto11:23
Crofton|workryoshu, also look at bitbake -c populate_sdk image-name11:27
Crofton|workhmm, but qt stuff has dedicated toolchain recipes also11:27
ryoshuthank you, my task is to add new armv8 bsp and put it onto the website, I need your assistance11:28
ryoshutoday are holidays but I will go to my work and check your tips :)11:28
likewiseryoshu: nice, what metal are you targeting?11:32
ryoshuCavium ThunderX11:32
ryoshuI have my 3.10 kernel, my toolchain11:34
*** niteshnarayanlal <niteshnarayanlal!~niteshnar@fedora/niteshnarayanlal> has quit IRC11:43
*** nighty^ <nighty^!> has joined #yocto11:43
*** belen <belen!~Adium@> has joined #yocto11:59
*** belen1 <belen1!Adium@nat/intel/x-wxmqjthrtdkrsfqr> has joined #yocto12:02
*** pohly <pohly!> has quit IRC12:03
*** belen <belen!~Adium@> has quit IRC12:03
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto12:05
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC12:05
skfaxI'm trying to use a .bbappend file to add a .cfg file to FILESEXTRAPATHS. Using "bitbake-layers show-appends" I can see that my .bbappends file is found. However I'm not getting the end result I want. How can I know if the .cfg file is taken into account when building?12:06
skfaxAlso; are .cfg files reserved for kernel configuration in yocto?12:07
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC12:17
*** challinan <challinan!> has quit IRC12:20
*** challinan <challinan!> has joined #yocto12:21
*** niteshnarayanlal <niteshnarayanlal!~niteshnar@fedora/niteshnarayanlal> has joined #yocto12:27
*** grma <grma!> has quit IRC12:30
*** niteshnarayanlal <niteshnarayanlal!~niteshnar@fedora/niteshnarayanlal> has quit IRC12:32
*** belen <belen!~Adium@> has joined #yocto12:42
*** vmeson <vmeson!~rmacleod@> has joined #yocto12:44
*** belen1 <belen1!Adium@nat/intel/x-wxmqjthrtdkrsfqr> has quit IRC12:44
*** lamego <lamego!~lamego@> has joined #yocto12:46
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto12:47
*** bluelightning_ is now known as bluelightning12:52
*** abbu <abbu!6e5dd462@gateway/web/freenode/ip.> has left #yocto12:54
*** grma <grma!> has joined #yocto12:54
bluelightningskfax: .cfg files are interpreted as config fragments in the context of kernel recipes that use, yes12:55
bluelightningskfax: if the kernel recipe doesn't "require recipes-kernel/linux/" (or perhaps indirectly via inherit kernel-yocto) then I'm fairly sure .cfg files won't be acted upon12:57
*** belen <belen!~Adium@> has quit IRC12:59
skfaxbluelightning: when i use "bitbake -s" both linux-netmodule-zx3, linux-xlnx and linux-yocto are listed. I'm not really understanding how they are connected12:59
skfaxbluelightning: But I've been appending to the linux-xlnx recipe: maybe I need to try to append to linux-yocto instead13:00
bluelightningskfax: in almost all instances, the one that will actually be used to provide the system kernel will be the one selected as PREFERRED_PROVIDER_virtual/kernel13:00
*** belen <belen!~Adium@> has joined #yocto13:01
bluelightningit is not unusual to have multiple available kernel recipes in the metadata, but only one should actually end up being built for a given machine13:01
joseppcbluelightning: In what cases it won't be PREFERRED_PROVIDER_virtual/kernel?13:02
skfaxbluelightning: When I use "bitbake -e <target>" I can find: PREFERRED_PROVIDER_virtual/kernel="linux-xlnx"13:02
bluelightningjoseppc: well, our metadata is flexible, if you removed references to virtual/kernel everywhere then it wouldn't be used...13:04
bluelightningskfax: right, so linux-xlnx would be the kernel recipe being used in your current configuration13:04
skfaxbluelightning: I'm not sure if linux-xlnx is based on linux-yocto though. So if using linux-yocto is needed to use configuration fragments then that might explain why it is not working13:05
*** dfaught <dfaught!> has joined #yocto13:05
bluelightningskfax: it doesn't have to be the actual linux-yocto recipe, it just has to make use of linux-yocto.inc13:05
skfaxI'm looking at now, and it has "inherit kernel", "require" and "require". No direct mention of ""13:06
skfax(the file only includes the file + adds some version info)13:07
skfaxI guess I can go for a "defconfig" approach instead and just keep the entire configuration in one file in my layer13:08
joseppcbluelightning: ok, I asked because a friend recently had a problem where _virtual/kernel did not work, but using _yocto-kernel did. I never quire understood what was caused that13:09
*** locutus_ <locutus_!> has joined #yocto13:09
bluelightningjoseppc: I'd probably need more contextual information to give a proper answer; it could simply be that the desired setting of PREFERRED_PROVIDER_virtual/kernel was being overridden13:11
bluelightningskfax: right, the other option would be to add the require of linux-yocto.inc13:11
bluelightningyou can do that from your bbappend FYI13:12
*** LocutusOfBorg1 <LocutusOfBorg1!> has quit IRC13:12
skfaxbluelightning: And that will likely not break something?13:14
bluelightningit should be OK as long as the kernel recipe and the other inc files aren't doing anything that would conflict with it13:15
skfaxok cool will try it13:15
joseppcbluelightning: yeah, I did not have the time to investigate it further either. He set PREFERRED_PROVIDER_virtual/kernel in his local.conf, iirc13:17
*** locutus_ <locutus_!> has quit IRC13:17
*** LocutusOfBorg1 <LocutusOfBorg1!> has joined #yocto13:17
bluelightningjoseppc: right, then it's possible that PREFERRED_PROVIDER_virtual/kernel was being set to some other value either later on (e.g in a machine or distro config file) or with an override, the result being that the local.conf value wasn't taking effect13:19
bluelightningjoseppc: FYI you can always see when that kind of thing is happening by looking at the output of bitbake -e - you get a full history of how each variable has been set13:19
*** vmrod25 <vmrod25!vmrod25@nat/intel/x-myfndoftkraadtkw> has joined #yocto13:20
joseppcbluelightning: I rechecked, I did not remember it correctly. It seems the problem was with PREFERRED_VERSION_virtual/kernel. The provider and version looked correct with bitbake -e.13:24
joseppcbluelightning: Anyway, I think it must have been a configuration problem from his part13:24
*** microMolvi <microMolvi!~mentor@> has joined #yocto13:25
*** Aethenelle <Aethenelle!~Aethenell@> has joined #yocto13:25
*** belen <belen!~Adium@> has quit IRC13:27
*** belen <belen!Adium@nat/intel/x-hedtemsqstdxcjoz> has joined #yocto13:27
bluelightningjoseppc: well, let's deal with it when it next comes up :)13:27
skfaxbluelightning: When I do "bitbake -s <target>" I find "linux-xlnx" listed. When I do "bitbake-layers show-appends" I find that both "" and "" is being appended to. However I cannot seem to find any of the assignments done in these bbappend files when using "bitbake -e <target>". Is the full history shown with -e ?13:29
*** tsramos <tsramos!~tsramos@> has joined #yocto13:29
*** microMolvi <microMolvi!~mentor@> has quit IRC13:30
*** challinan <challinan!> has quit IRC13:33
*** glfernando <glfernando!~glfernand@> has quit IRC13:38
*** Noor <Noor!~quassel@> has joined #yocto13:42
*** microMolvi <microMolvi!~mentor@> has joined #yocto13:55
*** lamego <lamego!~lamego@> has quit IRC13:56
*** AndersD <AndersD!> has quit IRC13:58
*** lamego <lamego!lamego@nat/intel/x-unoecxilmucrrdxg> has joined #yocto13:58
*** jku <jku!jku@nat/intel/x-pczeddqpbecsogtp> has quit IRC14:00
*** vmrod25 <vmrod25!vmrod25@nat/intel/x-myfndoftkraadtkw> has quit IRC14:01
*** Aethenelle <Aethenelle!~Aethenell@> has quit IRC14:01
*** challinan <challinan!> has joined #yocto14:02
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto14:04
*** madisox <madisox!> has joined #yocto14:06
*** microMolvi <microMolvi!~mentor@> has quit IRC14:07
*** belen <belen!Adium@nat/intel/x-hedtemsqstdxcjoz> has quit IRC14:09
*** glfernando <glfernando!~glfernand@> has joined #yocto14:09
*** araldit <araldit!> has left #yocto14:16
*** manuel__ <manuel__!> has joined #yocto14:20
*** manuel_ <manuel_!> has quit IRC14:21
*** manuel__ is now known as manuel_14:21
*** diego_ <diego_!> has joined #yocto14:27
*** diego_r <diego_r!> has quit IRC14:27
*** diego_ is now known as diego_r14:28
*** diego_ <diego_!~diego@> has joined #yocto14:28
*** diego_r <diego_r!> has quit IRC14:28
*** diego_ is now known as diego_r14:28
*** diego_ <diego_!> has joined #yocto14:29
*** diego_r <diego_r!~diego@> has quit IRC14:29
*** diego_ is now known as diego_r14:29
*** kanupatar <kanupatar!79f4c042@gateway/web/freenode/ip.> has joined #yocto14:33
kanupatarI need to build u-boot and kernel for beagle board..version C3. May I know any yocto env porting guide?14:33
kanupataralso, I need to have QT 4.814:33
*** staylor <staylor!> has joined #yocto14:35
*** hamis <hamis!~irfan@> has quit IRC14:38
*** anselmolsm <anselmolsm!~anselmols@> has quit IRC14:48
rburtonkanupatar: there's a beagleboard BSP14:50
*** challinan <challinan!> has quit IRC14:50
kanupatarrburton: i need to build the bsp using yocto env14:50
kanupatarrburton: git:// -b daisy  ?14:50
rburtonthat's a basic BSP, meta-ti has a better one14:51
rburtonwell, different.14:51
kanupatarbeaglebone-daisy-11.0.0.tar.bz2 ?14:51
kanupatarI have bb C314:51
mckoankanupatar: and probably branch 'dizzy' would be better option14:51
kanupatargit:// -b dizzy?14:52
kanupatarmckoan: ?14:52
mckoankanupatar: yes14:53
kanupatarmckoan: rburton then how can I start building it? any build procedures?14:53
kanupatarI have beagle board C314:54
kanupatarAlso, I need QT 4.814:54
mckoankanupatar: this may be a good starting point
kanupatarmckoan: not english?14:55
*** challinan <challinan!> has joined #yocto14:56
mckoankanupatar: the important parts are the commands :-D14:56
kanupatarmckoan: okay.. what are all commands I need to follow for baegle?14:56
kanupatarmckoan: it is generic isn't it14:56
ryoshuI want to upload my 3.10 kernel to your repositories14:57
kanupatarmckoan: sorry, yes it is beagle board specific14:57
ryoshuand have there a branch for my hardware14:57
ryoshuwhat's the proper procedure14:58
*** anselmolsm <anselmolsm!~anselmols@> has joined #yocto14:58
kanupatarmckoan: thanks...shoudld it include QT package also?14:58
kanupatarI need to build QT 4.8 for beagle c314:59
mckoankanupatar: no, but start with a minimal image14:59
*** sjolley <sjolley!~sjolley@> has quit IRC14:59
kanupatarmckoan: OK ok14:59
kanupatarmckoan: so for QT, just add it in script?14:59
bluelightningryoshu: the typical way to do this is to create a BSP layer for your hardware and push that as a git repository somewhere14:59
*** microMolvi <microMolvi!~mentor@> has joined #yocto15:00
ryoshubluelightning: aha15:00
ryoshuand ask for merge?15:00
mckoankanupatar: Qt4.8 should be traightforward: bitbake qt4e-demo-image15:01
kanupatarmckoan: thanks15:01
kanupatarits okay15:01
kanupatarcan I open hob and build?15:01
bluelightningryoshu: for additional machines, the idea is that you (or at least someone with interest in support for the machine) maintains the BSP layer rather than it being part of a central repository of support for multiple machines15:02
mckoankanupatar: gosh! I don't like HOB, use command line15:02
*** challinan <challinan!> has quit IRC15:03
kanupatarmckoan: okay okay.15:03
kanupatarmckoan: I need to learn git thoroughly, means it is building flow, customisation for different build etc15:04
kanupatarsorry, yocto15:04
kanupatarbitbake qt4e-demo-image --> what is the exact meaning  ? mckoan ?15:04
kanupataralso, I would like to have wayland15:05
*** challinan <challinan!> has joined #yocto15:05
kanupatarqt4e-demo-image --> is the qt lib build or for entire kernel build?15:05
mckoankanupatar: Qt4 don't support wayland15:06
mckoankanupatar: I'd suggest you to study a bit how Yocto works15:06
kanupatarmckoan: yes yes15:06
kanupatarmckoan: from scratch15:06
kanupatarmckoan:so I can learn from the beagle board exercise15:07
kanupatarmckoan: then QT5 wayland build?15:07
kanupatarmckoan: thanks, I will go through the link completely15:08
* kanupatar interested to become a contributor for ycoto project..can start as a tester15:08
* kanupatar would like to become an intern under mckoan :)15:08
ryoshubluelightning: I see15:09
ryoshubluelightning: thanks15:09
bluelightningryoshu: it may be worth noting, once you have created your layer, we can provide hosting for it on in its own repository, or alternatively you can set up a repo on github or similar15:10
bluelightningryoshu: once it's publicly available it can be added to the openembedded layer index at http://layers.openembedded.org15:10
bluelightningwhich will make it easy for others to find15:11
ryoshuI will try to see how is done for Cavium Octeon15:11
ryoshubluelightning: I will resume it today and be at IRC, today are holidays in .pl :)15:12
ryoshuI mean resume it tomorrow! :)15:12
bluelightningryoshu: ok, enjoy your holiday :)15:12
*** vmrod25 <vmrod25!~vmrod25@> has joined #yocto15:13
*** DanielAdolfsson <DanielAdolfsson!> has quit IRC15:13
*** berton <berton!> has joined #yocto15:13
*** ant_work <ant_work!> has quit IRC15:13
*** challinan <challinan!> has quit IRC15:14
*** microMolvi <microMolvi!~mentor@> has quit IRC15:16
*** challinan <challinan!> has joined #yocto15:18
*** challinan <challinan!> has quit IRC15:21
kanupatarmckoan: how can I build QT 5.3. with wayland for bb C3?15:24
*** tsramos <tsramos!~tsramos@> has quit IRC15:25
*** lamego <lamego!lamego@nat/intel/x-unoecxilmucrrdxg> has quit IRC15:31
*** sjolley <sjolley!sjolley@nat/intel/x-hylzacgvqqlmtsnf> has joined #yocto15:33
*** dvhart_ <dvhart_!~dvhart@> has quit IRC15:35
*** sameo <sameo!~samuel@> has quit IRC15:43
*** lamego <lamego!~lamego@> has joined #yocto15:48
-YoctoAutoBuilder- build #321 of build-appliance is complete: Success [build successful] Build details are at
*** dvhart_ <dvhart_!dvhart@nat/intel/x-qmtzcugfxqazhhjc> has joined #yocto16:02
*** mckoan is now known as mckoan|away16:04
*** nerdboy <nerdboy!> has joined #yocto16:07
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto16:08
*** challinan <challinan!> has joined #yocto16:16
-YoctoAutoBuilder- build #325 of nightly-qa-systemd is complete: Success [build successful] Build details are at
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto16:19
*** rneri <rneri!ricardo@nat/intel/x-upvdvdeoazawnfxh> has joined #yocto16:20
*** jbrianceau is now known as jbrianceau_away16:24
*** sarahsharp <sarahsharp!sarah@nat/intel/x-fcjonszubpzotgft> has joined #yocto16:30
*** dvhart_ <dvhart_!dvhart@nat/intel/x-qmtzcugfxqazhhjc> has quit IRC16:38
*** dvhart_ <dvhart_!dvhart@nat/intel/x-zlqhmvsegzekfuur> has joined #yocto16:38
*** T0mW <T0mW!> has quit IRC16:39
*** tomz <tomz!trz@nat/intel/x-mwomvspsunlbrwyu> has left #yocto16:42
*** egavin <egavin!> has quit IRC16:43
*** lamego <lamego!~lamego@> has quit IRC16:50
*** roric <roric!~roric@> has quit IRC16:54
*** lamego <lamego!lamego@nat/intel/x-fitmvlzjnvgrgwkm> has joined #yocto17:03
*** anselmolsm <anselmolsm!~anselmols@> has quit IRC17:06
*** vmrod25 <vmrod25!~vmrod25@> has quit IRC17:06
*** dvhart_ <dvhart_!dvhart@nat/intel/x-zlqhmvsegzekfuur> has quit IRC17:07
*** dvhart_ <dvhart_!~dvhart@> has joined #yocto17:08
*** diego_r <diego_r!> has quit IRC17:17
*** dvhart_ <dvhart_!~dvhart@> has quit IRC17:34
*** dvhart_ <dvhart_!dvhart@nat/intel/x-njoofufzabzggifl> has joined #yocto17:53
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC17:57
*** vmrod25 <vmrod25!~vmrod25@> has joined #yocto17:58
khem`is there some docs on how to use BUILD_IMAGES_FROM_FEEDS17:59
*** berton <berton!> has quit IRC18:13
*** JaMa <JaMa!> has quit IRC18:25
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has quit IRC18:29
*** adelcast <adelcast!~adelcast@> has left #yocto18:41
*** hitlin37 <hitlin37!uid16371@gateway/web/> has quit IRC18:42
*** adelcast <adelcast!~adelcast@> has joined #yocto18:42
*** ncgs <ncgs!> has quit IRC18:42
*** sarahsharp <sarahsharp!sarah@nat/intel/x-fcjonszubpzotgft> has quit IRC18:53
*** jwessel <jwessel!~jwessel@> has quit IRC18:55
*** raffo <raffo!> has quit IRC18:59
*** ncgs <ncgs!> has joined #yocto19:00
*** paulg_ <paulg_!~paulg@> has joined #yocto19:01
skfaxlayer-a/conf/machine/x.conf is being picked instead of layer-b/conf/machine/x.conf even when layer-b has a higher priority than layer-a19:12
skfaxif i remove x.conf from layer-a; x.conf from layer-b is found19:12
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has joined #yocto19:12
*** jwessel <jwessel!~jwessel@> has joined #yocto19:16
*** [Sno] <[Sno]!> has quit IRC19:23
*** _dv_ <_dv_!> has joined #yocto19:23
*** dv__ <dv__!> has quit IRC19:24
skfaxWhen a variable is being "set?" from two different configuration files; why is the configuration file from the layer with the lower priority chosen?19:30
*** sarahsharp <sarahsharp!~sarah@> has joined #yocto19:59
*** varibull <varibull!> has quit IRC20:03
*** varibull <varibull!> has joined #yocto20:04
*** varibull <varibull!> has quit IRC20:10
*** varibull <varibull!> has joined #yocto20:11
*** vmeson <vmeson!~rmacleod@> has quit IRC20:49
*** nighty^ <nighty^!> has quit IRC20:54
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto21:07
*** tmpsantos <tmpsantos!> has quit IRC21:11
*** vmeson <vmeson!> has joined #yocto21:14
*** sarahsharp <sarahsharp!~sarah@> has quit IRC21:18
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has quit IRC21:19
*** cazze <cazze!> has joined #yocto21:20
cazzelittle question, when i try to bitbake, i get some "Could not include ***-extraconf.inc21:20
cazzei don't see any difference with other recipes where the last line is require ***-extraconf.inc21:22
*** roric <roric!> has joined #yocto21:22
cazzewhat do i have to do to correct these errors?21:23
*** paulg_ <paulg_!~paulg@> has quit IRC21:24
*** rburton <rburton!> has quit IRC21:25
*** sarahsharp <sarahsharp!~sarah@> has joined #yocto21:25
*** skfax <skfax!> has quit IRC21:32
*** sameo <sameo!~samuel@> has joined #yocto21:37
*** jimBaxter <jimBaxter!> has quit IRC21:39
cazzecan't they be ignored or created at bake time?21:44
bluelightningcazze: I'm not sure what you're asking, but if you use "require ..." , the file must exist21:53
*** Jay7 <Jay7!> has joined #yocto21:59
*** dvhart_ <dvhart_!dvhart@nat/intel/x-njoofufzabzggifl> has quit IRC22:00
*** bfederau <bfederau!> has quit IRC22:01
*** dvhart_ <dvhart_!dvhart@nat/intel/x-kevhmpswgfrprcxg> has joined #yocto22:01
*** bfederau <bfederau!> has joined #yocto22:01
*** dfaught <dfaught!> has quit IRC22:04
*** sarahsharp <sarahsharp!~sarah@> has quit IRC22:04
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC22:23
*** dlan <dlan!~dennis@> has joined #yocto22:24
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto22:24
*** grma_ <grma_!> has joined #yocto22:24
*** grma <grma!> has quit IRC22:26
*** sarahsharp <sarahsharp!~sarah@> has joined #yocto22:27
*** moto-timo <moto-timo!~timo@fsf/member/moto-timo> has quit IRC22:28
*** moto-timo <moto-timo!~timo@> has joined #yocto22:28
*** moto-timo is now known as Guest7610322:29
cazzebluelightning: ok, i did a touch and it was ok. File was not in the git tree :-(22:30
*** Guest76103 <Guest76103!~timo@> has quit IRC22:30
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has joined #yocto22:31
*** dl9pf <dl9pf!~quassel@opensuse/member/dl9pf> has quit IRC22:31
*** dvhart_ <dvhart_!dvhart@nat/intel/x-kevhmpswgfrprcxg> has quit IRC22:32
*** dl9pf <dl9pf!> has joined #yocto22:33
*** dl9pf <dl9pf!~quassel@opensuse/member/dl9pf> has joined #yocto22:33
*** dvhart_ <dvhart_!dvhart@nat/intel/x-gjezwzuwbhtbqzuh> has joined #yocto22:33
*** seezer <seezer!quassel@quassel/developer/seezer> has quit IRC22:34
*** kido <kido!~kido@unaffiliated/kido> has quit IRC22:35
*** seezer <seezer!seezer@quassel/developer/seezer> has joined #yocto22:36
*** moto_timo <moto_timo!~timo@fsf/member/moto-timo> has joined #yocto22:36
*** eballetbo <eballetbo!> has quit IRC22:37
*** eballetbo <eballetbo!> has joined #yocto22:37
*** jfojtl <jfojtl!> has quit IRC22:41
*** jfojtl <jfojtl!> has joined #yocto22:42
staylorIs it possible to distribute the generated SDK using something like Debian packages instead of a single shell script installed?  Specifically I'd like a better way of distributing minor updates to a specific library in a cleaner way then shipping out a new .sh file or sending out replacement files.22:51
*** lamego <lamego!lamego@nat/intel/x-fitmvlzjnvgrgwkm> has quit IRC22:52
*** dvhart_ <dvhart_!dvhart@nat/intel/x-gjezwzuwbhtbqzuh> has quit IRC22:57
*** kido <kido!~kido@unaffiliated/kido> has joined #yocto23:03
*** sjolley <sjolley!sjolley@nat/intel/x-hylzacgvqqlmtsnf> has quit IRC23:07
*** staylor <staylor!> has quit IRC23:09
*** madisox <madisox!> has quit IRC23:14
*** roric <roric!> has quit IRC23:16
*** sameo <sameo!~samuel@> has quit IRC23:19
*** seebs <seebs!> has quit IRC23:30
*** seebs <seebs!> has joined #yocto23:32
*** sjolley <sjolley!sjolley@nat/intel/x-tdkodobwoaykmwnh> has joined #yocto23:49
*** sarahsharp <sarahsharp!~sarah@> has quit IRC23:49
*** grma_ <grma_!> has quit IRC23:57

Generated by 2.11.0 by Marius Gedminas - find it at!