Thursday, 2015-08-27

dhircshould I move downloads outside as well?00:01
kergothunless you enjoy re-downloading stuff regularly00:03
khemthis is what enjoyment has come00:04
khemgoes in line with my proposal for adding wifi connectivity to fundamental human rights00:05
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC00:06
nerdboyyeah, slight typo...00:08
nerdboydhirc: yes both of them00:09
nerdboyyou can have multiple ones for different builds even00:09
nerdboy*as in not binary compatible00:09
*** nighty^ <nighty^!> has quit IRC00:10
*** alimon <alimon!alimon@nat/intel/x-mkusoiqadoyrpomq> has quit IRC00:11
tlwoernerkhem: *free* wifi?00:15
khem`yes that goes unsaid with human rights00:16
tlwoernerif only we knew someone who worked at some major ISP... maybe they could push that from the inside?00:16
nerdboysome cities have essentially free or very low cost fiber everywhere00:17
nerdboy*the smarter ones00:17
nerdboymemphis i think?00:17
khem`hmmm so -Wunused-command-line-argument-hard-error-in-future isnt repected by clang anymore00:17
khem`I guess they are breaking free from gcc00:17
khem`or less care what it supports anymore00:17
khem`so I guess "future" has happened00:18
nerdboydhirc: pretty sure one shared sstate-cache will do it00:19
nerdboycertain changes will invalidate it anyway, and it should manage what goes with what00:19
*** ftonello_ <ftonello_!~quassel@> has quit IRC00:22
dhircnerdboy: Do any of the recipes, like core-sato etc, come with USB Audio enabled out of the box?00:41
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has quit IRC00:46
-YoctoAutoBuilder- build #456 of nightly-rpm is complete: Success [build successful] Build details are at
*** tlwoerner <tlwoerner!~trevor@unaffiliated/tlwoerner> has quit IRC01:20
*** sjolley <sjolley!~sjolley@> has joined #yocto01:22
-YoctoAutoBuilder- build #458 of nightly-mips-lsb is complete: Success [build successful] Build details are at
nerdboydhirc: that would depend pn which kernel it uses01:24
nerdboy*on even01:24
nerdboycheck if there's a defconfig in recipe?01:25
nerdboyotherwise use your own or make a "fragment" and a bbappend01:25
nerdboythe fragment thing is all explained in kernel-lab training link on yoctoproject01:26
nerdboyi tested it a while ago and it works with yocto-derived kernel recipes01:27
nerdboyeg, take your default beaglebone config in yocto01:28
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC01:29
nerdboymake or modify kernel bbappend, add src_uri for config fragment, drop fragment in files dir, rebuild kernel01:30
nerdboyeasy as pie...01:31
dhircnerdboy: I tred adding a fragment, and also added usbutil to get lsusb etc to debug. When I run lsusb I get this "unable to initialise libusb: -99"01:32
*** phantoneD <phantoneD!> has quit IRC01:32
nerdboyfor what machine/kernel/version?01:33
dhircbeagblebone (beaglebone black), yocto 3.14 / fido 1.801:33
nerdboyusb audio/touchscreen works for me on beaglebone...01:33
dhircwith core minimal?01:34
nerdboyi would switch from yocto bsp to meta-ti bsp01:34
nerdboyand use master branch01:34
nerdboyor fido if you have a requirement for that01:34
dhircIt says "Compatible with Yocto version/s: 1.6"01:34
nerdboywhat says?01:35
dhircI thought it was all merged with the main yocto meta?01:35
dhircSeems to be a lot of stale info in this space?01:35
nerdboytrust me, replace yocto-bsp layer with meta-ti and set your kernel to ti-staging01:35
*** sameo_ <sameo_!samuel@nat/intel/x-sgphbrsppjfjfbzy> has quit IRC01:36
nerdboyyocto build of beaglebone is not very optimal01:37
dhircwhen you say "set your kernel to ti-staging" where do I do that?01:37
nerdboywell, yocto-linux (mainline) is still not quite ready for beaglebone01:37
nerdboylocal.conf add PREFERRED_PROVIDER_virtual/kernel = "recipe-name"01:38
nerdboybetter grep for that to be safe...01:38
nerdboyit might be default on master01:38
dhircSo I change edit my conf/bblayers and replace yocto-bsp with the meta-ti one and update preferred provider to ti-staging01:38
* nerdboy looks at denix 01:38
nerdboygrep and see what it is in meta-ti01:39
nerdboyi need to boot up another machine to see latest config01:40
* nerdboy building for imx right now01:40,, which should I use?01:41
-YoctoAutoBuilder- build #475 of nightly-x86 is complete: Success [build successful] Build details are at
nerdboybut it's much newer on master i believe01:41
nerdboyall my current crap is fsl right now, lemme go fire up the other one...01:42
nerdboyyup linux-ti-staging_4.1.bb01:49
nerdboyon recent master, which has a lot more new stuff in it01:50
nerdboyplus DT overlays01:50
* nerdboy on the embedded bleeding edge, so...01:50
dhircok. Not sure I want staging though - sounds unstable? 3.14 mainline may be a better bet?01:53
dhircwill build staging first though and see if it just works01:53
*** dreyna4529 <dreyna4529!> has quit IRC01:58
dhircnerdboy: Do you have a copy of your local.conf, bblayers and what bitbake (image, target-thing) you built? Would be good to have a working references to start from. Currently still building my first try..02:12
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto02:15
nerdboystaging is where stuff goes first02:15
nerdboyyou want it02:15
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC02:19
-YoctoAutoBuilder- build #119 of nightly-mips64 is complete: Failure [failed Running Sanity Tests] Build details are at
*** fishey1 is now known as jmesmon02:29
-YoctoAutoBuilder- build #118 of nightly-arm64 is complete: Success [build successful] Build details are at
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto02:36
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC02:39
*** radhus <radhus!> has quit IRC02:43
*** mrsan- <mrsan-!mrsan@2a00:1a28:1157:42::5> has quit IRC02:44
dhircnerdboy: I get the exact same issue regarding lsusb for the meta-ti staging build?02:45
nerdboycan you get the config out of proc?02:46
nerdboymight need to modprobe configs02:46
*** phantoxeD <phantoxeD!> has joined #yocto03:01
kergothhmm, does use of VPATH cause problems for the -dbg code which grabs source files?03:04
kergothseems like it should be looking in both B and S for relative paths03:04
darknightekergoth:  you got a link to the repo generator?03:04
kergothit's in codebench svn, p2_repogenerator. could also look at the yaml based bits fahad did (iirc) which uses the stock p2 stuff03:06
*** Luming <Luming!luyu@nat/intel/x-jpdopqjspehnbgmt> has quit IRC03:08
kergoth gnu-devel -n -U -h i686-pc-linux-gnu sgxx/trunk/arm-none-linux-gnueabi-sourceryg++  init/build_p2_repogenerator from my shell history on build5 in the server farm seems promising, but it requires a gnu-checkout03:08
kergothactually, it looks like i have a tarball with built binaries03:08
*** Luming <Luming!luyu@nat/intel/x-kioljwjeknuxrufs> has joined #yocto03:09
nerdboydhirc: i would probably enable these too03:09
nerdboy# CONFIG_SND_HRTIMER is not set03:09
nerdboy# CONFIG_SND_DYNAMIC_MINORS is not set03:09
*** [Sno] <[Sno]!> has quit IRC03:09
nerdboylemme look at usb...03:09
nerdboyi would make EHCI not modules, and either similar for OHCI or disable it03:11
nerdboyusb tends to be crucial on these things so just compile it in03:12
kergother, wrong channel03:12
darknightekergoth: crud.03:13
nerdboyother stuff can be modules, just not the primary controller stuff03:13
nerdboydhirc: yes03:13
nerdboyplus omap support03:13
nerdboysome of these things do almost everything over usb bus...03:14
nerdboylook at rpi model b03:15
* nerdboy would've paid another 89 cents for a real network chip...03:16
-YoctoAutoBuilder- build #126 of nightly-rpm-non-rpm is complete: Success [build successful] Build details are at
*** jkridner|work <jkridner|work!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto03:18
* nerdboy getting tennis-spectator-neck bouncing between channels03:19
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC03:19
-YoctoAutoBuilder- build #466 of nightly-multilib is complete: Success [build successful] Build details are at
-YoctoAutoBuilder- build #457 of nightly-ipk is complete: Failure [failed Running Sanity Tests Running Sanity Tests_1 Running Sanity Tests_2] Build details are at
-YoctoAutoBuilder- build #474 of nightly-arm is complete: Success [build successful] Build details are at
*** Luming <Luming!luyu@nat/intel/x-kioljwjeknuxrufs> has quit IRC03:46
*** Luming <Luming!luyu@nat/intel/x-cqdwzlnrkdqxpfdb> has joined #yocto03:47
-YoctoAutoBuilder- build #473 of nightly-x86-64-lsb is complete: Failure [failed Running Sanity Tests] Build details are at
*** adelcast <adelcast!~adelcast@> has quit IRC03:56
*** rci_ <rci_!> has joined #yocto03:57
*** rci <rci!> has quit IRC03:58
*** jmpdelos <jmpdelos!> has quit IRC03:58
*** wenzong <wenzong!~wfan@> has quit IRC03:58
*** jmpdelos <jmpdelos!> has joined #yocto03:58
*** wenzong <wenzong!~wfan@> has joined #yocto03:58
-YoctoAutoBuilder- build #19 of nightly-wic is complete: Success [build successful] Build details are at
-YoctoAutoBuilder- build #464 of nightly-qa-skeleton is complete: Success [build successful] Build details are at
*** adelcast <adelcast!~adelcast@> has joined #yocto04:09
dhircnerdboy: It seems my fragment is not being applied when I look at /proc/config.gz.. I have create a meta layer (meta-bbb-via) and have added a .bbappend (, and the cfg ( My local and bblayers are and What am I doing wrong here?04:09
*** dreyna4529 <dreyna4529!> has joined #yocto04:26
*** redengin <redengin!> has quit IRC04:44
*** redengin <redengin!~redengin@2601:600:9200:7ab0:fc0f:1b01:eafa:205> has joined #yocto04:44
-YoctoAutoBuilder- build #464 of nightly-oecore is complete: Failure [failed Running Sanity Tests] Build details are at
-YoctoAutoBuilder- build #119 of nightly-arm64 is complete: Failure [failed Running Sanity Tests] Build details are at
*** hamis <hamis!~irfan@> has joined #yocto05:09
*** dshwang <dshwang!~dshwang@> has quit IRC05:11
*** dshwang <dshwang!~dshwang@> has joined #yocto05:13
*** [Sno] <[Sno]!> has joined #yocto05:18
*** loggerbox <loggerbox!todor@nat/intel/x-xwekhlhvrsexjlwb> has quit IRC05:30
*** tripzero_ <tripzero_!tripzero@nat/intel/x-caspkxuvqcgpeaky> has quit IRC05:30
-YoctoAutoBuilder- build #462 of nightly-qa-systemd is complete: Success [build successful] Build details are at
*** dshwang <dshwang!~dshwang@> has quit IRC05:30
*** loggerbox <loggerbox!todor@nat/intel/x-tqbeykphnoelbznt> has joined #yocto05:30
*** tripzero_ <tripzero_!tripzero@nat/intel/x-gmvuymjxwftbglea> has joined #yocto05:30
*** tripzero1 <tripzero1!tripzero@nat/intel/x-nlrfniuvwmkwiaxm> has joined #yocto05:30
*** dshwang <dshwang!~dshwang@> has joined #yocto05:30
*** tripzero <tripzero!tripzero@nat/intel/x-hdwtjqgmxxqszzfe> has quit IRC05:31
nerdboyi don't see anything jumping out...05:31
nerdboyhang on a sec05:31
nerdboythat's it05:36
nerdboytry adding machine to that append05:36
nerdboydhirc: ^^05:37
nemequI have a recipe which requires a variable be set in another recipe… how would I do that?  FWIW it is one of the variables in that I need to set.05:42
nemequOr should I be appending to that file (config.txt) directly from my recipe instead of trying to go through a variable?05:42
*** opennandra <opennandra!> has quit IRC05:46
redenginnemequ, using a local file to your recipe is probably the best practice05:46
nemequredengin, I have to add something to a file generated by that recipe (config.txt), AFAIK there is no other way to do what I need.05:47
nerdboyi take it it's not one of the options there now?05:48
nemequnerdboy, nope, it's i2c… i have a patch to add it, which I'm planning on submitting as soon as I get everything working05:48
nerdboyadd i2c as option to what?05:49
*** nemequ <nemequ!> has left #yocto05:49
redengincan you just chain in for now and use sed like the current recipe, but with your i2c variable?05:49
*** nemequ <nemequ!> has joined #yocto05:49
nerdboyworks when you load kernel modules05:49
nemequsorry, did I miss something when i accidentally closed the channel?05:50
nerdboyoh, the dt option05:50
nemequnm, channel logs05:50
nerdboythat could go up to to az guy05:50
* nerdboy steals it for his fork05:51
*** redengin <redengin!~redengin@2601:600:9200:7ab0:fc0f:1b01:eafa:205> has quit IRC05:52
*** redengin <redengin!~redengin@2601:600:9200:7ab0:fc0f:1b01:eafa:205> has joined #yocto05:52
redenginnemequ, how about just using bbappend and adding a predeploy task before deploy05:53
nemequand append to the file?  is that considered to be a good practice?05:54
redenginnemequ, err, make that a postdeploy  :)  since deploy is copying the file in05:54
nemequi'm planning on trying to get this integrated in meta-raspberrypi, so i want to do it right and i have no issue with modifying the existing recipe, if that matters...05:54
redenginnemequ, how about "addtask do_postdeploy after do_deploy before do_package05:57
nerdboyjust patch yours with that05:57
nerdboyenable the dt stuff, etc...05:58
redenginif you can live with a local recipe branch, thats probably best, doesn't rpi need this support anyway?05:58
nerdboythey just tell you to enable it manually05:58
nemequnerdboy, you mean the patch i posted?  that's what I'm doing, and setting ENABLE_I2C in my local.conf…05:58
*** opennandra <opennandra!> has joined #yocto05:59
nerdboygreat, let me know how that goes...05:59
nemequyeah, it's probably something that should be there, but i'd like to avoid making people enable it manually05:59
nemequnerdboy, it goes fine, i've been doing it for weeks.05:59
redenginnerdboy, manually when?  upon runtime?05:59
nerdboyno, that particular patch05:59
nerdboymanually edit config.txt or use the config tool i guess06:00
redenginah, cuz there could always be boot issues with a bunch of unserviceable interrupts enabled06:00
nerdboydt stuff is "relatively" new...06:00
nerdboylast i checked, the readme did not say anything about stable...06:01
redenginwhats dt stand for?06:01
nerdboydevice tree06:01
nemequredengin, device tree06:01
* nerdboy 's fork is a bit older than weeks06:02
nerdboyforked it from the original guy06:02
redenginwhat does config.txt do differently than the kernel config?06:03
redengini.e. do you need i2c to boot?06:03
nerdboyno, it's runtime config06:04
redengink, the "*-bootfiles" made me think this is pre-kernel06:04
redenginso, then is this just another path to setting the kernel config?06:05
nerdboynothing to do with kernel config06:05
nerdboybut you do need the right stuff enabled for the runtime options to mean anything06:06
*** pohly <pohly!> has joined #yocto06:06
nerdboyit's convenience06:06
redenginso what do these settings do that the kernel doesn't?06:07
nerdboymaybe read the comments?06:07
nerdboythe full config.txt is mostly comments06:08
*** tasslehoff <tasslehoff!~Tasslehof@> has joined #yocto06:08
nemequredengin, may help06:10
redenginso, my googling says this config.txt is the stand-in bios06:10
nemequthat actually sounds like a pretty good description to me…06:11
*** bzb <bzb!> has joined #yocto06:11
*** bzb <bzb!> has quit IRC06:12
*** AndersD <AndersD!> has joined #yocto06:15
nemequso basically, I have a recipe to add support for the PiFace RTC (, which requires i2c.  in order to do that i need to write a line to config.txt, which is provided by… what is the *right* way to do that?06:17
nemequthat patch i posted earlier works okay, but requires (afaik) intervention in local.conf, which I would like to avoid… i want to put something in my piface-rtc recipe, if possible, to just automatically enable it06:18
nemequthe postdeploy thing seems feasible, but it also seems like a bit of a hack so i'm not sure it would be accepted06:20
redengindoes the rpi bsp kernel config already enable i2c?06:21
nemequwithout adding something to config.txt the kernel can't communicate with the clock :(06:22
redenginthen I'd just append the kernel config to enable i2c and not let the user via config.txt disable it06:23
-YoctoAutoBuilder- build #451 of nightly-arm-lsb is complete: Success [build successful] Build details are at
nemequi don't think that will work.  based on it sounds like the firmware needs to know to enable config.txt, not just the kernel06:24
nemequ^ @ redengin06:24
nemequsee the second paragraph on that page06:25
nemequerr, the firmware needs to know to enable *i2c*, not just the kernel06:26
redenginsounds like rpi isn't sharing its device code, so it must do it itself06:27
redenginwithout knowing more about the rpi yocto architecture I really don't have any good suggestions beyond the postdeploy06:28
*** jku <jku!jku@nat/intel/x-lqgzndfipptvnkvr> has joined #yocto06:29
redenginyou should just submit your patch as an addition to do_deploy and I'm sure they'd be happy with it06:29
nemequok, i'll do that06:29
nemequthanks for the help redengin, nerdboy06:30
nerdboycould for and do pull request06:31
redenginnemequ, you may want to change it to a sed one liner to follow suit with their recipe06:31
nerdboyor open issue here:
-YoctoAutoBuilder- build #452 of nightly-arm-lsb is complete: Failure [failed Running Sanity Tests] Build details are at
nerdboy*fork even06:32
nerdboyor spork maybe06:32
nemequnerdboy, using seed would require a placeholder in config.txt06:32
nemequ"#enable_i2c" or something so i could s/#enable_i2c/dtparam=i2c=on/06:33
redenginnemequ, I assumed that a stand in for bios would already have explicit defaults, but perhaps I assume too much06:33
nemequwell that config file is part of the meta-raspberrypi repo, so i could add a placeholder…06:33
redenginI'd definitely suggest adding explicit defaults in a config.txt.patch with your pull request06:34
nemequyeah, that seems reasonable06:34
*** benjamirc <benjamirc!~besquive@> has quit IRC06:35
*** aj_c <aj_c!Alex_Joya@nat/intel/x-fenwtxobqmkynuhi> has quit IRC06:35
*** tripzero_ <tripzero_!tripzero@nat/intel/x-gmvuymjxwftbglea> has quit IRC06:35
*** glfernando <glfernando!~fernando@> has quit IRC06:35
*** marquiz <marquiz!~marquiz@> has quit IRC06:35
*** clsulliv <clsulliv!clsulliv@nat/intel/x-mhblahztlhilkbou> has quit IRC06:35
*** ulf` <ulf`!ulf@nat/intel/x-vkgrgwahfnkolywt> has quit IRC06:35
*** loggerbox <loggerbox!todor@nat/intel/x-tqbeykphnoelbznt> has quit IRC06:35
*** tripzero1 <tripzero1!tripzero@nat/intel/x-nlrfniuvwmkwiaxm> has quit IRC06:35
*** sjolley <sjolley!~sjolley@> has quit IRC06:36
*** igor <igor!~Igor_Stop@> has quit IRC06:36
redenginso, whats the rpi community doing these days?  I'm always looking for a reason to write some code06:39
*** grma <grma!> has joined #yocto06:45
*** frsc <frsc!> has joined #yocto06:48
*** tripzero <tripzero!tripzero@nat/intel/x-ywpgejgpryvrqoky> has joined #yocto06:49
*** benjamirc <benjamirc!~besquive@> has joined #yocto06:49
*** loggerbox <loggerbox!~todor@> has joined #yocto06:49
*** sjolley <sjolley!~sjolley@> has joined #yocto06:50
*** tripzero_ <tripzero_!~tripzero@> has joined #yocto06:50
*** aj_c <aj_c!~Alex_Joya@> has joined #yocto06:50
*** frsc <frsc!> has joined #yocto06:50
*** igor <igor!~Igor_Stop@> has joined #yocto06:50
*** ylouise <ylouise!~yalouise@> has joined #yocto06:51
*** clsulliv <clsulliv!clsulliv@nat/intel/x-xifslxpezriuokwn> has joined #yocto06:51
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has joined #yocto06:54
*** jbrianceau_away is now known as jbrianceau06:54
*** ulf` <ulf`!~ulf@> has joined #yocto06:55
*** TobSnyder <TobSnyder!> has joined #yocto07:03
*** florian_kc is now known as florian07:26
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-wfxshtjhztzbxlgh> has joined #yocto07:29
*** dreyna4529 <dreyna4529!> has quit IRC07:29
*** roccof <roccof!> has joined #yocto07:34
*** uggedal <uggedal!> has quit IRC07:35
*** tripzero_ <tripzero_!~tripzero@> has quit IRC07:37
*** tripzero <tripzero!tripzero@nat/intel/x-ywpgejgpryvrqoky> has quit IRC07:37
*** sjolley <sjolley!~sjolley@> has quit IRC07:38
*** loggerbox <loggerbox!~todor@> has quit IRC07:38
*** clsulliv <clsulliv!clsulliv@nat/intel/x-xifslxpezriuokwn> has quit IRC07:38
*** ylouise <ylouise!~yalouise@> has quit IRC07:38
*** aj_c <aj_c!~Alex_Joya@> has quit IRC07:38
*** igor <igor!~Igor_Stop@> has quit IRC07:38
*** benjamirc <benjamirc!~besquive@> has quit IRC07:38
*** sjolley <sjolley!~sjolley@> has joined #yocto07:38
*** tripzero <tripzero!tripzero@nat/intel/x-imqxfjkdjekxpqsk> has joined #yocto07:38
*** tripzero_ <tripzero_!tripzero@nat/intel/x-ehnyorcrcvxfrpsz> has joined #yocto07:38
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC07:39
*** igor <igor!~Igor_Stop@> has joined #yocto07:39
*** benjamirc <benjamirc!besquive@nat/intel/x-lsgqfvltnrxdgprr> has joined #yocto07:39
*** ylouise <ylouise!~yalouise@> has joined #yocto07:39
*** clsulliv <clsulliv!clsulliv@nat/intel/x-fvcuelejydwlwgze> has joined #yocto07:39
*** aj_c <aj_c!Alex_Joya@nat/intel/x-nfoltfeoxitinqbl> has joined #yocto07:40
*** loggerbox <loggerbox!todor@nat/intel/x-nnozgclbpjtigoev> has joined #yocto07:40
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto07:40
*** psnsilva <psnsilva!> has joined #yocto07:41
*** jonathanmaw <jonathanmaw!> has joined #yocto07:54
*** [Sno] <[Sno]!> has quit IRC07:59
*** TobSnyder1 <TobSnyder1!> has joined #yocto07:59
*** sameo_ <sameo_!~samuel@> has joined #yocto08:02
*** TobSnyder <TobSnyder!> has quit IRC08:02
*** [Sno] <[Sno]!> has joined #yocto08:03
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto08:06
*** Daemon404 <Daemon404!~who_knows@pdpc/supporter/student/Daemon404> has quit IRC08:15
*** hamis <hamis!~irfan@> has quit IRC08:16
*** Daemon404 <Daemon404!~who_knows@> has joined #yocto08:24
bluelightningmorning all08:25
*** hamis <hamis!~irfan@> has joined #yocto08:27
*** jimBaxter <jimBaxter!> has joined #yocto08:27
*** CromFr <CromFr!~CromFr@> has quit IRC08:29
-YoctoAutoBuilder- build #461 of nightly-ppc-lsb is complete: Success [build successful] Build details are at
*** TobSnyder <TobSnyder!> has joined #yocto08:38
*** TobSnyder1 <TobSnyder1!> has quit IRC08:40
*** ftonello <ftonello!~quassel@> has joined #yocto08:41
*** nighty^ <nighty^!> has joined #yocto08:44
*** belen <belen!Adium@nat/intel/x-yaigxvrchleblyhy> has joined #yocto08:44
*** rburton <rburton!> has joined #yocto08:52
*** marquiz <marquiz!marquiz@nat/intel/x-heikqfgixbeaboxe> has joined #yocto08:54
-YoctoAutoBuilder- build #459 of nightly-mips-lsb is complete: Failure [failed Running Sanity Tests BuildImages_1] Build details are at
JYDawgquestion: I have a package which in its bitbake recipe needs a hook for preupgrade.08:57
-YoctoAutoBuilder- build #161 of nightly-oe-selftest is complete: Success [build successful] Build details are at
JYDawgis there any way to create this?08:59
bboozzooJYDawg: take a look at prerm, postrm, preinst hooks,
*** sameo_ <sameo_!~samuel@> has quit IRC09:19
JYDawgbboozzoo: looking at the code ... no reference to upgrade.09:27
sujith_hbluelightning: ping09:27
sujith_hbluelightning: I would like to spend some effort on If you can guide me on the same, like how to move ahead with the task, it would be great help for me.09:27
yoctiBug 6787: enhancement, Medium, 2.1, unassigned, NEW , Cancelling builds at any point in the build process09:27
bluelightningsujith_h: I think there are several challenges with this one09:31
bluelightningsujith_h: the first is that only one controlling UI can connect to the bitbake server at once, so it's not possible to connect to the running server separately and tell it to stop09:32
*** CromFr <CromFr!~CromFr@> has joined #yocto09:32
bluelightningsujith_h: the other I guess is that bitbake might not be running at that point at all (it might still be fetching metadata)09:34
bluelightningsujith_h: the first problem might be easy to work around by just sending SIGINT to the bitbake UI process09:35
bluelightningif you want to force stop you'd just send it twice09:35
bluelightningit's not the ideal solution though and I'm not sure how practical it will be09:35
*** CromFr <CromFr!~CromFr@> has quit IRC09:36
*** CromFr <CromFr!~CromFr@> has joined #yocto09:36
sujith_hbluelightning: I was thinking about the same. Like an button to stop bitbake process which would send SIGINT09:36
*** CromFr <CromFr!~CromFr@> has quit IRC09:36
sujith_hbluelightning: but as you said right, its a work around09:36
*** CromFr <CromFr!~CromFr@> has joined #yocto09:37
*** _4urele_ <_4urele_!> has quit IRC09:45
*** sameo_ <sameo_!~samuel@> has joined #yocto09:50
*** sno <sno!> has joined #yocto09:51
*** [Sno] <[Sno]!> has quit IRC09:51
*** CromFr <CromFr!~CromFr@> has quit IRC09:52
*** CromFr <CromFr!~CromFr@> has joined #yocto09:52
*** realBigfoot <realBigfoot!~realBigfo@> has quit IRC10:00
*** realBigfoot <realBigfoot!~realBigfo@> has joined #yocto10:00
*** dv__ <dv__!> has quit IRC10:28
*** dv__ <dv__!> has joined #yocto10:32
*** Crofton <Crofton!~balister@> has joined #yocto10:55
*** jeremiah_afk is now known as jeremiah11:01
LocutusOfBorg1Hi folks, I'm porting python-gst1.0 to yocto, would you apply a patch on poky?11:03
bluelightninggood question11:09
bluelightningassuming you effectively mean "would we put python-gst in OE-Core", it depends on whether that needs to be aligned closely with gstreamer itself11:10
LocutusOfBorg1I see it there11:12
LocutusOfBorg1so I would like to give you a ./poky/meta/recipes-devtools/python/python-gst1.0_1.5.2.bb11:12
LocutusOfBorg1or whatever, isn't that already part of core?11:12
bluelightningLocutusOfBorg1: there is a python-gst in meta-multimedia (part of the meta-openembedded repo), it's 0.10.x though11:15
bluelightningLocutusOfBorg1: I'd probably go for adding it to meta-multimedia11:15
LocutusOfBorg1so would you accept a recipe?11:17
bluelightningwell, it's not really up to me :)11:19
bluelightningbut I would say since we have python-gst in meta-multimedia, the right place to add the 1.0 version is meta-multimedia rather than the core11:20
bluelightning(in case it's not clear, poky is really a combination of several different components; the recipes under meta/ come from OE-Core and poky just pulls those in verbatim - so any additions/changes to those are sent to OE-Core first and then they automatically come into the poky repository; however that wouldn't apply here if the recipe was instead added to meta-multimedia, that's completely separate)11:22
bluelightningin case you haven't seen it:
LocutusOfBorg1so where does this come from?11:23
bluelightningseems like that's in fido but not master11:23
bluelightningI was looking at master11:23
LocutusOfBorg1oh... sorry, I always work with fido sure11:24
bluelightningright, just looked at the history - it was moved out because it's the obsolete 0.10.x version11:24
LocutusOfBorg1strange to find something in fido and not in master...11:24
bluelightningI'm honestly not sure now11:24
bluelightningrburton: where do you think python-gst 1.0 ought to go? OE-Core or meta-multimedia?11:24
LocutusOfBorg1anyway I'm writing the recipe, if you have a place, I'll be so happy to contribute11:25
bluelightningLocutusOfBorg1: ok, that's great... I'm sure there will be a home for it :)11:26
*** Crofton <Crofton!~balister@> has quit IRC11:31
*** JaMa <JaMa!> has joined #yocto11:38
snoI have a weird problem and don't know how to start debug it ...11:43
snoI have a recipe "foo" - this contains several packages: foo-bar, foo-runtime, foo-extra, foo-doc, ...11:44
snofor some kind of reason, bitbake doesn't find foo-bar and so depending packages fail11:45
rburtonbluelightning: doesn't new python-gst need meta-gir?11:45
*** jku <jku!jku@nat/intel/x-lqgzndfipptvnkvr> has quit IRC11:59
*** varibull <varibull!> has quit IRC12:09
*** varibull <varibull!> has joined #yocto12:10
*** simmel80 <simmel80!> has joined #yocto12:17
bluelightningrburton: possibly, not sure12:21
*** libv <libv!> has left #yocto12:21
LocutusOfBorg1rburton, not sure, for now I need to write a recipe for python-pyygobject312:22
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-wfxshtjhztzbxlgh> has quit IRC12:25
*** varibull <varibull!> has quit IRC12:25
*** varibull <varibull!> has joined #yocto12:25
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-hlnelzponalibtgq> has joined #yocto12:26
rburtonyeah that's where gir comes in i'm sure12:37
-YoctoAutoBuilder- build #159 of nightly-oe-selftest is complete: Failure [failed Running oe-selftest] Build details are at
*** Crofton <Crofton!~balister@> has joined #yocto12:54
*** lamego <lamego!lamego@nat/intel/x-ywihlxvukqcfulux> has joined #yocto12:58
*** jku <jku!jku@nat/intel/x-qrvxfwrmdskwmfwp> has joined #yocto13:11
*** anselmolsm <anselmolsm!anselmolsm@nat/intel/x-akouowoxsqfcpwel> has joined #yocto13:15
-YoctoAutoBuilder- build #476 of nightly-arm is complete: Success [build successful] Build details are at
*** tsramos <tsramos!tsramos@nat/intel/x-dkfqywybiazbeson> has joined #yocto13:22
*** dmoseley <dmoseley!> has joined #yocto13:24
*** cference <cference!> has joined #yocto13:33
*** jku <jku!jku@nat/intel/x-qrvxfwrmdskwmfwp> has quit IRC13:35
*** tasslehoff <tasslehoff!~Tasslehof@> has quit IRC13:47
*** grma <grma!> has quit IRC14:04
*** lilwyrm <lilwyrm!~wyrm@> has quit IRC14:07
*** madisox <madisox!> has joined #yocto14:10
*** jku <jku!> has joined #yocto14:10
*** AndersD <AndersD!> has quit IRC14:14
*** opennandra <opennandra!> has quit IRC14:14
*** Daemon404 <Daemon404!~who_knows@> has quit IRC14:16
*** Daemon404 <Daemon404!~who_knows@pdpc/supporter/student/Daemon404> has joined #yocto14:16
*** opennandra <opennandra!> has joined #yocto14:23
*** marcin_ <marcin_!c39feabe@gateway/web/freenode/ip.> has joined #yocto14:23
marcin_hi guys14:23
marcin_I am new to yocto and I am trying to build my first image14:24
*** sujith_h <sujith_h!~sharidas@kde/developers/sujithh> has left #yocto14:24
marcin_as a target I've picked up raspberrypi14:24
marcin_I have problem building it14:24
marcin_my host OS is Ubuntu1214:25
marcin_and I am facing problems building dpkg (dpkg_1.17.21)14:25
marcin_ERROR: Task 192 (virtual:native:/home/a10053/yocto/poky/meta/recipes-devtools/dpkg/, do_compile) failed with exit code '1'14:25
marcin_but the thing is that after running 'bitbake -c compile dpkg' everythings is just fine14:26
*** sgw_ <sgw_!> has joined #yocto14:27
marcin_any hints why it is not working while building whole image running 'bitbake rpi-basic-image' while is fine with previous command?14:27
*** bigwyrm <bigwyrm!~wyrm@> has joined #yocto14:29
bluelightningmarcin_: can you use pastebin to show us more of the error message?14:30
marcin_error is here: /usr/local/include/bson.h:63:2: error: #error Must compile with c99 or define MONGO_HAVE_STDINT, MONGO_HAVE_UNISTD, MONGO_USE__INT64, or MONGO_USE_LONG_INT.14:30
marcin_my question is why this is working while compiling just this one single package14:31
marcin_and not when building whole image14:31
marcin_also I am wondering how to force c99 for building dpkg14:32
marcin_should I configure this in 'poky/meta/recipes-devtools/dpkg/' ?14:32
marcin_also if do_compile is not defined where this one is inherited from?14:33
fraytypically it's -std=c99  You can add that to the CFLAGS in the recipe if necessary.. but I find that very odd that dpkg does do that itself if it actually needs c9914:33
bluelightningmarcin_: is dpkg-native actually being built when building rpi-basic-image?14:33
bluelightningmarcin_: I'm not sure it would be by default14:34
zeddiiis anyone successfully using SYSTEMD_AUTO_ENABLE ? I suspect it is broken, and can't find a working reference .. so if someone has one, I'd appreciate the link.14:37
*** marcin__ <marcin__!c39feabe@gateway/web/freenode/ip.> has joined #yocto14:38
marcin__see this for full log:
*** marcin_ <marcin_!c39feabe@gateway/web/freenode/ip.> has quit IRC14:39
marcin__looks like package is taken to be build14:40
*** ylouise <ylouise!~yalouise@> has left #yocto14:43
*** aehs29 <aehs29!~aehernan@> has joined #yocto14:44
*** marcin__ <marcin__!c39feabe@gateway/web/freenode/ip.> has quit IRC14:44
*** marcin_ <marcin_!c39feabe@gateway/web/freenode/ip.> has joined #yocto14:44
*** staylor <staylor!> has joined #yocto14:50
*** ftonello <ftonello!~quassel@> has quit IRC14:54
*** r24s <r24s!d0b90c36@gateway/web/freenode/ip.> has joined #yocto14:55
*** sujith_h <sujith_h!~sharidas@kde/developers/sujithh> has joined #yocto14:56
*** hamis <hamis!~irfan@> has quit IRC15:02
rburtonhuh how does bind-dev work15:02
*** alimon <alimon!alimon@nat/intel/x-wwitlnucnsinvlav> has joined #yocto15:02
rburtonits full of headers but no libraries anywhere15:03
rburtonoh, static libs only?15:03
*** ftonello <ftonello!~quassel@> has joined #yocto15:03
*** frsc <frsc!> has quit IRC15:07
*** ftonello <ftonello!~quassel@> has quit IRC15:11
*** aehs29 <aehs29!~aehernan@> has quit IRC15:11
*** aehs29 <aehs29!~aehernan@> has joined #yocto15:14
*** raykinsella781 <raykinsella781!rkinsell@nat/intel/x-nugbxuezmlrgxebx> has joined #yocto15:15
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-hlnelzponalibtgq> has quit IRC15:16
*** ftonello <ftonello!~quassel@> has joined #yocto15:16
*** cference <cference!> has quit IRC15:17
*** raykinsella781 <raykinsella781!rkinsell@nat/intel/x-nugbxuezmlrgxebx> has left #yocto15:19
kergothzeddii: i've used it in the past -- it just arranges to run systemctl enable / disable in the postinst/prerm. if your service file doesn't have the needed wantedby/etc, the enable/disable might not do what you want..15:20
*** sjolley <sjolley!~sjolley@> has quit IRC15:20
*** TobSnyder <TobSnyder!> has quit IRC15:29
marcin_how to add C flags to be used for compilation of some given package?15:30
*** ftonello <ftonello!~quassel@> has quit IRC15:32
bluelightningmarcin_: CFLAGS_append = " --desired-option" - you'd put that in the recipe itself (or a bbappend if you're applying it to an existing recipe in someone else's layer that you're using)15:33
bluelightningmarcin_: another alternative is to do CFLAGS_append_pn-recipename = ... at the configuration level15:33
*** ftonello <ftonello!~quassel@> has joined #yocto15:33
*** diego_r <diego_r!> has quit IRC15:34
*** tsramos <tsramos!tsramos@nat/intel/x-dkfqywybiazbeson> has quit IRC15:34
marcin_bluelightning: thanks15:37
daleg_when yocto goes to create a DEB package of the kernel, where are the contents of the DESCRIPTION field sourced from?15:38
marcin_and what about defining some env variables for specific package?15:38
marcin_is do_configure and export good place to do so?15:42
bluelightningmarcin_: you can certainly do it that way yes15:42
*** ftonello <ftonello!~quassel@> has quit IRC15:42
kergothdaleg_: the DESCRIPTION metadata variable.15:43
*** ftonello <ftonello!~quassel@> has joined #yocto15:43
daleg_kergoth: right, of course. I'm trying to hunt down where that is, because yocto (rather, python) is bombing when creating my kernel deb because it's blindly trying to re-encode a UTF-8 string into a UTF-8 string, which python can't cope with and the run bombs with a stacktrace.15:46
kergothas with any metadata variable, you can inspect what it's set to, and how it got set that way, with bitbake -e15:46
kergothbitbake -e yourrecipe15:46
daleg_cool, thanks. I'm fumbling around in the dark here given that I've really only been working with yocto for a few days now.15:47
*** jkridner|work is now known as jkridner15:47
*** dreyna4529 <dreyna4529!> has joined #yocto15:48
*** psnsilva <psnsilva!> has quit IRC15:50
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has quit IRC15:54
*** sjolley <sjolley!~sjolley@> has joined #yocto15:57
*** dvhart <dvhart!dvhart@nat/intel/x-abfyvawchspneqjp> has joined #yocto16:00
*** belen2 <belen2!Adium@nat/intel/x-zttknlywojhfmlrc> has joined #yocto16:01
*** jonathanmaw <jonathanmaw!> has quit IRC16:02
*** belen <belen!Adium@nat/intel/x-yaigxvrchleblyhy> has quit IRC16:02
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto16:02
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC16:03
*** mrsan <mrsan!> has joined #yocto16:04
*** xerent <xerent!> has joined #yocto16:04
xerenthi, I added a line in the preprocess() block in my image recipe, namely "ln -s /lib/foo ${IMAGE_ROOTFS}/lib/bar", but the link fails to appear in my resulting image. I'm wondering where I can find the log file for this step so I can find out what's gone wrong.16:06
*** bluelightning_ is now known as bluelightning16:06
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC16:08
bluelightningxerent: are you doing anything to ensure the preprocess() function is being called within the recipe?16:08
*** zenx <zenx!~quassel@> has joined #yocto16:09
*** nerdboy <nerdboy!> has joined #yocto16:09
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto16:09
*** tsramos <tsramos!tsramos@nat/intel/x-gtgcqgkddzhnewhe> has joined #yocto16:11
xerentI guess not :)16:12
xerentmaybe IMAGE_PREPROCESS_COMMAND += "preprocess; "16:13
xerentwould be a good idea.16:13
bluelightningright yes that's what I was getting at :)16:13
* xerent hugs bluelightning 16:14
xerenthaving so much fun working overtime to set up a new iMX6 board16:14
*** tsramos <tsramos!tsramos@nat/intel/x-gtgcqgkddzhnewhe> has quit IRC16:15
*** dhirc <dhirc!~dhirc@unaffiliated/dhirc> has quit IRC16:20
*** zenx <zenx!~quassel@> has quit IRC16:22
*** berton <berton!~fabio@> has joined #yocto16:23
*** afxez0r <afxez0r!afxez0r@nat/intel/x-hxdxurcnxenkwpij> has joined #yocto16:23
*** marcin_ <marcin_!c39feabe@gateway/web/freenode/ip.> has quit IRC16:24
*** dhirc <dhirc!~dhirc@unaffiliated/dhirc> has joined #yocto16:25
*** belen2 <belen2!Adium@nat/intel/x-zttknlywojhfmlrc> has quit IRC16:26
*** roccof <roccof!> has quit IRC16:26
*** tsramos <tsramos!tsramos@nat/intel/x-jgbvhixidnabpykk> has joined #yocto16:27
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC16:27
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto16:28
* nerdboy waves at the outgoing shift...16:30
*** tsramos <tsramos!tsramos@nat/intel/x-jgbvhixidnabpykk> has quit IRC16:31
*** belen <belen!Adium@nat/intel/x-lwudxdzhrpkcitjs> has joined #yocto16:31
*** psnsilva <psnsilva!> has joined #yocto16:31
*** sameo_ <sameo_!~samuel@> has quit IRC16:33
*** aj_c <aj_c!Alex_Joya@nat/intel/x-nfoltfeoxitinqbl> has quit IRC16:36
*** psnsilva <psnsilva!> has quit IRC16:37
*** belen2 <belen2!Adium@nat/intel/x-nqmlmmobxjprloie> has joined #yocto16:42
*** belen <belen!Adium@nat/intel/x-lwudxdzhrpkcitjs> has quit IRC16:44
*** jbrianceau is now known as jbrianceau_away16:50
*** sameo_ <sameo_!~samuel@> has joined #yocto16:50
*** psnsilva <psnsilva!> has joined #yocto16:51
*** ftonello <ftonello!~quassel@> has quit IRC16:52
*** belen2 <belen2!Adium@nat/intel/x-nqmlmmobxjprloie> has quit IRC17:01
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC17:01
*** dmoseley <dmoseley!> has quit IRC17:03
*** glfernando <glfernando!~fernando@> has joined #yocto17:06
*** sgw_ <sgw_!> has quit IRC17:09
*** jku <jku!> has quit IRC17:17
*** tsramos <tsramos!tsramos@nat/intel/x-zrjirupxitofmwkd> has joined #yocto17:20
*** hitlin37 <hitlin37!uid16371@gateway/web/> has quit IRC17:22
*** sameo_ <sameo_!~samuel@> has quit IRC17:23
*** sgw_ <sgw_!> has joined #yocto17:23
*** jkridner|work <jkridner|work!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto17:23
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC17:27
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto17:28
*** aehs29 <aehs29!~aehernan@> has left #yocto17:30
*** jkridner|work <jkridner|work!~jkridner@pdpc/supporter/active/jkridner> has quit IRC17:32
*** dreyna4529 <dreyna4529!> has quit IRC17:32
*** jkridner|work <jkridner|work!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto17:32
*** dlerner <dlerner!> has joined #yocto17:32
*** jkridner_ <jkridner_!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto17:34
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC17:35
*** jkridner|work <jkridner|work!~jkridner@pdpc/supporter/active/jkridner> has quit IRC17:37
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto17:39
daleg_alright, I found the source of my problem with yocto bombing while packaging a 4.1.5 kernel17:41
*** dlerner <dlerner!> has left #yocto17:41
daleg_it's an issue with the description in one of the kernel module packages17:41
daleg_"cafe-nand kernel module; NAND flash driver for OLPC CAFÉ chip"17:41
daleg_this gets fed into line 331 of package_deb.bbclass17:42
daleg_ctrlfile.write('%s\n' % unicode(textwrap.fill(description.strip(), width=74, initial_indent=' ', subsequent_indent=' ')))17:42
daleg_unicode() was born without a frontal lobe, so if it's fed a unicode string, it freaks out and kills itself17:43
daleg_THANKS PYTHON17:43
kergoththat would be a recipe with non-ascii in it, didn't you say you took care of that? :)17:44
nerdboythat was the "orinal out of range" failure?17:44
nerdboy*ordinal even17:44
daleg_kergoth: I'm using a recipe-kernel that was generated using the 'yocto-kernel' command17:44
daleg_nerdboy: yep17:44
daleg_so the backstory is this:17:45
daleg_1) I want a 4.1.5 kernel17:45
nerdboythe trac version was a commit message somewhere with a non-ascii char in it17:45
daleg_2) I use 'yocto-kernel' to generate a recipe for that17:45
daleg_3) build bombs with unicode poison sprinkled somewhere in the mix17:45
kergothlesson: bitbake and oe need fixing to not suck with unicode in general17:45
nerdboybitbake is not alone there...17:46
daleg_now, the question is where is this "cafe-nand kernel module; NAND flash driver for OLPC CAFÉ chip" string coming from?17:46
kergothgood question17:46
daleg_kconf in the kernel source?17:46
daleg_time for some recursive greps17:46
nerdboycommit msg? or config description?17:46
daleg_basically what this means, is that there's multiple vectors into the build system that unicode can be injected17:47
daleg_and if that happens... poof17:47
daleg_you lose, good day sir17:47
* nerdboy also loves the random source file with comment block containing some eastern european char and system thinks file is wrong iso type17:48
nerdboytends to also make things blow up strangely17:48
JaMayes, like baník pýčo :)17:49
* nerdboy high-fives JaMa 17:49
nerdboyno funny names in comments please17:49
daleg_you know, this goes back to the golden rule of C compilers: never use unicode in anything ever17:50
daleg_not in comments, at least17:50
kergothdaleg_: that's a definite problem, have you oepned a bug in the yocto bugzilla yet?17:50
kergothprobably should17:50
daleg_kergoth: I plan to, I want to nail down the exact source of this particular issue first so as to have a complete example17:51
kergoththat's admirable17:51
kergothand sadly uncommon17:51
daleg_but the overall theme is: many vectors for unicode to get into The System; and if that happens, good luck17:51
nerdboylike training lockheed engineers to use the PR template?17:51
kergoththat sounds unpleasant17:52
nerdboy1) what happened, 2) which LAN/system...17:52
nerdboyfinally got it into clearquest and they still ignored it17:52
nerdboyPR scrubs were at least "interesting"...17:54
*** realBigfoot <realBigfoot!~realBigfo@> has quit IRC17:56
daleg_ok so who is familiar with the yocto kernel source trees?17:56
daleg_a recursive grep of it found the culprit location:17:56
daleg_./pkgdata/runtime/kernel-module-cafe-nand:DESCRIPTION_kernel-module-cafe-nand: cafe-nand kernel module; NAND flash driver for OLPC CAF\xc3\x89 chip17:56
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC17:56
daleg_so whatever makes the file: pkgdata/runtime/kernel-module-cafe-nand:DESCRIPTION_kernel-module-cafe-nand17:57
daleg_er pkgdata/runtime/kernel-module-cafe-nand17:57
* nerdboy points at OLPC devs17:57
nerdboylooks like their patch...17:57
daleg_maybe they don't enable this module in their kernel defconfig and don't run into this17:58
*** realBigfoot <realBigfoot!~realBigfo@> has joined #yocto17:59
daleg_who knows, this sausage factory is already turning me into a vegetarian17:59
ntllikely drivers/mtd/nand/cafe_nand.c from the kernel source?18:01
ntl * Driver for One Laptop Per Child ‘CAFÉ’ controller, aka Marvell 88ALP0118:01
*** bluelightning <bluelightning!~paul@> has joined #yocto18:01
*** bluelightning <bluelightning!~paul@> has quit IRC18:01
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto18:01
daleg_ok, so basically, who or whatever generates those pkgdata files needs to sanitize the strings and ASCII-ify them first18:02
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto18:02
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC18:02
daleg_or else when Joe Random Kernel Dev spits a new module onto the conveyor belt leading to Torvalds' desk and it has unicode in its description, we're going to have issues18:03
daleg_or, as a short term thing18:05
daleg_we can pass on UnicodeDecodeError exceptions18:05
daleg_because really, do we care?18:05
*** sgw_ <sgw_!> has quit IRC18:08
daleg_or just try not to encode them ever18:09
daleg_because we make a lot of assumptions by even attempting to do it18:09
*** pohly <pohly!> has quit IRC18:09
daleg_whereas if we don't, we're just passing what's there through18:10
kergothwe might want to just blindly pass them on, but it depends on the package manager. rpm doesn't assume anything about the field contents, they're passed as is according to fray, but not sure about debian18:10
daleg_maybe this is a deb requirement. but it's still silly that we assume that the string isn't already utf-8 given how shitty python 2's ability to deal with char encoding is18:11
*** dreyna4529 <dreyna4529!> has joined #yocto18:15
nerdboyum, i would imagine they use it a lot on certain hardware...18:15
nerdboyolpc 1.0 runs off that thing18:16
nerdboyer, boots to nand anyway18:16
*** JaMa <JaMa!> has quit IRC18:17
nerdboyif was going to stuff into my overlay i would probably enforce filtering and spit out one-and-only-one known encoding18:20
nerdboybut that would be a consensus of "1" so not too hard to convince myself...18:20
kergothwe really need to make the transition to python3 and move to using unicode everywhere internally18:20
kergothAny thoughts on whether to keep wireless-tools as well as iw in packagegroup-base? I'm thinking we probably should keep both until we *verify* that every network configuration mechanism can use the latter18:20
* nerdboy votes for python3 and max verification18:21
nerdboythat be one of my "V"'s...18:22
daleg_wow ok18:26
daleg_what do you know18:26
daleg_this fix went in just days ago:18:26
*** paulg <paulg!> has joined #yocto18:26
daleg_I'm cherry-picking this over to my pocky branch and trying it18:27
*** DarkKnight <DarkKnight!> has quit IRC18:28
*** belen <belen!> has joined #yocto18:28
*** DarkKnight <DarkKnight!> has joined #yocto18:29
*** dfaught <dfaught!> has joined #yocto18:30
*** dfaught <dfaught!> has quit IRC18:31
daleg_ok, so to recap - a few days ago a fix for all this debian package unicode crap was committed back to master; I'm a fido user, and missed it. I cherry-picked it over to my fido tree, it works, the world seems ok now18:38
daleg_lessons learned: python char encoding is still the pit of despair it has always been; and check master.18:43
*** vi <vi!86868b4d@gateway/web/freenode/ip.> has joined #yocto18:47
viFetcher failure: Fetch command failed with exit code 4, output:18:47
viis the issue18:47
viwhats the reason ?18:47
kergothyou didn't include the reason18:54
kergothsummarizing or grabbing part of a log doesn't give us enough info to tell you anything18:54
kergothput the log in a pastebin18:54
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/> has quit IRC18:56
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC18:58
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto18:58
*** tsramos <tsramos!tsramos@nat/intel/x-zrjirupxitofmwkd> has quit IRC18:59
*** tsramos <tsramos!~tsramos@> has joined #yocto18:59
nerdboydaleg_: what is your requirement to be on release branch?19:01
nerdboyer, more context maybe...19:01
daleg_being new to yocto, I guess it made sense?19:01
daleg_should I be on master?19:01
viI am making fido 1.8 build19:02
daleg_then what good are the releases then?19:02
viand got error19:02
nerdboystablize on your end as you reach your "target" goal19:02
viWARNING: Failed to fetch URL, attempting MIRRORS if available ERROR: Fetcher failure: Fetch command failed with exit code 4, output: OpenSSL: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure Unable to establish SSL connection.19:02
viERROR: Function failed: Fetcher failure for URL: ''. Unable to fetch URL from any source19:02
daleg_SSLv3 nice19:03
* nerdboy really an outsider, not inner circle19:03
nerdboythey should be stable snapshots pretty much, fixing/adding specific things to that release, also matching docs release19:04
nerdboyyou can't sprint forever...19:04
nerdboyOTOH, stuff is changing fast upstream, kernel/u-boot/runtime19:04
nerdboy"vendors" like freescale migrating off their old forks and pushing stuff up19:05
nerdboycan't capture it all at once19:05
* nerdboy waits for comments/corrections19:06
rburtondaleg_: if you're new to yocto, running off a release branch makes perfect sense19:06
rburtonmaster changes, a lot19:06
vibut I want to use master19:06
nerdboylot of work goes into each one trying to make something release-able19:06
nerdboymaster is usually "safe"19:06
rburtonnerdboy: tell that to the autobuilder ;)19:07
rburtonusually, yeah.  but it's the churn that can be hard to work against19:07
nerdboycould hit build failures anywhere depending on image/machine combo19:07
nerdboyi ain't complainin'...19:07
rburtonevery day your entire platform rebuilds and suddenly the toolchain changes underneath you and your code starts emitting new errors...19:07
nerdboymaster works for me19:07
nerdboythat's normal19:08
daleg_I mean, my OS is currently build using Buildroot right now. I'm exploring Yocto as a replacement for Buildroot because I want to have a dev variant of my OS... so my goal right now is not so much to track Yocto master, but to use a Yocto release (Fido, in my case) to get a OS image that is the same as what I currently have with Buildroot19:08
* nerdboy used to gentoo ~19:08
rburtonnerdboy: depends on how much effort you want to put into tracking oe-core vs how much you want it to just work19:08
nerdboylike i said, works for me19:08
rburtondaleg_: especially if you're new to yocto, use the fido branch19:09
kergothwe use master, but not directly. we use specific revisions, locked on a weekly basis, i update after testing to make sure nothing explodes19:09
nerdboyi choose when i want o pull and/or fix19:09
*** limbrik <limbrik!~textual@> has quit IRC19:09
kergothyeah, fido is good for a stable baseline19:09
nerdboyi can at least keep myself stable for a little while19:09
nerdboythe the medication runs out19:10
nerdboy*then even19:10
*** tsramos <tsramos!~tsramos@> has quit IRC19:11
nerdboydaleg_: for it usually goes like this, every few months or so (or when i get a new something i can build for)19:11
*** tsramos <tsramos!~tsramos@> has joined #yocto19:12
nerdboypull on master, build/fix/pull to get it going, test things on the same (upstream) commit for a while (push/pull from my own repo), spit something out, next19:13
daleg_that's generally what I do with buildroot19:14
nerdboythere ya go19:14
nerdboyi do push back fixes when i have something19:14
nerdboythey seem to tolerate that from me19:15
* nerdboy crashed a couple dev mtgs even19:15
*** r24s <r24s!d0b90c36@gateway/web/freenode/ip.> has quit IRC19:32
*** jkridner_ is now known as jkridner19:37
*** adelcast <adelcast!~adelcast@> has quit IRC19:38
nerdboyotavio: getting a couple of boot errors with console-image-full19:57
nerdboybesides the lockdep error19:57
nerdboyrepeated after first-boot, so i don't think it will fix itself19:58
nerdboy  <=  second boot from latest image build (last commit is a week old i think)20:01
nerdboystill, i guess i expected more trouble, so20:01
nerdboyyou get a cookie20:01
*** belen <belen!> has quit IRC20:09
*** belen1 <belen1!Adium@nat/intel/x-ugmqlppajkqgcqds> has joined #yocto20:19
*** raykinsella78 <raykinsella78!~rkinsell@> has joined #yocto20:20
-YoctoAutoBuilder- build #463 of nightly-ppc-lsb is complete: Success [build successful] Build details are at
* nerdboy waves at belen1 20:23
*** paulg <paulg!> has quit IRC20:23
*** belen1 <belen1!Adium@nat/intel/x-ugmqlppajkqgcqds> has quit IRC20:31
*** raykinsella78 <raykinsella78!~rkinsell@> has quit IRC20:32
*** dreyna_ <dreyna_!> has joined #yocto20:35
*** dreyna4529 <dreyna4529!> has quit IRC20:37
*** paulg <paulg!~paulg@> has joined #yocto20:44
realBigfootmy rootfs is readonly right after building yocto, does anyone know what this could possibly be?20:50
*** raykinsella78 <raykinsella78!~rkinsell@> has joined #yocto20:50
paulgbooted with "ro" on the kernel command line perhaps?20:51
*** Crofton <Crofton!~balister@> has quit IRC20:53
*** ant_home <ant_home!> has joined #yocto20:53
*** radhus <radhus!> has joined #yocto20:56
*** berton <berton!~fabio@> has quit IRC20:58
*** raykinsella78 <raykinsella78!~rkinsell@> has quit IRC21:02
*** nitink <nitink!~nitink@> has joined #yocto21:02
*** sgw_ <sgw_!> has joined #yocto21:10
*** sjolley <sjolley!~sjolley@> has quit IRC21:10
-YoctoAutoBuilder- build #458 of nightly-ipk is complete: Success [build successful] Build details are at
-YoctoAutoBuilder- build #466 of nightly-x32 is complete: Success [build successful] Build details are at
realBigfootpaulg, grub is configured to be ro21:16
paulgwell, there is your answer then.21:18
paulgyou can fix it on the fly temporarily with...21:19
paulgmount -nv -o remount,rw /21:19
paulgthen update grub etc.21:19
*** dreyna4529 <dreyna4529!> has joined #yocto21:19
realBigfootyes I can make it to rw but, shouldn't yocto like make it rw by default?21:20
*** dreyna_ <dreyna_!> has quit IRC21:21
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-brgeoohtouloiqqu> has joined #yocto21:21
*** ljose <ljose!> has joined #yocto21:22
ljoseHi, I enabled libc-backtrace in DISTRO_FEATURES and now glibc fails to build with core-image-minimal21:23
ljosecc1: all warnings being treated as errors21:24
ljose/home/ubuntu/poky/builds/core-image-minimal-beagle/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/glibc/2.21-r0/build-arm-poky-linux-gnueabi/sysd-rules:225: recipe for target '/home/ubuntu/poky/builds/core-image-minimal-beagle/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/glibc/2.21-r0/build-arm-poky-linux-gnueabi/misc/gethostid.o' failed21:24
paulgrealBigfoot, normally  sysV init or systemdisease is responsible for flipping it to rw during bootup.21:38
realBigfootpaulg, I see, i am on systemd maybe i have compiled it with wrong tag?21:38
*** nighty^ <nighty^!> has quit IRC21:39
paulgI've not used systemdisease enough yet to know much of how it operates.  (Not looking forward to it either....)21:39
*** rburton <rburton!> has quit IRC21:39
*** sgw_ <sgw_!> has quit IRC21:40
realBigfootpaulg, ahhaha i see21:40
paulgguess i'll have to someday, seeing as it has taken on the "we are the borg; prepare to be assimilated" approach in deployment everywhere.  :-(21:41
realBigfootpaulg, yeah it looks like everything will have systemd after all21:42
*** DriverCoder <DriverCoder!~mdrustad@> has joined #yocto21:43
* paulg wonders if it spread to android too21:43
khem`ljose: did you build from scratch21:44
realBigfootpaulg, it might21:44
ljosekhem: nope just rebuild a previous image21:45
*** sameo_ <sameo_!~samuel@> has joined #yocto21:45
ljoseBTW, does anybody know if -mapcs-frame is required to get backtraces with ARMv7l21:45
*** ntl <ntl!> has quit IRC21:51
*** DriverCoder <DriverCoder!~mdrustad@> has quit IRC21:52
*** raykinsella78 <raykinsella78!rkinsell@nat/intel/x-brgeoohtouloiqqu> has left #yocto21:54
khem`ljose: now a days it should provided you have compiled right ABI specific unwind tables into glibc as well21:55
khem`in the past it apcs backtrace support was iffy21:55
*** dhirc <dhirc!~dhirc@unaffiliated/dhirc> has quit IRC21:55
khem`and framepointer based was what worked always21:55
ljosekhem`: I using glibc backtrace function and building with -rdynamic but getting bogus stacks21:57
ljoseshould I build with -funwind-tables too?21:58
*** dhirc <dhirc!~dhirc@> has joined #yocto21:59
*** dhirc <dhirc!~dhirc@unaffiliated/dhirc> has joined #yocto21:59
*** fmeerkoetter <fmeerkoetter!> has quit IRC22:01
*** bfederau <bfederau!> has quit IRC22:01
*** sjolley <sjolley!~sjolley@> has joined #yocto22:01
*** fmeerkoetter <fmeerkoetter!> has joined #yocto22:01
*** bfederau <bfederau!> has joined #yocto22:01
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC22:02
*** ntl <ntl!> has joined #yocto22:04
*** sno <sno!> has quit IRC22:06
*** tsramos <tsramos!~tsramos@> has quit IRC22:12
*** tsramos <tsramos!~tsramos@> has joined #yocto22:12
*** tsramos <tsramos!~tsramos@> has quit IRC22:16
*** dvhart <dvhart!dvhart@nat/intel/x-abfyvawchspneqjp> has quit IRC22:19
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC22:26
*** ljose <ljose!> has quit IRC22:30
*** phantoneD <phantoneD!> has joined #yocto22:37
*** jimBaxter <jimBaxter!> has quit IRC22:38
*** jimBaxter <jimBaxter!> has joined #yocto22:39
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto22:39
*** jimBaxter <jimBaxter!> has quit IRC22:39
*** phantoxeD <phantoxeD!> has quit IRC22:41
nerdboydepends on readonlyroot options no?22:42
nerdboyshould be a setting for that now...22:42
-YoctoAutoBuilder- build #472 of nightly-world is complete: Success [build successful] Build details are at
*** phragment <phragment!> has quit IRC22:51
*** ant_home <ant_home!> has quit IRC22:52
*** Crofton <Crofton!~balister@> has joined #yocto22:53
kergoththere is, read-only-rootfs image feature22:54
*** khem` <khem`!~khem@unaffiliated/khem> has quit IRC22:54
* nerdboy needed 3 years ago when stuck on oe-classic22:56
nerdboy*that feature even22:56
nerdboyi kinda hacked it, but it wasn't enough we still had to hack stuff even more...22:57
*** paulg <paulg!~paulg@> has quit IRC22:57
nerdboythose commits were helpful at least22:57
*** ant_home <ant_home!> has joined #yocto23:00
*** Crofton <Crofton!~balister@> has quit IRC23:03
*** staylor <staylor!> has quit IRC23:07
*** dreyna4529 <dreyna4529!> has quit IRC23:08
*** [Sno] <[Sno]!> has joined #yocto23:09
-YoctoAutoBuilder- build #120 of nightly-mips64 is complete: Success [build successful] Build details are at
*** lamego <lamego!lamego@nat/intel/x-ywihlxvukqcfulux> has quit IRC23:11
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto23:14
*** dreyna4529 <dreyna4529!> has joined #yocto23:22
*** jmpdelos <jmpdelos!> has quit IRC23:23
-YoctoAutoBuilder- build #476 of nightly-x86-64 is complete: Success [build successful] Build details are at
*** khem` <khem`!~khem@unaffiliated/khem> has joined #yocto23:36
dhircnerdboy: I am going a little crazy getting this to work. I have has zero luck with the fragments. So tried creating a .config and copied it to meta-ti/recipes-kernel/linux/linux-ti-staging-4.1/defconfig, but with no luck. Is this the correct spot to put a whole config? Really want to try and get this sorted today.. The other thing is, how can I check to see what config bitbake is using before building the whole image?23:38
denixdhirc: config fragments?23:39
dhircdenix: Backstory, trying to enable USB audio on the beagle bone black.23:39
dhircI added my own meta layer with the fragments, but when I check /proc/config.gz they are not changing23:40
*** bongo <bongo!> has joined #yocto23:40
denixdhirc: you can just append your config fragments to KERNEL_CONFIG_FRAGMENTS list23:41
denixdhirc: here's an example -
*** madisox <madisox!> has quit IRC23:41
bongois there a way to share the downloads folder kind of like you can share the shared state?23:42
bongoThe reasoning is so you could do a clean build even if the Internet was down and also to speed up new builds for clients on the same local network23:42
*** paulg <paulg!> has joined #yocto23:42
dhircdenix: This looks promising.. Is there a way to check what config bitbake is working with? I don't want to have to wait for a complete build to check the config is correct. Wasted a lot of time doing this!23:43
denixdhirc: run do_configure and check the resulting .config in build/23:44
dhircdenix: How do you run "do_configure"? I am pretty green23:51
denixdhirc: bitbake virtual/kernel -c configure23:52

Generated by 2.11.0 by Marius Gedminas - find it at!