Monday, 2014-06-30

*** _valle_ <_valle_!> has quit IRC00:10
*** _valle_ <_valle_!> has joined #yocto00:10
*** rburton <rburton!> has quit IRC00:11
*** rburton <rburton!> has joined #yocto00:12
*** rburton <rburton!> has quit IRC00:45
*** rburton <rburton!> has joined #yocto00:46
*** sameo <sameo!~samuel@> has quit IRC01:20
*** rburton <rburton!> has quit IRC02:05
*** rburton <rburton!> has joined #yocto02:05
*** nitink <nitink!nitink@nat/intel/x-qbzbfutcihkpfalk> has joined #yocto02:19
*** rburton <rburton!> has quit IRC02:39
*** rburton <rburton!> has joined #yocto02:44
*** wgao <wgao!~wgao@> has joined #yocto03:26
*** alexhairyman <alexhairyman!> has quit IRC04:11
*** [Sno] <[Sno]!~Sno]> has quit IRC04:33
*** e8johan <e8johan!> has joined #yocto04:35
*** msm` <msm`!> has joined #yocto04:58
*** AndersD <AndersD!> has joined #yocto05:10
*** tlwoerner <tlwoerner!~trevor@linaro/tlwoerner> has joined #yocto05:16
*** AndersD <AndersD!> has quit IRC05:16
*** AndersD <AndersD!> has joined #yocto05:17
*** darknighte_ <darknighte_!~darknight@pdpc/supporter/professional/darknighte> has quit IRC05:39
*** g1zer0 <g1zer0!> has joined #yocto05:56
*** ubik3000 <ubik3000!~cristiani@> has quit IRC06:00
*** agust <agust!> has joined #yocto06:05
*** darknighte_ <darknighte_!~darknight@pdpc/supporter/professional/darknighte> has joined #yocto06:06
*** likewise <likewise!~Leon@> has joined #yocto06:37
*** [Sno] <[Sno]!~Sno]> has joined #yocto06:43
*** mckoan|away <mckoan|away!> has quit IRC06:52
*** eballetbo <eballetbo!> has joined #yocto06:53
*** cristianiorga <cristianiorga!cristianio@nat/intel/x-mjrdhxqywowuotcp> has joined #yocto06:55
*** mckoan <mckoan!~marco@unaffiliated/mckoan> has joined #yocto06:58
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has joined #yocto06:59
*** jbrianceau_away is now known as jbrianceau06:59
*** tasslehoff <tasslehoff!~Tasslehof@> has joined #yocto07:02
*** TuTizz <TuTizz!~TuTizz@> has joined #yocto07:05
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has joined #yocto07:05
*** kroon <kroon!~kroon@> has joined #yocto07:06
*** sgw_ <sgw_!> has quit IRC07:10
mckoangood morning07:10
*** beaver_545 <beaver_545!~stuart@> has quit IRC07:15
*** elinuxer <elinuxer!~elinuxer@> has joined #yocto07:22
elinuxerHi yocto07:22
*** ant_work <ant_work!> has joined #yocto07:23
elinuxerI working in beaglebone black development board, For that i compiled  u-boot and kernel and filesystem using meta-ti layer with minimal image core-image-minimal. If i boot this image in my board it hangs on the starting kernel..please check the link and help me to solve this issue.      
*** shoragan <shoragan!~shoragan@debian/developer/shoragan> has joined #yocto07:29
*** sgw_ <sgw_!> has joined #yocto07:33
*** sameo <sameo!samuel@nat/intel/x-ruompgsyedlvxgae> has joined #yocto07:45
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:46
*** florian_kc is now known as florian07:47
elinuxerHi please any one help me to resolve this problem.. Please07:53
*** bluelightning <bluelightning!> has joined #yocto07:56
*** bluelightning <bluelightning!> has quit IRC07:56
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto07:56
[Sno]elinuxer: smells as if youre loadaddr is wrong08:33
*** belen <belen!Adium@nat/intel/x-fqhfzqdapvwujobr> has joined #yocto08:40
*** eballetbo_ <eballetbo_!> has joined #yocto08:40
*** eballetbo <eballetbo!> has quit IRC08:42
*** JimBaxter <JimBaxter!> has joined #yocto08:44
elinuxerThis kernel load address is 80008000. Is it need to update anywhere.08:46
*** eballetbo_ <eballetbo_!> has quit IRC08:48
*** eballetbo <eballetbo!> has joined #yocto08:48
*** belen1 <belen1!Adium@nat/intel/x-mhsjhzcyzubtosoi> has joined #yocto08:59
*** belen <belen!Adium@nat/intel/x-fqhfzqdapvwujobr> has quit IRC09:00
AndersDelinuxer, how does your uEnv.txt look like? There seems to be an issue with the U-Boot environment.09:01
AndersDelinuxer, Look at the line "Unknown command 'console=ttyO0,115200n8' - try 'help'09:01
AndersDelinuxer, in our pastebin.09:02
AndersDconsole=... should have been appended to bootargs in u-boot, not evaluated.09:02
elinuxerAndersD: please check my uEnv.txt file
AndersDelinuxer, the line "loadkernel=run bootargs;mmc rescan; fatload mmc 0 0x80200000 uImage-beaglebone.bin" is wrong09:05
AndersDYou shouldn't have the "run bootargs" part in it09:05
elinuxerAndersD:please tell me how to modify this..09:06
AndersDAs you're not evaluating variables in your bootargs line, just remove that part from loadkernel.09:06
AndersDYou could also quite likely remove the loadaddr statement from uEnv.txt.09:08
AndersDOr skip the last part about loadaddr, I didn't look close enough on your uEnv.txt.09:09
elinuxerAndersD:Shall i write like this
AndersDAlmost, make it "loadkernel=mmc rescan; fatload mmc 0 0x80200000 uImage-beaglebone.bin"09:10
AndersDThough, you should change 0x80200000 to ${loadaddr}, to be more consistent with how you're starting the kernel.09:11
*** rburton <rburton!> has quit IRC09:13
elinuxerAndersD:thank you so much now it's booting.09:14
*** rburton <rburton!> has joined #yocto09:14
*** rburton <rburton!> has left #yocto09:15
AndersDelinuxer, Good!09:19
AndersDThe issue was the likely that the kernel didn't get your console=... arguments (though I would have thought it would get it anyway). Thus, the kernel didn't know where to put it's logging.09:20
*** awafaa_ is now known as awafaa09:22
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC09:25
*** bluelightning <bluelightning!> has joined #yocto09:26
*** bluelightning <bluelightning!> has quit IRC09:26
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto09:26
*** ndec_ is now known as ndec09:28
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC09:31
*** mulhern <mulhern!~mulhern@> has joined #yocto09:31
*** bluelightning <bluelightning!> has joined #yocto09:31
*** bluelightning <bluelightning!> has quit IRC09:31
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto09:31
*** mulhern <mulhern!~mulhern@> has quit IRC09:32
*** elinuxer <elinuxer!~elinuxer@> has quit IRC09:41
*** elinuxer <elinuxer!~elinuxer@> has joined #yocto09:48
*** msm <msm!> has joined #yocto10:01
*** msm` <msm`!> has quit IRC10:04
*** ant_work <ant_work!> has quit IRC10:14
*** Xz_ is now known as Xz10:16
*** seezer <seezer!quassel@quassel/developer/seezer> has quit IRC10:25
*** seezer <seezer!quassel@quassel/developer/seezer> has joined #yocto10:25
elinuxerAndersD: I HAVE ANOTHER PROBLEM. I want to compile meta-beagleboard layer with my poky distro if i try to add this layer with poky disto its showing error mentioned in patedbin
elinuxerwhat is problem.10:37
*** melonipoika <melonipoika!> has joined #yocto10:46
AndersDelinuxer, which version of poky are you using, and which versin of meta-beagleboard?10:50
AndersDelinuxer, you have a spelling error in bblayers.conf. It should be common-bsp...10:52
*** jkridner <jkridner!> has joined #yocto10:56
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto10:56
*** elinuxer <elinuxer!~elinuxer@> has quit IRC10:57
*** elinuxer <elinuxer!~elinuxer@> has joined #yocto10:57
elinuxerAndersD: i have followed the  web mentioned link
elinuxeri cant see the version..10:58
elinuxerAll are from dylan branch..10:59
AndersDelinuxer, like I said, you have a typo in bblayers.conf11:04
AndersDThe branch info (i.e. dylan) is good enough for hte moment regarding the versions. Though, I think it should work once you fix the typo.11:05
elinuxersorry..I am not understanding  about typo.11:06
AndersDOk, have line "  /home/tamilarasi/beagle/poky/meta-beagleboard/comman-bsp \" in your bblayers.conf., comman-bsp should be common-bsp11:07
*** mckoan is now known as mckoan|away11:11
*** jluisn <jluisn!~quassel@> has joined #yocto11:17
*** padge_ <padge_!> has joined #yocto11:19
*** padge_ <padge_!> has left #yocto11:20
elinuxerAndersD: oh. It's my error. Now it's working..11:23
*** adelcast <adelcast!~adelcast@> has joined #yocto11:30
*** bfederau <bfederau!> has joined #yocto11:33
*** d_s_e <d_s_e!> has joined #yocto11:44
*** Guest7691 is now known as jero-11:50
*** Rick___ <Rick___!5a509091@gateway/web/freenode/ip.> has joined #yocto11:56
*** jluisn <jluisn!~quassel@> has quit IRC11:58
Rick___hi while do_install i get ERROR: cannot stat bb-example, no such file or directory, i guess something is missing, how can i get more infos about what is missing?11:59
*** jluisn <jluisn!~quassel@> has joined #yocto12:00
*** elinuxer <elinuxer!~elinuxer@> has quit IRC12:11
*** challinan <challinan!> has joined #yocto12:12
*** elinuxer <elinuxer!~elinuxer@> has joined #yocto12:12
*** fray <fray!> has quit IRC12:23
*** fray <fray!> has joined #yocto12:24
*** proximus1 <proximus1!> has joined #yocto12:28
*** proximus <proximus!> has quit IRC12:31
*** adelcast <adelcast!~adelcast@> has quit IRC12:35
*** elinuxer <elinuxer!~elinuxer@> has quit IRC12:38
*** elinuxer <elinuxer!~elinuxer@> has joined #yocto12:41
*** phragment <phragment!> has quit IRC12:46
*** fray <fray!> has quit IRC12:54
*** fray <fray!> has joined #yocto12:56
*** phragment <phragment!> has joined #yocto12:56
TuTizzHi all, I am not sure but I think PACKAGECONFIG = ${@base_contains('DISTRO_FEATURES','systemd','systemd','consolekit',d)}" is not working if systemd is put in DISTRO_FEATURES_append = " systemd" and not directly in DISTRO_FEATURES ?= "systemd". Could you confirm that please?12:59
*** kscherer <kscherer!~kscherer@> has joined #yocto13:08
*** rajesh_ <rajesh_!> has joined #yocto13:10
*** dmoseley <dmoseley!> has joined #yocto13:14
*** elinuxer <elinuxer!~elinuxer@> has quit IRC13:15
*** elinuxer <elinuxer!~elinuxer@> has joined #yocto13:17
bluelightningTuTizz: that should not be the case, no13:26
[Sno]in which order yocto finds receipes?13:33
*** elinuxer <elinuxer!~elinuxer@> has quit IRC13:34
[Sno]given a bblayers.conf where sources/meta-openembedded/meta-oe is before sources/meta-stef - and both have a libcec-git - which one is choosen?13:35
likewiseIf a have a "some-recipe_%.bbappend", what is the recommended way of extending FILESEXTRAPATHS?13:37
bluelightning[Sno]: generally, it depends upon the layer priority (higher is picked first); then if they are the same, which version is higher13:38
bluelightninglikewise: as always, FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"13:38
[Sno]bluelightning: that's enlightening - all layers (meta-oe, meta-stef, mete-me) were at 613:43
likewisebluelightning: When is "files" used instead of ${PN} ?13:44
*** wv <wv!> has joined #yocto13:45
[Sno]so a BUILDDIR/conf/bblayers.conf should probably tweak it per project ...13:45
bluelightninglikewise: it's up to your preference - it just has to match up with where you actually place the files you're adding / overriding13:46
*** mkeeter <mkeeter!~mkeeter@> has joined #yocto13:46
bluelightninglikewise: (for the bbappend that is)13:46
wvHello, I'm having troubles building yocto for my baytrail platform13:47
likewisebluelightning: thanks13:47
wvI'm using the latest from git dora, as wel as from meta-intel13:47
wvIf I do a bitbake of core-image-sato, it fails on bzip2-native13:48
wvlog on
wvcan somebody tell me what's wrong?13:48
*** jwessel <jwessel!~jwessel@> has joined #yocto13:57
*** e8johan <e8johan!> has quit IRC13:58
*** proximus1 <proximus1!> has quit IRC13:59
*** AndersD <AndersD!> has quit IRC14:00
*** proximus <proximus!> has joined #yocto14:05
*** sjolley <sjolley!~sjolley@> has quit IRC14:11
*** melonipoika <melonipoika!> has quit IRC14:18
*** melonipoika <melonipoika!> has joined #yocto14:19
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC14:21
*** adelcast <adelcast!~adelcast@> has joined #yocto14:24
*** mago_ <mago_!> has quit IRC14:28
*** tasslehoff <tasslehoff!~Tasslehof@> has quit IRC14:29
*** petero <petero!> has joined #yocto14:33
peterohello everybody14:33
peteroi have a bbappend file14:33
*** madisox <madisox!~madisox@nat/cisco/x-zdwtcshwnhrykhwu> has quit IRC14:34
peterois there a way to extend a let's say do_compile task that is already defined in the original .b bfile?14:34
*** tomz_ <tomz_!~tomz@> has quit IRC14:35
peteromy bbappend's do_compile overwrites my do_compile defined in the .bb14:35
peteroi'd like to have both executed14:35
*** stuartw_ <stuartw_!~stuartw@> has joined #yocto14:44
*** sjolley <sjolley!sjolley@nat/intel/x-iurjamepsxpnshfu> has joined #yocto14:44
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC14:46
*** tyler-baker <tyler-baker!~tyler@linaro/tyler-baker> has joined #yocto14:47
stuartw_Hi All, I'm currently having trouble with getting my current hardware (meta-valleyisland) on the network, whenever I boot the board up or try ifup/dhclient/udhcpc eth0 I'm getting no offers from the network. I would believe this would be network side apart from booting the board into windows connects fine to the network. Does anyone have any ideas on how to solve this?14:47
wvstuartw, and you do have a eth0?14:48
stuartw_yes, the driver wasn't originally enabled in the kernel so after a menuconfig it appeared, could I have missed an option out somewhere?14:49
wvstuartw_ that was what I was going to ask, if you enabled the kernel driver :)14:52
wvI'm out of options then (besides a network problem)14:52
wvdid you try to enable the network manually?14:52
wv(ifconfig eth0 etc)?14:53
stuartw_well, the eth0 driver is i210 which seems to link to the IGB drivers in Yocto, the following is what i enabled through menuconfig:14:54
stuartw_and those were all i could find relating to the IGB14:55
wvhm, no further ID, sorry14:55
stuartw_yes, i tried setting manually, but still wouldn't connect (i.e. ping from target and to target)14:55
stuartw_well thanks anyway, at least I know I haven't missed something silly!14:56
peteroalright, found it14:56
*** petero <petero!> has quit IRC14:56
wvand you're sure there is a good cable in between? and they're plugged in correctly?14:56
wvBlinking led on your pc side, also enabled there?14:56
wv(these are the silly things ;))14:56
wvbut verry common :-D14:57
stuartw_I'll say yes as when booting windows on the board it connects perfectly (unfortunately)14:57
*** kroon <kroon!~kroon@> has quit IRC14:58
*** armpit <armpit!> has joined #yocto14:59
stuartw_I missed out that infact, whenever I boot windows first then reboot into linux, the board is configured and able to connect to the network???14:59
stuartw_so it sounds to me more like a driver issue?14:59
*** g1zer0 <g1zer0!> has quit IRC15:00
*** mkeeter <mkeeter!~mkeeter@> has quit IRC15:01
*** [Sno] <[Sno]!~Sno]> has quit IRC15:01
*** mkeeter <mkeeter!> has joined #yocto15:01
*** mkeeter <mkeeter!> has quit IRC15:03
*** mkeeter <mkeeter!~mkeeter@> has joined #yocto15:03
likewisestuartw_: avb?15:04
stuartw_what does avb stand for? sorry for the lack of knowledge :P15:05
likewisestuartw_: just wondering if you were playing with Audio Video Bridging (i210 seems nice for that)15:08
*** Gintaro <Gintaro!> has quit IRC15:08
stuartw_not that i currently know of, it's just what was on the board that i was given15:09
*** Gintaro <Gintaro!> has joined #yocto15:10
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has quit IRC15:12
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has joined #yocto15:14
likewiseRephrasing: If we have a some-recipe_%.bbappend, and package-version specific patches, FILESEXTRAPATHS_prepend := "${THISDIR}/${PV}"   will have the ${PV} part set to "%" in the search path. How to get back the desured behaviour where ${PV} was taken from the package-version .bb file?15:27
*** kroon <kroon!> has joined #yocto15:32
*** mkeeter <mkeeter!~mkeeter@> has quit IRC15:39
*** mkeeter <mkeeter!~mkeeter@> has joined #yocto15:39
*** jwessel <jwessel!~jwessel@> has left #yocto15:39
kergothlikewise: i expect you could force thisdir to be immediately expanded, but let PV be expanded later as it should be, when it has the correct value. e.g. THISDIR := "${THISDIR}"; FILESEXTRAPATHS_prepend = "${THISDIR}/${BP}:" or somesuch, but thats obviously untested15:42
*** munch <munch!> has joined #yocto15:45
*** likewise <likewise!~Leon@> has quit IRC15:46
*** eballetbo <eballetbo!> has quit IRC15:52
*** radzy_away is now known as radzy15:53
*** mebrown <mebrown!> has quit IRC15:54
*** mebrown <mebrown!> has joined #yocto15:55
*** mkeeter <mkeeter!~mkeeter@> has quit IRC15:56
*** mkeeter <mkeeter!> has joined #yocto15:56
*** radzy <radzy!~radzy@> has quit IRC15:58
*** radzy <radzy!~radzy@> has joined #yocto16:02
*** radzy is now known as radzy_away16:03
*** radzy_away is now known as radzy16:03
*** T0mW <T0mW!> has joined #yocto16:14
*** jbrianceau is now known as jbrianceau_away16:16
*** mario-goulart <mario-goulart!> has quit IRC16:27
*** mario-goulart <mario-goulart!> has joined #yocto16:28
*** msm <msm!> has left #yocto16:32
*** rajesh_ <rajesh_!> has quit IRC16:36
*** mkeeter <mkeeter!> has quit IRC16:41
*** mkeeter <mkeeter!~mkeeter@> has joined #yocto16:42
*** challinan <challinan!> has quit IRC16:44
*** seebs <seebs!> has quit IRC16:44
*** manuel_ <manuel_!~manuel_@> has joined #yocto16:46
*** seebs <seebs!> has joined #yocto16:47
*** kroon <kroon!> has quit IRC16:52
*** AlexG <AlexG!c0c6972c@gateway/web/freenode/ip.> has joined #yocto16:56
*** maxtothemax <maxtothemax!~maxtothem@> has joined #yocto17:01
*** belen1 <belen1!Adium@nat/intel/x-mhsjhzcyzubtosoi> has quit IRC17:02
*** AlexG <AlexG!c0c6972c@gateway/web/freenode/ip.> has quit IRC17:04
*** pidge <pidge!~pidge@> has joined #yocto17:06
*** challinan <challinan!> has joined #yocto17:07
*** sameo <sameo!samuel@nat/intel/x-ruompgsyedlvxgae> has quit IRC17:09
*** mkeeter <mkeeter!~mkeeter@> has quit IRC17:12
*** mkeeter <mkeeter!> has joined #yocto17:13
*** LynnCyrin <LynnCyrin!~LCyrin@2607:fb90:40d:9c4d:9725:8054:fd46:ff20> has joined #yocto17:30
maxtothemaxquestion about the finer points of PREFERRED_PROVIDER17:49
volker-I have a recipe that I want to reuse for a lot of cases. The differences I want to do is changing two variables: a path and a projectname.17:49
volker-how do I do this the best? Creating a .inc file which I use via "require" and then only changing the two variables?17:49
maxtothemaxI hate to blurt out my question at the same time as volker's but I shall continue typing mine anyway17:50
volker-all in one folder with multiple .bb files or is there a way to do this across folders17:50
maxtothemaxsuppose recipes A and B both PROVIDE "X" and B is the PREFERRED_PROVIDER17:51
maxtothemax but A is depended upon directly by another recipe that's included in the build, so it will always be built anyway17:51
maxtothemaxdoes that mean B doesn't get built?17:51
maxtothemaxor could you end up with A and B both being built?17:52
kergothmost likely both will get sucked in, and bitbake will display an error about it17:52
maxtothemaxhow would I achieve that behavior then?17:52
kergothyou'd set preferred provider to A, or fix the the recipe that depends on it explicitly17:53
kergothno, conflicts would do nothing, bitbake knows two providers of a thing shouldnt' be built, but you ahven't told it what to do to address the situation17:53
maxtothemaxwhat I want is for package A to not be built if package B is built, and vice versa17:54
maxtothemaxif PROVIDES is not going to do that, is there another mechanism?17:54
*** [Sno] <[Sno]!~Sno]> has joined #yocto17:56
maxtothemaxI mean, the caveman way would be to have people manually put one or the other in IMAGE_INSTALL but I was hoping for something better17:58
kergoththat's never going to happen18:01
kergothbecause that would make your builds completely nondeterministic18:01
volker-kergoth: any opinions about reusable recipes that only differ in two variables?18:02
kergothuse a .inc, seems trivial enough to me18:02
volker-kergoth: yes, are there alternative ways?18:03
kergothis there a problem with using a .inc? I don't see the problem18:03
volker-.bbappend would be nice, but from my understanding it won't work in the same layer18:03
kergothyou could use a class, but that seems pointless for two recipes18:03
kergothbbappend wouldnt' make any sense18:03
kergothbbapepnd modifies an existing recipe, it doesn't create two recipes18:03
volker-kergoth: ok. I was looking for different ways where the folder would be called foo-project and not foo to make it more obvious. while foo-project uses the files from another recipe folder18:05
*** dimi1 <dimi1!~dimi@> has joined #yocto18:05
volker-just brainstorming about different options. I hear already the "that package does not have its own foldername"18:06
*** vroomfondel <vroomfondel!> has joined #yocto18:06
maxtothemaxis it possible to construct a recipe that will install extra files if something is *not* in IMAGE_FEATURES?18:07
maxtothemaxthat would also do what I want18:07
kergoththat wouldn't make sense either, image features can only affect images. if you modify how ar ecipe builds for it, then it'd be impossible to use the binary package that recipe prdouces in two different images which use two different IMAGE_FEATURES18:08
kergothyou can't modify how things are built based on what image you happen to be building at this exact moment, considering you could 'bitbake oneimage twoimage threeimage forty-two-other-images'18:08
volker-kergoth: but isnt readonly image option such a case where it is sometimes inside of the recipe?18:10
kergothany recipe doing something based on a read only image feature is a broken recipe18:10
dimi1why not splitting the extra files in an additional recipe18:10
kergothvolker-: first of all, image features are recipe variables, you dont have to set them in local.conf, but can set them in the image, in which case it'd be impossible for the other recipe to know that it was set at all :)18:15
kergothsecond, what would happen if you 'bitbake some-read-write-image some-read-only-image'?18:15
kergothit just wouldn't make any sense18:15
volker-kergoth: true, didn't think about that bitbake line. You could argue now that bitbake is the perfect tool and should be able to identify image differences to move the modularity into the recipe ;)18:16
kergoththat wouldn't make sense18:16
kergothyou're not thinking about the fact that recipe emit binary packages, and then those binary packages can go into any number of images18:17
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC18:17
kergothin fact, the image can be created in an entirely separate build from the build which produced the binary package feed18:17
volker-I just looked into the openssh recipe, I personaly find it ugly to have readonly labled files in regular recipes18:17
kergotheither the read onlyw orkarounds ahve to be implemented in the image, or you can do something like split off additional packages which do the per-recipe read-only workarounds and then install those extra packages in the image the way we handle -dev/-dbg/-doc. i've done that in meta-read-only-rootfs in the past, but it proved to no longer really be necessary18:17
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has quit IRC18:17
volker-kergoth: you can have DISTRO_FEATURES in the recipe but not IMAGE_FEATURES, I think that can raise confusion18:20
kergothnot really18:20
kergotha distro is global18:20
kergothan image is a recipe18:20
kergoththey're not even comparable18:20
kergothby definition a distro affects multiple recipes, and by definition an image does not18:20
kergothone involves configuration metadata, one is recipe metadata18:20
kergoththe former flows into the latter, not vice versa18:21
volker-I get the logic behind it, still, as external user it can be somewhat confusing.18:21
kergothits not possibel for one recipe to inspect another recipe's metadata18:21
kergothnor will it ever be18:21
kergothif the external user doesn't grasp the difference between a distro and an image and a machine, then they need to go back to the docs, or we need better docs18:21
kergothits a basic fundamental concept without which they're not likely to get very far18:21
volker-FILES_${PN}-sshd += [...]18:22
volker-FILES_${PN}-sshd += "[...] ${sysconfdir}/ssh/sshd_config_readonly [...]"18:22
kergothi really don't think including a tiny config file in a main recipe is that harmful, but as i said, there are other options, you could split that out into as eparate package which is only installed when the read only feature is enabled for a given image18:23
volker-I can end up in a read-only labled file in a read-only image18:23
kergothoh no, a 5k file, the horror18:24
kergoth(possibly smaller)18:24
volker-it's not about the size, it is more a confusion point18:24
kergothregardless, this is how it works, a recipe that goes based on an image feature is a bug18:24
kergothif yo udont like how we're doing it, patches are welcome18:24
volker-I can live with it, just my feedback :)18:25
volker-I got through some learning curves (and am sure miss some other ones) in yocto :)18:25
kergothit's a tradeoff. to do it differently without fundametally breaking how bitbake works would be rather more complex, so we keep a file that *might* cause user confusion, in theory, possibly ,in favor of a simpler implementation18:26
*** JimBaxter <JimBaxter!> has quit IRC18:27
volker-Tomorrow is July, the yocto book release is expected for July18:28
dimi1what is the yocto book release? a book about yocto?18:30
vroomfondelfor me as a complete yocto beginner it seems central to understand bitbake first, right?18:31
volker-still no table of content18:31
dimi1volker-: 10x18:31
volker-vroomfondel: yes, somewhat, bitbake is huge and powerful. I think the basics are important.18:32
vroomfondelis there also a build process for bootloaders in yocto?18:33
kergothbootloaders are recipes like anything else. the recipes are marked so bitbake doesn't try to build the wrong one for a given machine, and it's appropriately pulled into image builds for machines that need them18:34
volker-vroomfondel: the image comes with a boot loader, you can dd it and boot from it. For grub I haven't found seen one, but you can install grub18:34
*** maxtothemax <maxtothemax!~maxtothem@> has quit IRC18:34
vroomfondelI am on an ARM18:34
volker-no hands on experience with ARM, but as I said, the default image I worked with always came with a working bootloader18:35
volker-I assume you can take a image and dd it to an SDcard and boot from it18:36
kergothsupport for sd card images varies with the machine/bsp, there's no standard mechanism for construction of a full disk image from a kernel+rootfs+bootloader in yocto at this time, but options do exist, it just depends on your hardware18:37
*** wv <wv!> has quit IRC18:37
*** melonipoika <melonipoika!> has quit IRC18:42
*** SorenHolm <SorenHolm!> has quit IRC18:44
halsteadWe are going to have 15-20 second bugzilla outage in a moment.18:45
*** SorenHolm <SorenHolm!> has joined #yocto18:45
*** maxtothemax <maxtothemax!~maxtothem@> has joined #yocto18:52
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC18:55
*** stryx`_ <stryx`_!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto18:56
*** kroon <kroon!> has joined #yocto19:03
*** hyei <hyei!> has joined #yocto19:04
*** yocti <yocti!> has joined #yocto19:15 [freenode-info] if you're at a conference and other people are having trouble connecting, please mention it to staff:
*** tasslehoff <tasslehoff!> has joined #yocto19:25
*** beaver_545 <beaver_545!~stuart@> has joined #yocto19:30
*** hyei <hyei!> has quit IRC19:34
*** mkeeter <mkeeter!> has quit IRC19:44
*** mkeeter <mkeeter!> has joined #yocto20:01
*** manuel__ <manuel__!> has joined #yocto20:02
*** manuel_ <manuel_!~manuel_@> has quit IRC20:02
*** manuel__ is now known as manuel_20:02
*** radzy is now known as radzy_away20:15
*** tasslehoff <tasslehoff!> has quit IRC20:21
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has joined #yocto20:22
*** hyei <hyei!~hyei@> has joined #yocto20:28
joshualamoriegidday there, I'm having some difficulty building a kernel module as a package within daisy.20:30
joshualamorieI have followed a couple of patterns already present, but I'm uncertain if they are going to be generally valid20:31
joshualamorieMy current problem is a missind scripts/basic/fixdep20:31
joshualamorieThere seems to be others who have encountered this.20:31
volker-nice new feature: The following packages could not be configuredoffline and rootfs only: ['mypackage']20:34
joshualamorieis there a 'canonical' complete example of a recipe for building an out-of-kernel module?20:36
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto20:37
volker-sorry, the correct string is " The following packages could not be configuredoffline and rootfs is read-only"20:38
*** sullical__ <sullical__!sullical@nat/intel/x-ottdmbwohnmvrqzv> has quit IRC21:02
*** sullical <sullical!~sullical@> has joined #yocto21:02
*** Jefro <Jefro!> has joined #yocto21:07
*** ant__ <ant__!> has joined #yocto21:11
*** mkeeter_ <mkeeter_!> has joined #yocto21:27
*** mckoan_ <mckoan_!~marco@unaffiliated/mckoan> has joined #yocto21:28
*** agust1 <agust1!> has joined #yocto21:30
*** dl9pf___ <dl9pf___!> has joined #yocto21:33
*** auke-_ <auke-_!~auke@> has joined #yocto21:34
*** mckoan|away <mckoan|away!~marco@unaffiliated/mckoan> has quit IRC21:34
*** agust <agust!> has quit IRC21:34
*** auke- <auke-!~auke@> has quit IRC21:35
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC21:35
*** jonmasters <jonmasters!> has quit IRC21:35
*** mkeeter <mkeeter!> has quit IRC21:35
*** jluisn <jluisn!~quassel@> has quit IRC21:35
*** akbennett <akbennett!akbennett@linaro/akbennett> has quit IRC21:35
*** dl9pf <dl9pf!~quassel@opensuse/member/dl9pf> has quit IRC21:35
*** ant__ <ant__!> has quit IRC21:35
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto21:36
*** akbennett <akbennett!akbennett@gateway/shell/linaro/x-blzjzavshgamjukl> has joined #yocto21:36
*** jonmasters_ <jonmasters_!> has joined #yocto21:37
*** ant__ <ant__!> has joined #yocto21:43
*** dimi1 <dimi1!~dimi@> has quit IRC21:46
*** radzy_away is now known as radzy21:47
*** fray <fray!> has quit IRC21:57
*** fray <fray!> has joined #yocto21:59
*** bfederau <bfederau!> has quit IRC22:01
*** bfederau <bfederau!> has joined #yocto22:01
*** radzy is now known as radzy_away22:05
*** mkeeter_ <mkeeter_!> has quit IRC22:12
*** hyei <hyei!~hyei@> has quit IRC22:23
*** hyei <hyei!~hyei@> has joined #yocto22:24
*** jackmitchell <jackmitchell!> has joined #yocto22:30
*** kroon <kroon!> has quit IRC22:30
*** seebs <seebs!> has quit IRC22:36
*** sjolley <sjolley!sjolley@nat/intel/x-iurjamepsxpnshfu> has quit IRC22:37
*** seebs <seebs!> has joined #yocto22:38
*** seebs_ <seebs_!> has joined #yocto22:40
*** ant__ <ant__!> has quit IRC22:40
*** agust1 <agust1!> has quit IRC22:40
*** seebs <seebs!> has quit IRC22:41
*** seebs_ is now known as seebs22:41
*** mkeeter <mkeeter!> has joined #yocto22:43
*** sameo <sameo!~samuel@> has joined #yocto22:44
*** nitink <nitink!nitink@nat/intel/x-qbzbfutcihkpfalk> has quit IRC22:45
*** beaver_545 <beaver_545!~stuart@> has quit IRC22:46
*** nitink <nitink!nitink@nat/intel/x-xpmqfgghxxlrwhlr> has joined #yocto22:46
*** jackmitchell <jackmitchell!> has quit IRC22:51
*** radzy_away is now known as radzy22:53
*** sjolley <sjolley!~sjolley@> has joined #yocto23:02
*** sjolley1 <sjolley1!sjolley@nat/intel/x-rpwuhxkfpneknvum> has joined #yocto23:04
*** nitink <nitink!nitink@nat/intel/x-xpmqfgghxxlrwhlr> has quit IRC23:05
*** sjolley <sjolley!~sjolley@> has quit IRC23:07
*** nitink <nitink!~nitink@> has joined #yocto23:22
*** acidx <acidx!> has joined #yocto23:23
*** manuel_ <manuel_!> has quit IRC23:41
*** d_s_e <d_s_e!> has quit IRC23:47
*** mkeeter <mkeeter!> has quit IRC23:48
*** mkeeter <mkeeter!~mkeeter@2601:6:b80:5a:e818:cdd0:9823:8a01> has joined #yocto23:48
*** munch <munch!> has quit IRC23:50

Generated by 2.11.0 by Marius Gedminas - find it at!