Thursday, 2014-01-30

-YoctoAutoBuilder- build #5 of nightly-x32 is complete: Success [build successful] Build details are at
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC00:08
*** davest <davest!Adium@nat/intel/x-iebygvttkgdkpltt> has quit IRC00:11
*** sjolley <sjolley!sjolley@nat/intel/x-txwqcvpjwljexkju> has quit IRC00:14
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has quit IRC00:18
*** khem` <khem`!~kraj@> has joined #yocto00:29
*** seebs <seebs!> has quit IRC00:29
khemdenix: whats up00:30
khem`I havent been praying for snow, its my daughter since we went to lake Tahoe last month there was nothing00:31
*** seebs <seebs!> has joined #yocto00:32
denixkhem: finally got to branching off dora in meta-ti, since ${COREBASE}/LICENSE got changed :) almost missed that one while I was on vacation...00:32
khem`I know it would come at some point00:33
khem`but makes distro folks happier00:33
denixkhem: indeed, but since we internally still have active development on dylan for some products, I now have to support 3 branches simultaneously (master, dora, dylan)...00:34
denixI was holding off for as long as I could :)00:34
khem`yeah if you can do that successfully then you are genius since normal folks can maintain 1 branch, smart folks can do 2 and it takes a genius to do 3 :)00:35
khem`master is bleeding why do you support it ;)00:35
denixkhem`: to be current myself and not break stuff for community folks. our products use stable branches of course00:37
*** sameo <sameo!~samuel@> has quit IRC00:55
*** sjolley <sjolley!sjolley@nat/intel/x-kkqruskudrmtvkcp> has joined #yocto01:01
-YoctoAutoBuilder- build #4 of minnow is complete: Success [build successful] Build details are at
*** fray <fray!> has joined #yocto01:04
*** davest <davest!Adium@nat/intel/x-vtpqwocsfcrshwze> has joined #yocto01:05
*** davest1 <davest1!Adium@nat/intel/x-xrtdqzvpbfmdpdvh> has joined #yocto01:09
*** davest <davest!Adium@nat/intel/x-vtpqwocsfcrshwze> has quit IRC01:09
*** davest1 <davest1!Adium@nat/intel/x-xrtdqzvpbfmdpdvh> has quit IRC01:10
*** Garibaldi|work <Garibaldi|work!> has quit IRC01:20
-YoctoAutoBuilder- build #5 of nightly-ppc is complete: Failure [failed Running Sanity Tests] Build details are at
-YoctoAutoBuilder- build #5 of nightly-mips is complete: Failure [failed Running Sanity Tests] Build details are at
-YoctoAutoBuilder- build #5 of nightly-arm is complete: Failure [failed Running Sanity Tests] Build details are at
*** sgw_ <sgw_!~sgw@> has quit IRC01:41
-YoctoAutoBuilder- build #4 of minnow-lsb is complete: Success [build successful] Build details are at
-YoctoAutoBuilder- build #5 of nightly-x86 is complete: Failure [failed Running Sanity Tests] Build details are at
*** sjolley1 <sjolley1!sjolley@nat/intel/x-xxmucaunkbfngqhb> has joined #yocto01:54
*** sjolley <sjolley!sjolley@nat/intel/x-kkqruskudrmtvkcp> has quit IRC01:56
*** mulhern <mulhern!> has joined #yocto01:58
*** mulhern <mulhern!> has quit IRC01:58
*** Net147 <Net147!> has joined #yocto02:00
*** michael_e_brown <michael_e_brown!> has joined #yocto02:03
michael_e_browndoes anybody know the status of python3 in yocto? I've been poking around the repo and don't really see it, although I see some patches to meta-oe mailing list.02:04
*** tm8080 <tm8080!4c11f2de@gateway/web/freenode/ip.> has joined #yocto02:05
*** Jefro <Jefro!> has quit IRC02:05
khem`michael_e_brown: Patches are there see my contrib tree02:10
khem`its on top of master but should work ok on dora too02:11
michael_e_brownah. thanks. I'm on dora and was considering moving over to master to get py302:11
michael_e_brownany plans on getting that into poky, or is there a timeline for conversion?02:12
*** tm8080 is now known as tpmanley02:14
-YoctoAutoBuilder- build #5 of nightly-fsl-arm is complete: Success [build successful] Build details are at
khem`michael_e_brown: it should go into Oe-Core/master sometime02:18
khem`there are some cosmetic issues with it02:18
khem`I have it working with dylan/dora/master02:18
*** tpmanley <tpmanley!4c11f2de@gateway/web/freenode/ip.> has left #yocto02:20
*** ScriptRipper <ScriptRipper!~ScriptRip@opensuse/member/MartinMohring> has quit IRC02:22
*** ScriptRipper <ScriptRipper!~ScriptRip@opensuse/member/MartinMohring> has joined #yocto02:26
vmesonmichael_e_brown: see
michael_e_brownThanks for the reference!02:29
khem`yes since these files are same as they are trying to replace02:33
khem`so functionally it does not matter02:33
*** nitink <nitink!~nitink@> has joined #yocto02:42
*** nitink1 <nitink1!~nitink@> has quit IRC02:43
*** nitink <nitink!~nitink@> has quit IRC02:47
*** silviof3 <silviof3!> has joined #yocto03:01
*** silviof2 <silviof2!> has quit IRC03:04
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto03:16
*** behanw <behanw!~behanw@> has quit IRC03:53
*** Jefro <Jefro!> has joined #yocto03:56
*** sgw_ <sgw_!~sgw@> has joined #yocto03:57
*** sgw_1 <sgw_1!> has joined #yocto04:00
*** sgw_ <sgw_!~sgw@> has quit IRC04:03
*** behanw <behanw!> has joined #yocto04:13
*** behanw <behanw!> has quit IRC04:22
*** tobiash <tobiash!> has joined #yocto04:32
-YoctoAutoBuilder- build #5 of nightly-fsl-arm-lsb is complete: Success [build successful] Build details are at
-YoctoAutoBuilder- build #4 of eclipse-plugin-kepler is complete: Failure [failed] Build details are at
michael_e_brownkhem, you still around?04:38
khem`I just rebased the python3 branch04:39
michael_e_brownI added the openembedded-core-contrib  kraj/python3  branch04:39
khem`I also fixed the warnings04:39
michael_e_brownand without changing anything I got:04:39
michael_e_brownERROR: ExpansionError during parsing /home/michael_e_brown/cp-2/build/qemu/release-xrev/../../../openembedded-core-contrib/meta/recipes-devtools/python/ Failure expanding variable DEPENDS: ExpansionError: Failure expanding variable DEPENDS, expression was  virtual/x86_64-poky-linux-gcc virtual/x86_64-poky-linux-compilerlibs virtual/libc   python3 ${@["${PYTHON_PN}-native ${PYTHON_PN}", "04:39
michael_e_brown"][(d.getVar('PACKAGES', True) == '')]}  ${PYTHON_PN}-native  which triggered exception SyntaxError: EOL while scanning string literal (DEPENDS, line 1)04:39
michael_e_brownDo I need to update any config? I was just adding that layer to my existing dora build to make sure everything still compiles before switching over to python304:40
khem`hmm did you cherry-pick the patches04:40
khem`or how did you do it04:40
michael_e_brownjust added the whole layer... maybe I screwed something up, but it seemed straightforward04:40
khem`you said you were on poky or some sort04:41
michael_e_brownI checked out the kraj/python3 branch and added it to my bblayers04:41
michael_e_brownpoky, dora branch04:41
khem`well poky does not take OE-Core as such it fudges it into a layer of its own04:41
khem`so your best approach is to cherry-pick04:42
khem`I just posted the series to ml04:42
khem`as well04:42
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC04:42
michael_e_brownOk. little bit more work. I'll check it out.04:42
khem`so you can just 1 by 1 on dora/poky04:42
khem`you will get a conflict on [15/15] python-setuptools: Remove its provided by python-distribute04:43
khem`thats because dora has a different version of python-setuptools_1.4.bb04:43
khem`that its removing04:43
khem`so you can solve that manually04:43
khem`other 14 should apply straight forward04:44
michael_e_brownok. all new stuff to me, but it looks straightforward.04:44
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto04:44
michael_e_brownthanks for the direction and pointers04:44
khem`let me know how it goes04:45
khem`you will provide testing to them04:45
khem`so reply to mailing thread with your results04:45
michael_e_brownany plan to get this into yocto 1.6? Or is there a target for it?04:45
khem`yes I 1.6 should get it04:46
khem`hopefully this is last iteration04:46
michael_e_brownok. I'll apply and send a note when I get it.04:46
*** Jefro <Jefro!> has quit IRC04:47
-YoctoAutoBuilder- build #4 of nightly-oecore is complete: Failure [failed Running Sanity Tests] Build details are at
-YoctoAutoBuilder- build #4 of build-appliance is complete: Failure [failed BuildImages_1 Publishing Artifacts] Build details are at
michael_e_brownkhem, second patch in the series fails for some weird reason:04:59
michael_e_brown$ ./  6605904:59
michael_e_brown+ for patchnumber in '$@'04:59
michael_e_brown+ wget -nv -O pw-am-66059.patch04:59
michael_e_brown2014-01-29 22:58:13 URL: [20974] -> "pw-am-66059.patch" [1]04:59
michael_e_brown+ git am -s pw-am-66059.patch04:59
michael_e_brownApplying: python-3.3-manifest: Add python3 manifest file04:59
michael_e_brown/home/michael_e_brown/cp-2/poky/.git/rebase-apply/patch:19: trailing whitespace.04:59
michael_e_brownfatal: corrupt patch at line 27404:59
michael_e_brownPatch failed at 0001 python-3.3-manifest: Add python3 manifest file04:59
michael_e_brownWhen you have resolved this problem run "git am --resolved".04:59
michael_e_brownIf you would prefer to skip this patch, instead run "git am --skip".04:59
khemah yes04:59
michael_e_brownTo restore the original branch and stop patching run "git am --abort".04:59
michael_e_brownand... looking at the patch, something is off:04:59
khemit has a line which is longer than 998 chars04:59
khemwhich emails cant handle05:00 is split05:00
michael_e_brownI tried to fix it, but I failed somehow05:00
khemclone oe-core-contrib05:00
khemcheckout kraj/python3 branch05:00
khemand generate the patches05:00
michael_e_brownI can do that.05:00
khemgit format-patch -1505:00
khemand then git am them in your poky tree05:01
michael_e_browneasy enough. let me reclone my tree since you said you rebased everything05:01
*** sjolley <sjolley!sjolley@nat/intel/x-eijkdqpfeopubyit> has joined #yocto05:04
*** sjolley1 <sjolley1!sjolley@nat/intel/x-xxmucaunkbfngqhb> has quit IRC05:05
*** behanw <behanw!> has joined #yocto05:06
*** denix <denix!> has quit IRC05:10
khem`btw. in angstrom I already have it working with dora05:12
michael_e_brownthanks. git am is progressing. halfway there.05:15
michael_e_brownthere are some trailing whitespace warnings, btw05:15
*** Jefro <Jefro!> has joined #yocto05:19
*** e8johan <e8johan!> has joined #yocto05:22
*** behanw <behanw!> has quit IRC05:27
* mranostay yawns05:45
*** SorenHolm <SorenHolm!> has joined #yocto06:06
*** SorenHolm <SorenHolm!> has quit IRC06:13
*** Jefro <Jefro!> has quit IRC06:25
*** GusBricker <GusBricker!> has quit IRC06:29
*** GusBricker <GusBricker!> has joined #yocto06:30
*** sjolley <sjolley!sjolley@nat/intel/x-eijkdqpfeopubyit> has quit IRC06:32
*** sjolley <sjolley!~sjolley@> has joined #yocto06:34
*** GusBricker <GusBricker!> has quit IRC06:35
*** sjolley <sjolley!~sjolley@> has quit IRC06:35
*** Jefro <Jefro!> has joined #yocto06:44
*** Jefro <Jefro!> has quit IRC06:50
*** khem` <khem`!~kraj@> has quit IRC06:55
*** khem` <khem`!> has joined #yocto06:55
*** mihai <mihai!~mihai@> has joined #yocto06:58
*** kbart <kbart!~KBart@> has joined #yocto07:01
michael_e_brownkhem, got interrupted with girlfriend issues, but I finally got everything applied, and rebuilding same exact image (no python3, still python2) WORKS GREAT, NO PROBLEMS. Next step, I will pull in python3 to see how that works.07:03
*** reallife <reallife!> has quit IRC07:05
*** reallife <reallife!> has joined #yocto07:05
khem`there are plenty of other recipes for python universe that I havent contributed07:06
khem`essentially things like jinja sphinx pyzmq and stuff07:06
khem`once OE-Core patches go in then I will propose them for meta-oe07:06
*** g1zer0 <g1zer0!> has joined #yocto07:07
michael_e_brownkhem, adding python3 fails to build:07:09
michael_e_brownERROR: This autoconf log indicates errors, it looked at host include and/or library paths while determining system capabilities.07:09
michael_e_brownRerun configure task after fixing this. The path was '/home/michael_e_brown/cp-2/build/qemu/release-xrev/tmp/work/x86_64-poky-linux/python3/3.3.3-r0.0/Python-3.3.3'07:09
michael_e_brownERROR: Function failed: do_qa_configure07:09
michael_e_brownERROR: Logfile of failure stored in: /home/michael_e_brown/cp-2/build/qemu/release-xrev/tmp/work/x86_64-poky-linux/python3/3.3.3-r0.0/temp/log.do_configure.1008507:09
michael_e_brownERROR: Task 461 (/home/michael_e_brown/cp-2/build/qemu/release-xrev/../../../poky/meta/recipes-devtools/python/, do_configure) failed with exit code '1'07:09
michael_e_brownNOTE: Tasks Summary: Attempted 3060 tasks of which 3044 didn't need to be rerun and 1 failed.07:09
michael_e_brownNo currently running tasks (3060 of 3070)07:09
michael_e_brownSummary: 1 task failed:07:09
michael_e_brown  /home/michael_e_brown/cp-2/build/qemu/release-xrev/../../../poky/meta/recipes-devtools/python/, do_configure07:09
michael_e_brownSummary: There were 2 ERROR messages shown, returning a non-zero exit code.07:09
michael_e_brownlet me look in the log file to see what I can see07:09
michael_e_browncc1: warning: include location "/usr/include/ncursesw" is unsafe for cross-compilation [-Wpoison-system-directories]07:12
michael_e_brownIt looks like, line 4311:07:13
michael_e_brownCPPFLAGS="$CPPFLAGS -I/usr/include/ncursesw"07:14
khem`michael_e_brown: I bet I fixed it once07:18
khem`whats your build OS07:18
michael_e_brownI am on centos 607:18
michael_e_brownit looks like a clear problem in the stock python configure.ac07:18
khem`if you have possibility can you uninstall ncursesw07:19
khem`on it07:19
khem`yes I know07:19
khem`the problem is in python07:19
michael_e_brownlooks like it should be using pkg-config07:19
michael_e_brownthis is a shared build machine... slightly difficult to uninstall07:20
khem`btw. you might also want something like
khem`hmm ok07:20
michael_e_brownoh, thanks. that packagegroup looks lovely.07:21
michael_e_brownI'm going to get yelled at tomorrow, but I uninstalled curses devel and everything it depends on and it's compiling now. We ought to patch that to use PKG_CHECK_MODULES()07:22
michael_e_brownoh, wait, HPUX probably isnt doing pkg-config07:22
michael_e_brownWell, I know how *I* would fix this. How would you fix this for the 'official' python3 package? (just curious)07:23
khem`OK cooking a patch hang on07:24
*** swex <swex!~swex@> has quit IRC07:26
michael_e_brownAnother "issue" (may or may not be real, since I'm just starting to move some stuff to python3): python3-fcntl package is empty.07:27
*** agust <agust!> has joined #yocto07:28
michael_e_brown$ find .  | grep fcntl07:28
michael_e_brown[michael_e_brown@gitbuild12g106 Python-3.3.3]$ cd ../packages-split/07:28
michael_e_brown[michael_e_brown@gitbuild12g106 packages-split]$ find python3-fcntl/07:28
michael_e_brownIt looks like there is an fcntlmodule.o, but it doesn't end up in python3-fcntl, nor do I see it anywhere else.07:28
michael_e_brownAh, looks legit:07:31
michael_e_brown| Collected errors:07:31
michael_e_brown|  * satisfy_dependencies_for: Cannot satisfy the following dependencies for python3-subprocess:07:31
michael_e_brown|  * python3-fcntl *07:31
michael_e_brown|  * opkg_install_cmd: Cannot install package python3-subprocess.07:31
michael_e_brownso there is another problem to fix, khem.07:31
khem`OK I pushed a patch to contrib branch07:32
khem`git pull and cherry pick it07:32
michael_e_brownLooks like needs an update:07:32
michael_e_brownFILES_${PN}-fcntl="${libdir}/python3.3/lib-dynload/fcntl.*.so "07:32
michael_e_brownshould be fcntlmodule*.so07:33
michael_e_brownor just fcntl*.so07:33
khem`let me see if I can reproduce the second problem07:36
michael_e_brownkhem, could you check what you just committed? It appears that you:07:36
michael_e_brown+            file://avoid-ncursesw-include-path.patch \07:36
michael_e_brownbut did not git add the actual patch file07:36
*** SorenHolm <SorenHolm!> has joined #yocto07:37
michael_e_brownFor the fcntl one, maybe python isnt installing it?07:37
michael_e_brown$ find image/ | grep fcntl07:37
michael_e_brownI'm not seeing the built installed07:37
*** diego_r <diego_r!> has joined #yocto07:38
khem`OK repushed07:38
michael_e_browncool. I learned a new trick. thanks. "="07:42
michael_e_brownre-installed the offending ncurses-devel and it got past do_configure07:43
michael_e_brownnow on do_compile07:43
*** ant_work <ant_work!> has joined #yocto07:44
michael_e_brownbuild successful07:45
khem` is the module07:45
khem`that it should build07:45
khem`few years ago I fixed it for python 207:46
khem`it might need similar stuff with p307:46
*** ant___ <ant___!> has joined #yocto07:56
*** ant___ <ant___!> has quit IRC07:57
*** e8johan_ <e8johan_!> has joined #yocto07:58
*** e8johan <e8johan!> has quit IRC07:59
khem`OK I think I know the problem07:59
khem`trying out a potential fix07:59
*** ant_work <ant_work!> has quit IRC07:59
michael_e_brownok, good, because I have been looking at it and have no idea what's going on.08:00
*** zecke <zecke!> has joined #yocto08:03
*** fpaut_ is now known as fpaut08:05
*** eballetbo <eballetbo!> has joined #yocto08:14
khem`its a chicken egg problem08:16
khem`where mods need libpython to be staged08:17
khem`so compile step needs to be divided08:17
khem`hopefully that will fix it08:17
michael_e_brownok, thanks for looking. bedtime for me.08:17
michael_e_brownI'll pull and test tomorrow if you have something pushed08:18
*** ant_work <ant_work!> has joined #yocto08:21
*** aragua <aragua!> has joined #yocto08:26
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto08:32
*** florian_kc is now known as florian08:33
*** tasslehoff <tasslehoff!~tasslehof@> has joined #yocto08:36
*** zeeblex <zeeblex!~apalalax@> has joined #yocto08:37
*** arky <arky!> has joined #yocto08:44
*** arky <arky!> has left #yocto08:53
*** fray <fray!> has quit IRC09:00
*** jonatan <jonatan!> has quit IRC09:01
*** beaver_545 <beaver_545!~stuart@> has joined #yocto09:03
*** sameo <sameo!~samuel@> has joined #yocto09:05
g1zer0hi! how do I trigger updating a package feed manifest (Packages*) after bitbaking a previously unused recipe?09:09
g1zer0I mean... 'bitbake gdb' does put ipks in deploy/ipk dir, but the Packages* files don't seem to be updated09:10
g1zer0working with yocto dora09:10
Net147g1zer0: bitbake package-index09:10
*** JimBaxter <JimBaxter!> has joined #yocto09:12
g1zer0Net147: thx... i definitely missed the right keyword to search the docs... ;-)09:13
g1zer0Net147: it works as expected!09:14
*** mckoan|away is now known as mckoan09:20
mckoangood morning09:20
*** Net147 <Net147!> has quit IRC09:30
*** zeeblex1 <zeeblex1!~apalalax@> has joined #yocto09:34
*** zeeblex <zeeblex!~apalalax@> has quit IRC09:34
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto09:37
TuTizzMorning every one,09:37
TuTizzI want to create the following custom filesystem /boot (ext3 unmount) / (ubifs ro) /home (ext3 + ecryptfs) /update (ext3 unmount) /update-1 (ext3 unmount), can someone help me please?09:37
TuTizzI found IMAGE_FSTYPES = "ubifs" but that create the entire image, what should I do?09:37
TuTizzWhere should I specify this options?09:37
bluelightningmorning all09:39
bluelightningTuTizz: we don't have built-in support for creating custom partition layouts, but we do have a work-in-progress tool called "wic" for doing that09:40
TuTizzok will take a look09:41
*** khem` <khem`!> has quit IRC09:42
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto09:52
*** belen <belen!Adium@nat/intel/x-vlzhcmrwqlinbjub> has joined #yocto09:55
*** dany <dany!> has quit IRC10:13
lpapprburton: hi, do you know how the image gets the information which distribution to use?10:15
rburtonbitbake reads the DISTRO on parse, which leads to the distro configuration files being read10:15
rburtonso when the image is being built, bitbake has loaded the distro configuration10:16
lpapprburton: ah, ok, and the DISTRO comes from e.g. local config, or the image conf itself, etc.10:16
lpappimage config = image recipe.10:17
rburtonyou wouldnt put DISTRO= into an image recipe10:17
rburtonyou'd put it in a local.conf or site.conf normally10:18
lpappsite.conf, that is, when you work with developers on the same thing.10:18
rburtonbitbake doesn't care what you do with local.conf or site.conf, it just loads both with the intention that one is site-specific and the other is yours.10:19
lpapprburton: why do I see the DISTRO variable set in distro configs?10:19
lpappit should be set by the user of the distro, yes?10:19
lpappor is that for making the name different from the file name?10:20
rburtonwhere do you see DISTRO set in a distro config?10:20
lpapprburton: ../meta-yocto/conf/distro/poky.conf:1:DISTRO = "poky"10:21
lpapp../meta-yocto/conf/distro/poky-tiny.conf:32:DISTRO = "poky-tiny"10:21
lpappthose deserve a patch, or?10:21
rburtonpatch, no, that's there for a reason. i just don't know what it is.10:22
lpapprburton: who may know?10:22
lpappmy assumption is decoupling the file name for the distro name for customization.10:22
bluelightningthere can be no decoupling10:22
bluelightningthe distro conf is included by looking for conf/distro/${DISTRO}.conf10:23
bluelightningsee bitbake.conf where that is done10:23
*** oneQubit <oneQubit!> has quit IRC10:25
lpapprburton: hmm, that documentation mentions that it should be used from outside the distro config, and then it gives an example when it is used inside. It is a bit incomprehensive for me, I am afraid.10:26
lpappbluelightning: then what is the use of it inside the distro config?10:26
bluelightningdon't know either10:27
bluelightningit ought to be superfluous10:27
lpappOK, I will ask on the mailing list.10:27
lpapprburton: I will remove it in my distro conf, if that is safe?10:30
lpappI just mimiced poky. :-)10:31
lpappoops, the poky mailing list subscription is broken for me.10:32
rburtonlpapp: not sure, might be there for a reason10:32
*** beaver_545 <beaver_545!~stuart@> has quit IRC10:33
av500an "old" reason maybe10:34
g1zer0Hi all! I'm facing this problem while porting a bsp layer from dylan to dora. I can successfully build both kernel and user space. Kernel (3.10) starts smoothly but the user space is broken. This is a bsp for a pretty prehistoric i486sx target. Everything was working fine with latest dylan. During boot, many userspace processes (udevd, connmand, ecc..) get killed by SIGILL. What I came up with after some investigation mak10:36
g1zer0es me suspect something went wrong while building eglibc. Btw: not everything is broken in userspace; i.e. dropbear works and I can connect to the target. I even can debug on target with gdb. I'm not guru-ish enough to figure out what went wrong... Here is a bt from gdb when running one of the failing processes:10:36
g1zer0Program received signal SIGILL, Illegal instruction.10:36
g1zer00x48f40ca4 in __init_cpu_features () at ../sysdeps/x86_64/multiarch/init-arch.c:5210:36
g1zer052  __cpuid (0, __cpu_features.max_cpuid, ebx, ecx, edx);10:36
g1zer0(gdb) bt10:36
g1zer0#0  0x48f40ca4 in __init_cpu_features () at ../sysdeps/x86_64/multiarch/init-arch.c:5210:36
g1zer0#1  0x48f40f2b in __get_cpu_features () at ../sysdeps/x86_64/multiarch/init-arch.c:19110:36
g1zer0#2  0x48f40f54 in elision_init (argc=1, argv=0xbffffdd4, environ=0xbffffddc)10:36
g1zer0    at ../nptl/sysdeps/unix/sysv/linux/x86/elision-conf.c:6510:36
g1zer0#3  0x48d953d6 in call_init (l=<optimized out>, argc=1, argv=argv@entry=0xbffffdd4, env=env@entry=0xbffffddc)10:36
g1zer0    at dl-init.c:8410:36
g1zer0#4  0x48d9550b in call_init (env=0xbffffddc, argv=0xbffffdd4, argc=1, l=<optimized out>) at dl-init.c:3610:36
g1zer0#5  _dl_init (main_map=0x48da8928, argc=1, argv=0xbffffdd4, env=0xbffffddc) at dl-init.c:9910:36
g1zer0#6  0x48d86d3f in _dl_start_user () from /lib/
g1zer0that x86_64 sounds suspicious to me...10:36
lpapprburton: ok, will just ask then after some local git history digging10:40
lpappav500: you are old, accept it. ;-)10:40
av500I do, kid, I do10:41
lpapprburton: RP added it in 2005. :D10:41
Xzhi guys, looking for firmware called 'iwlwifi-5000-x.ucode'10:44
Xzdo I find it anywhere in Yocto?10:44
Xzapparently poky/ and meta-intel/ don't support that one10:44
RPXz: isn't it part if linux-firmware?10:44
bluelightningXz: is it part of the upstream linux firmware repo?10:44
RPlpapp: I think those names were hardcoded so that overrides worked correctly, even when you use the distro files from local includes that overide them. Its more of a hardcoded sanity check10:45
XzRP: as per linux-firmware recipe I don't see support for that10:46
bluelightningXz: it's possible that it isn't explicitly split out10:46
XzRP: bluelightning: chip is called Intel WiFi LINK 510010:46
XzRP: bluelightning: so if I install whole linux-firmware it will just be there? iwlwifi supports that10:47
bluelightningXz: you can do that, or you can modify the linux-firmware recipe to split it out10:47
RPXz: I'd see if that file is part of that recipe. We can always split it out10:47
lpappRP: can you mention a scenario when it would not work without it?10:48
RPlpapp: where you include the poky distro from some other local settings file by using a different DISTRO setting?10:49
lpappRP: what exactly wouldn't work them? Can you give an expected and actual output?10:50
RPlpapp: the expected output would be the poky overrides being applied. The actual output without that is that the overrides do not get applied10:50
RPlpapp: what exactly is causing you a problem with these?10:51
*** beaver_545 <beaver_545!~stuart@> has joined #yocto10:53
*** dany <dany!> has joined #yocto10:53
lpappRP: "by using a different DISTRO setting?" => you mean before or after the include?10:54
lpappRP: my assumption is before.10:56
RPlpapp: before11:01
lpappRP: then I do not follow.11:01
lpappRP: IMO, this needs a rethrought, currently if you include it after, it goes on even though the end user may have wanted to include it after11:02
lpappso it is silently goes further on rather than a warning.11:02
RPlpapp: distroA.conf requires poky.conf, you'd use DISTRO = "distroA" but it would subclass poky and end up looking like poky. This is how distro inheritance used to work11:03
lpapppoky + your extension.11:03
lpappin your distroA.11:03
lpappwhat is the problem in there?11:03
RPlpapp: there is no problem, I'm trying to explain why the metadata is the way it is which I believe is what you asked?11:04
XzI moved to /dev/shm and observing strange problems: chown: changing ownership of `/dev/shm/tmp/work/i586-poky-linux-uclibc/gcc-runtime/4.7.2-r20/image/usr': Operation not permitted11:04
Xzhave you ever seen it?11:04
XzYocto fails on 'chown'11:05
XzI think it has something to do with pseudo11:05
bluelightningXz: er, I don't think you should be using /dev/shm itself as TMPDIR11:05
Xzbluelightning: why not?11:05
bluelightningXz: by all means, mount your own tmpfs and use that, but /dev/shm has a specific purpose11:05
Xzbluelightning: I have no root on that machine :(11:06
Xzbluelightning: and it has 132GB memory11:07
bluelightningXz: ask whoever has root to set you up a ramdisk then ;)11:07
lpappRP: yes, but it must solve some issue, but I do not see what issue yet.11:07
*** fray <fray!> has joined #yocto11:07
Xzbluelightning: ok, I can sort it out in background11:07
Xzbluelightning: but I don't think it will solve my chown problem11:07
lpapp1) foo.conf -> requires poky.conf11:07
lpapp2) You use DISTRO = "foo"11:07
lpappThe end user will build based on foo as expected.11:08
RPlpapp: The value of DISTRO is used in OVERRIDES11:08
lpappit is an internal detail that foo is utilizing poky internally.11:08
RPand often you'd want poky in there rather than foo11:08
lpappRP: why?11:08
RPlpapp: so the poky distro overrides get used11:08
RPwe now have DISTROOVERRIDES so the world has changed since 2005 but the principle still stands11:09
lpappRP: if I use distro "foo" I expect DISTRO="foo" to be applied, not DISTRO="poky".11:10
RPlpapp: You might expect that, others do not11:10
lpappfor me, it does not matter if my interface "foo" replaces "poky" internally one day for something else.11:10
Xzapparently I'm not the only one with 'chown' problem11:10
lpappRP: why would they expect it differently?11:10
lpapptheir interface is "foo", and the internals are just internals.11:11
RPlpapp: by including the poky distro, they likely want all of the "policy" associated with that distro which includes its overrides11:11
lpappRP: or may not...11:13
RPlpapp: This is the expected behaviour, I'm telling you that, not debating it11:13
lpappit feels a bit like this inheritance method is not yet polished.11:13
*** mulhern <mulhern!> has joined #yocto11:13
lpappwell, I would expect it different as the author of foo.11:13
*** mulhern <mulhern!> has quit IRC11:14
* RP shrugs11:14
bluelightninglpapp: RP asked you a question earlier - are you trying to solve an actual problem that you are experiencing here?11:14
rburtonas the author of foo, why would you inherit the poky distro if you didn't want poky's behaviour?11:14
* zecke is happy to have his ignore list. :)11:14
lpappbluelightning: yes, cleaning up potentially unneeded things.11:15
bluelightninglpapp: so, no then...11:15
lpappso yes....11:15
lpappwell, I accept that "dummy" stuff are there without knowledge is not an issue for you... but it certainly is for me as the maintainer of the thing.11:16
bluelightningyou'll not save any kind of space, build time, etc. by fiddling with this, and you're not actually experiencing any kind of build failure as a result11:16
lpapphow do you *really* know I do not face an issue due to this any soon?11:16
lpappas a maintainer I *would* like to understand what is going on.11:16
lpappabout the software I need to supervise.11:16
bluelightningbecause we asked and you didn't answer in the affirmative?11:16
lpapp"do not try to prevent issues, fix it once you spend enough time with debugging it"11:17
lpappthat is not my maintainer mentality, but I accept if others see the world differently.11:17
lpapp(but this is my software after all... and I will certainly drop that definition in my distro conf respectively)11:18
lpappthis setting would make it impossible to use DISTRO in foo.11:20
lpapp1) You use it before the requires, it is void11:20
lpapp2) If you use it after, it will not work for the poky bits.11:20
lpappMy opinion is that the inheritance for distros is currently broken... IMHO, it is a valid use case to take advantage both layers, but currently you cannot.11:20
RPlpapp: its not impossible to use DISTRO in foo, you can simply make an assignment after the include11:20
lpappRP: no, you wrote that then the poky bits will not get applied.11:21
RPlpapp: you could add poky to DISTROOVERRIDES at the same time if that is what you wish11:21
lpappRP: If I am writing a foo layer depending on poky, I would like to utilize both layer features.11:22
RPlpapp: there are a ton of different ways this can be setup. We've chosen to leave this setup the way it originally started because people have relied on that behaviour for the past 9 years and there is no pressing reason to change that11:22
RPI agree that if we sat down today we might do some things differently. That isn't a luxury we have11:22
lpappRP: OK, so you admit that it is not the best, but you prefer compatibility.11:24
lpapphmm, I do not see the logs here for 2014:
RPlpapp: I think any of the people who've worked on OE for a while will agree there are places where things are suboptimal however yes, we try and have some compatibility11:26
lpappRP: OK, that I can accept, but comments like "* zecke is happy to have his ignore list. :)" for a different technical opinion is go a bit far...11:26
RPlpapp: where there is a pressing need for a change, we can  and have made changes but we try and reserve those changes for the places we really need them11:26
RPlpapp: that is his choice11:27
lpappOK, thanks for sharing your opinion. Now, at least, I understand the reason.11:27
lpappRP: sure, and I do not mind, but providing such negative comments in public is not healthy IMHO.11:27
lpapp(but let us get over that)11:27
TuTizzI have an error with sysroot_stage_all_append, is this name changed?11:34
*** belen1 <belen1!Adium@nat/intel/x-immaubovmdnczvwe> has joined #yocto11:34
RPTuTizz: in the kernel?11:36
RPwell, in a kernel recipe?11:36
RPTuTizz: it changed from a shell to a python function11:36
*** belen <belen!Adium@nat/intel/x-vlzhcmrwqlinbjub> has quit IRC11:37
RPTuTizz: you're probably appending shell to a python function and its getting confused11:37
TuTizzyep this is it, thanks11:38
lpappwhat is a better way than deleting the ./tmp/deploy/images/* files myself before creating an imagE?11:38
lpappI think -c clean did not work for me.11:39
*** daiane <daiane!> has quit IRC11:40
*** daiane <daiane!> has joined #yocto11:41
lpappyeah, bitbake -c clean myimage does not clean that folder up.11:41
*** belen <belen!~Adium@> has joined #yocto11:44
*** belen1 <belen1!Adium@nat/intel/x-immaubovmdnczvwe> has quit IRC11:47
lpapp"README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt" -> perhaps, that file could document how to clean that folder up then?11:48
jackmitchellI think the best way to handle that directory would be a script, similar to the sstate management scripts11:50
bluelightningthere is RM_OLD_IMAGES11:50
lpappmy wish as a user is that it is simpler to copy files from there.11:51
lpapp(if I do not need to check the timestamp, etc, manually)11:51
bluelightninger RM_OLD_IMAGE, that is11:51
lpappand I have a cleaner feeling if only the latest is held in there.11:51
bluelightningthat is exactly what that variable does if set to 111:51
lpappbluelightning: oh, sounds like a local.conf material?11:52
bluelightningit's not in dylan though11:52
bluelightningwas introduced in dora11:52
lpappright, thanks anyway11:52
lpappwell, one thing comes up while looking up its documentation...11:53
lpapp1) Open
lpapp2) Ctrl-f: RM_OLD_IMAGE11:53
lpapp3) Go there11:53
lpapp4) I cannot see any option for the "perma link".11:53
lpapphow can I easily share it then with others?11:53
rburtonyeah, we need a way to get permalinks for everything11:53
rburtonyou can guess the link target though11:53
bluelightningwell, there is a way11:53
lpappthe workarounds have been:11:54
lpapp1) Guesses11:54
lpapp2) Get a link to an existing based on a link.11:54
lpapp(and modify that), but it is suboptimal...11:54
lpappis there a bug tracking this wish?11:54
*** Net147 <Net147!> has joined #yocto11:55
RPXz: It appears there are iwlwifi-5000-*.ucode files in linux-firmware fwiw11:56
*** dguthrie_ <dguthrie_!> has joined #yocto11:58
Xzbluelightning: I solved my chown problem - /dev/shm/mydir must belong to the group I belong to12:00
*** belen1 <belen1!Adium@nat/intel/x-ztruifyilwqdcbfi> has joined #yocto12:00
Xzbluelightning: RP: shouldn't something like that be in README? that directory you build yocto in must belong to the same group as user building?12:01
*** belen <belen!~Adium@> has quit IRC12:01
dguthrie_I am trying to build a package with depends on perl-native. But when the configure script for the package runs it can't find /usr/bin/perl. Why does perl-native install the perl binary to ${sysroot}/usr/bin/nativeperl12:01
Xzbluelightning: RP: otherwise pseudo and chown complain about 'Operation not permited'12:01
RPXz: I'd never realised that was an issue. We should add a check to sanity.bbclass12:01
bluelightningdguthrie_: your recipe should "inherit perlnative"12:02
RPdguthrie_: did you inherit the perlnative class?12:02
lpappif I delete the ./tmp/deploy/images myself, bitbake u-boot does not repopulate that folder with the u-boot binary.12:02
RPdguthrie_: if not, take a look at it and you'll understand why12:02
bluelightningdguthrie_: the reason is, we don't want races between the host's perl and our own built version12:02
lpappwhat could be the reason for that?12:02
dguthrie_ok thanks, will inherit from perlnative12:03
bluelightninglpapp: because the stamp file exists telling the build system it doesn't need to deploy it again12:03
RPlpapp: bitbake doesn't track the files in there so it has no idea you deleted it. This is what the README you mentioned earlier warns about12:03
bluelightninglpapp: this is *exactly* why that README_ file is there...12:03
lpappbluelightning: but strangely enough, bitbake myimage repopulates that folder12:03
lpappbluelightning: nope12:03
lpappthe image works just fine.12:03
bluelightninglpapp: yep12:03
lpappbitbake myimage will repopulate it, but bitbake u-boot will not.12:03
RPlpapp: images are always rebuilt, kernels and uboot come from deploy tasks which don't rebuild every time12:04
bluelightningRP: well, in dylan they were12:04
rburtondora is "fixed" in that it won't re-deploy if nothing has changed, right?12:04
lpappRP: there is no need to rebuild, just redeploy.12:04
lpappI am using dylan.12:04
RPrburton: correct12:05
RPrburton: wemade images use the full sstate checksums and only redeploy when they change12:05
lpappbluelightning: so images are always reprocessed in dylan, but packages are not?12:06
bluelightninglpapp: yes12:06
bluelightninglpapp: where by packages you mean other non-image recipes12:06
lpappok, so "bitbake -c deploy -f u-boot" it is, thanks.12:07
*** dguthrie_ <dguthrie_!> has quit IRC12:08
lpappis there any code name for the next release, already?12:15
*** fusman <fusman!~fahad@> has quit IRC12:23
RPlpapp: its not been announced yet12:31
lpappbluelightning: rburton
yoctiBug 5772: normal, Undecided, ---, melissa, NEW , Add easily obtainable permalinks to the variables in the documentation12:32
*** danielki <danielki!~daniel@> has joined #yocto12:32
lpappRP ok, thanks12:32
zeckeRP: Do you guys have reports that gcc 4.8.1/Linux-3.10 fail?12:49
lpappYocto is intending to move to python 3 in the next release?12:49
-YoctoAutoBuilder- build #5 of minnow is complete: Failure [failed BuildImages Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #5 of minnow-lsb is complete: Failure [failed BuildImages Publishing Artifacts] Build details are at
*** sroy_ <sroy_!~sroy@2607:fad8:4:6:6e88:14ff:feff:5374> has joined #yocto12:55
*** riskable <riskable!~quassel@2601:e:8c00:7e:c59e:4a3e:ba71:56a> has joined #yocto12:58
*** belen <belen!~Adium@> has joined #yocto12:58
*** g1zer0 <g1zer0!> has quit IRC13:01
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC13:02
*** rainerschuster <rainerschuster!> has joined #yocto13:04
*** ant_work <ant_work!> has quit IRC13:05
*** rainerschuster <rainerschuster!> has left #yocto13:05
*** bluelightning <bluelightning!~paul@> has joined #yocto13:05
*** bluelightning <bluelightning!~paul@> has quit IRC13:05
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto13:05
RPzecke: I haven't seen anything about that13:06
RPlpapp: we'll probably add recipes for it13:06
lpapp(someone told me it would)13:10
zeckeRP: too bad. I have weird return values on read from a AF_UNIX socket. strace itself getting stuck13:10
lpappRP: I mean, things like bitbake move to python 3 in 1.6.13:11
zqadtime to change that password anyway13:17
*** aragua <aragua!> has quit IRC13:17
*** aragua <aragua!> has joined #yocto13:28
jackmitchellit's ok, only an internal one :)13:31
bluelightningit's well and truly external now ;)13:33
lpappit does not have an uppercase in it which is a usual requirement13:35
-YoctoAutoBuilder- build #25 of buildtools is complete: Success [build successful] Build details are at
*** OlivierG <OlivierG!> has joined #yocto13:36
zeckeIn dora. Which part of the kernel should depend on kmod?13:39
*** tasslehoff <tasslehoff!~tasslehof@> has quit IRC13:39
bluelightningzecke: I thought you sent a patch for that ages ago...13:40
jackmitchelllpapp: the real one does have upper case; it a double typo ;)13:41
zeckebluelightning: if i did.. it must have been for edison. We are now working on the dora upgrade for the BTS images.13:41
lpappjackmitchell: :D13:42
bluelightningzecke: hmm, I just checked back, maybe I was mistaken13:42
zeckebluelightning: I sent patches for update-alternatives of uImage.13:42
zeckebluelightning: so kernel.bbclass creates a postinst that will invoke depmod13:44
zeckebluelightning: but there is no RDEPENDS that lead to the installation of kmod. :(13:45
bluelightningzecke: I think we may have enabled depmod in busybox...13:45
zeckebluelightning: that could explain.13:45
*** elmi82 <elmi82!> has joined #yocto13:46
zeckeyes you do. We have a custom defconfig for busybox to enable ifplugd. :}13:46
zeckeat the same time systemd tries to execute /bin/kmod and that fails too13:47
bluelightningzecke: systemd should have kmod in its RDEPENDS13:49
lpappkhem: so how is the bitbake port work to python 3?13:50
*** zz_akbennett is now known as akbennett13:50
*** tasslehoff <tasslehoff!~tasslehof@> has joined #yocto13:51
*** rainerschuster <rainerschuster!> has joined #yocto13:51
zeckebluelightning: haha. more stuff i broke. We kick out dbus from the RDEPENDS. :}13:52
bluelightningzecke: you use systemd without dbus?13:52
zeckebluelightning: without dbus-daemon13:53
zeckebluelightning: it is using libdbus and communicates over AF_UNIX13:54
bluelightningah right13:54
bluelightningzecke: FYI you should be able to use _remove in dora for that sort of thing now13:54
*** av500 <av500!> has quit IRC13:56
zeckebluelightning: ah lovely! it appears to work.13:59
zeckebluelightning: the BTS is just a TI Davinci DM644x.. a tiny arm core (by modern standards) no need to start daemons that take RAM and don't do useful things14:00
bluelightningzecke: fair enough14:00
bluelightningzecke: btw, are you or any of your colleagues by chance coming to FOSDEM?14:00
zeckebluelightning: no one that is involved with the Yocto part but two colleagues will be there. I have to attend a funeral instead. :(14:01
bluelightningzecke: ah, my condolences14:01
-YoctoAutoBuilder- build #5 of nightly-qa-skeleton is complete: Success [build successful] Build details are at
*** e8johan_ <e8johan_!> has quit IRC14:02
zeckebluelightning: thanks. I intend to join ELCE and also hand in a talk about using Yocto to build our GSM basestation14:03
*** av500 <av500!> has joined #yocto14:03
-YoctoAutoBuilder- build #5 of nightly-intel-gpl is complete: Failure [failed BuildImages BuildImages_1] Build details are at
TuTizzwhat is YOCTO #3847?14:04
yoctiBug 3847: enhancement, High, 1.5.1, tom.zanussi, VERIFIED FIXED, New partitioning description and tooling14:06
TuTizzok ty14:06
*** oneQubit <oneQubit!> has joined #yocto14:11
*** Net147 <Net147!> has quit IRC14:12
*** elmi82 <elmi82!> has quit IRC14:13
*** SorenHolm <SorenHolm!> has quit IRC14:15
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-zrncjzsnabgtjzcv> has joined #yocto14:15
*** dlerner1 <dlerner1!~dlerner@> has left #yocto14:17
*** dlerner1 <dlerner1!~dlerner@> has joined #yocto14:18
*** elmi82 <elmi82!> has joined #yocto14:20
*** bfederau <bfederau!> has quit IRC14:20
*** zeeblex <zeeblex!apalalax@nat/intel/x-ydbvadmxvdlrlfbx> has joined #yocto14:21
*** mthalmei_away <mthalmei_away!> has quit IRC14:21
*** bfederau <bfederau!> has joined #yocto14:22
zeckebluelightning/RP: What is the procedure to get that into the Dora gcc 4.8?14:22
yoctiBug 58854: was not found.14:22
*** otavio <otavio!~otavio@debian/developer/otavio> has quit IRC14:23
*** otavio <otavio!> has joined #yocto14:23
*** otavio <otavio!~otavio@debian/developer/otavio> has joined #yocto14:23
*** zeeblex1 <zeeblex1!~apalalax@> has quit IRC14:23
-YoctoAutoBuilder- build #5 of poky-tiny is complete: Success [build successful] Build details are at
*** mthalmei_away <mthalmei_away!> has joined #yocto14:26
lpappif I change a patch, will Yocto re-apply it for bitbake -c compile -f virtual/kernel?14:31
*** belen <belen!~Adium@> has quit IRC14:31
rburtonif anything in SRC_URI changes, fetch and patch re-execute14:31
lpappnothing changed.14:32
lpappthe patch changed itself.14:32
rburtonthat's what i meant14:32
rburtonif SRC_URI points at a patch, then fetch/patch re-runs if it changes14:32
lpappok, but -c compile -f will not, right.14:33
lpappbitbake virtual/kernel will recreate the ipkg though?14:33
rburtonyou'er asking explicitly to run compile14:33
lpapprburton: well, yes and no.14:33
lpappbitbake virtual/kernel seems to return instantly.14:33
lpappeven though I did modify a patch14:33
lpappI added three lines.14:33
*** sjolley <sjolley!~sjolley@> has joined #yocto14:34
lpappit should rebuild the kernel :-/14:34
rburtonyes it should14:34
lpappmight be some bug somewhere.14:35
*** rainerschuster <rainerschuster!> has left #yocto14:43
*** fusman <fusman!~fahad@> has joined #yocto14:47
-YoctoAutoBuilder- build #6 of nightly-qa-logrotate is complete: Success [build successful] Build details are at
*** ploppy <ploppy!> has quit IRC14:56
*** ploppy <ploppy!> has joined #yocto14:57 says that in order to submit a patch user has to do 'git format-patch -1' or 'git format-patch HEAD~'14:57
Xzdon't we want people to use -M flag to git-format-patch?14:58
lpappyou can14:58
Xzlpapp or khem I think was suggesting that yesterday to me14:58
Xzdo we want to improve doc?14:58
Xzand add that -M flag?14:58
Xzno idea who is responsible for doc14:58
-YoctoAutoBuilder- build #6 of nightly-qa-pam is complete: Success [build successful] Build details are at
lpappXz: Scott, yeah, why not.14:59
bluelightningXz: yes we should fix that in the manual14:59
Xzis it 'scot' on this channel?14:59
lpapphave never seen him here.15:00
lpappbut no15:00
Xzcould you msg me email?15:00
Xzcool, thanks15:00
*** Xz <Xz!kmsywula@nat/intel/x-bklfljtgsnwjctlg> has quit IRC15:11
*** Xz <Xz!~kmsywula@> has joined #yocto15:11
*** challinan <challinan!> has joined #yocto15:15
*** gmacario <gmacario!> has joined #yocto15:15
*** tasslehoff <tasslehoff!~tasslehof@> has quit IRC15:17
*** SorenHolm <SorenHolm!> has joined #yocto15:21
Xzhow do I do tell bitbake to use different (shared) download directory?15:26
*** SorenHolm <SorenHolm!> has quit IRC15:26
rburtonset DL_DIR15:26
rburton(if you want to read/write into a local directory)15:27
Xzrburton: DL_DIR is rw? so if anything must be downloaded bitbake will use it?15:27
rburtonDL_DIR is where bitbake's fetchers will check first for files to download, and will put anything it downloads into there15:28
rburton(so you really want to share DL_DIR between all of your build directories)15:28
Xzcool, is it bitbake or bash variable?15:28
rburtonbitbake, see your local.conf15:28
Xzrburton: thanks, works15:34
rburtonXz: this is the sort of thing you can put into a shared site.conf that you copy between all your build folders, if you have several15:34
*** fpaut is now known as ghosta15:35
Xzrburton: where do you put site.conf? under conf/ ?15:35
*** ghosta is now known as fpaut15:35
rburtonthat's one place15:35
Xzrburton: I'm not using site.conf so far15:35
rburtonpersonally i have a meta-ross that i add to bblayers, that has a site.conf in it15:35
Xzrburton: nice trick15:36
kergothi usually set up my bblayers.conf ot include ~/.oe, and put it there15:36
*** rainerschuster <rainerschuster!> has joined #yocto15:36
kergothlots of ways to do it :)15:36
Xzguys, on dylan sanity checker does not catch wrong git version: git version
kergothdownside to the ~/.oe approach is that you can forget it's there, since its largely out of sight :)15:37
*** sjolley1 <sjolley1!~sjolley@> has joined #yocto15:37
*** sjolley <sjolley!~sjolley@> has quit IRC15:37
*** rainerschuster <rainerschuster!> has quit IRC15:39
Xzanybody goes to FOSDEM'14  ?15:40
Xzin Brussels, 1&2 February 201415:41
bluelightningXz: yep, I'll be there15:41
bluelightningXz: Beth and Belen are also going15:41
bluelightningXz: and a lot of others15:41
Xzwill talk to my boss about it15:42
Xzit's a pity it's so soon15:42
XzI'm working on one demo-robot15:42
*** kbart <kbart!~KBart@> has quit IRC15:43
Xzdo you know where do I fix sanity checker for dylan's git version ?15:47
*** Crofton <Crofton!> has joined #yocto15:49
lpappXz: are you also working for intel?15:49
*** zecke <zecke!> has quit IRC15:51
mckoanbluelightning: if Belen did a presentation I would jump on the first flight :-D15:53
*** zeeblex <zeeblex!apalalax@nat/intel/x-ydbvadmxvdlrlfbx> has left #yocto15:53
lpappmckoan: why ?15:53
*** Jefro <Jefro!> has joined #yocto15:53
mckoanlpapp: as I told her at ELCE her talks are great like the TED ones :-D15:54
mckoanprobably a matter of charisma ;-)15:55
*** sjolley1 <sjolley1!~sjolley@> has quit IRC15:55
lpappmckoan: ok15:59
*** gjohnson <gjohnson!> has left #yocto16:05
*** Xz <Xz!~kmsywula@> has quit IRC16:07
*** sgw_1 <sgw_1!> has quit IRC16:11
*** denix <denix!> has joined #yocto16:11
*** fpaut is now known as fpaut_16:11
*** fpaut_ is now known as fpaut16:12
*** dguthrie <dguthrie!> has joined #yocto16:15
*** Xz <Xz!kmsywula@nat/intel/x-fxoblecoogdelxye> has joined #yocto16:23
*** challinan <challinan!> has quit IRC16:24
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC16:24
*** belen <belen!~Adium@> has joined #yocto16:25
*** belen <belen!~Adium@> has quit IRC16:25
*** belen <belen!~Adium@> has joined #yocto16:26
*** elmi82 <elmi82!> has quit IRC16:26
*** fusman <fusman!~fahad@> has quit IRC16:27
*** sjolley <sjolley!~sjolley@> has joined #yocto16:28
*** sjolley <sjolley!sjolley@nat/intel/x-tyczzjisoqqumyyx> has joined #yocto16:29
*** belen1 <belen1!~Adium@> has joined #yocto16:31
*** belen <belen!~Adium@> has quit IRC16:32
*** khem` <khem`!> has joined #yocto16:34
*** challinan <challinan!> has joined #yocto16:36
*** Xz <Xz!kmsywula@nat/intel/x-fxoblecoogdelxye> has quit IRC16:40
*** Xz <Xz!kmsywula@nat/intel/x-xcdyphprxyckacjo> has joined #yocto16:40
*** zecke <zecke!> has joined #yocto16:42
*** gmacario <gmacario!> has quit IRC16:43
*** aragua <aragua!> has quit IRC16:43
*** diego_r <diego_r!> has quit IRC16:43
*** seebs <seebs!> has quit IRC16:47
*** mckoan is now known as mckoan|away16:49
*** jackmitchell <jackmitchell!> has quit IRC16:49
*** fpaut is now known as fpaut_16:49
*** seebs <seebs!> has joined #yocto16:52
*** seebs <seebs!> has quit IRC16:54
*** belen1 <belen1!~Adium@> has quit IRC16:54
*** sgw_ <sgw_!~sgw@> has joined #yocto16:55
*** zenlinux_ <zenlinux_!> has joined #yocto16:55
*** belen <belen!Adium@nat/intel/x-uiymyeyrllvgtqzb> has joined #yocto16:55
*** seebs <seebs!> has joined #yocto16:56
*** behanw <behanw!~behanw@> has joined #yocto16:57
*** seebs <seebs!> has joined #yocto17:00
*** zenlinux_ <zenlinux_!> has quit IRC17:03
*** zenlinux_ <zenlinux_!> has joined #yocto17:03
*** balister_ <balister_!> has joined #yocto17:05
lpappwhy is poky not depending on u-boot, but poky-tiny does?17:07
*** Crofton <Crofton!> has quit IRC17:09
*** onoffon <onoffon!~kraj@> has joined #yocto17:10
*** khem` <khem`!> has quit IRC17:11
*** gjohnson <gjohnson!> has joined #yocto17:17
*** onoffon is now known as khem`17:26
*** shoragan <shoragan!~jlu@debian/developer/shoragan> has quit IRC17:30
*** fray <fray!> has quit IRC17:33
*** eballetbo <eballetbo!> has quit IRC17:35
*** daiane <daiane!> has quit IRC17:35
*** beaver_545 <beaver_545!~stuart@> has quit IRC17:36
lpappwhat is the point of the nobase.patch?17:36
*** zenlinux_ <zenlinux_!> has quit IRC17:37
*** zenlinux_ <zenlinux_!> has joined #yocto17:37
lpappRP: would you accept me splitting this patch into two logical?
lpappRP: that way, it would be easier for me to drop one, and keep the other logical change.17:38
lpappIMO, removing "*" is a strange idea...17:38
lpappthe other change could probably be even upstreamed.17:38
*** belen <belen!Adium@nat/intel/x-uiymyeyrllvgtqzb> has quit IRC17:38
*** daiane <daiane!> has joined #yocto17:39
-YoctoAutoBuilder- build #6 of nightly-ppc is complete: Success [build successful] Build details are at
JaMalpapp: I support splitting it in 2, it would save me few lines in .bbappend17:40
*** belen <belen!~Adium@> has joined #yocto17:40
JaMathe problem is that even with 2 patches only 2nd one can be dropped without causing the conflict :)17:41
JaMado_configure_prepend() { # nobash.patch has interesting side-effect which we still need sed -i 's%^root:[^:]*:%root::%g' ${S}/passwd.master17:41
JaMais what I have17:41
*** nitink <nitink!~nitink@> has joined #yocto17:41
lpappJaMa: oh, I was just writing an email to openembedded-core in parallel.17:42
khem`JaMa: why dont you have image post process function to sed it to whatever value you want17:42
lpappJaMa: we need the /bin/sh part, but the /etc/shadow part breaks for us.17:42
lpappalso, the /etc/shadow part is not in scope for that change based on the change name.17:43
lpappJaMa: I am not sure why the no bash part is not upstreamed?17:43
lpappdo you know the reason for that?17:44
lpappI can understand that the shadow part cannot be upstreamed.17:45
lpappJaMa: yes, we do such a nasty sed, too!17:45
lpappwell, something similar.17:45
danielkihm, how can I easily disable the init script? I want *no* text output to the device's screen, and ideally the splash screen to remain visible until a custom graphical app starts.17:49
*** sameo <sameo!~samuel@> has quit IRC17:50
*** Squix <Squix!> has quit IRC17:51
-YoctoAutoBuilder- build #5 of nightly-fsl-ppc is complete: Failure [failed Building Toolchain Images_1 Publishing Artifacts] Build details are at
*** nitink <nitink!~nitink@> has quit IRC17:51
lpappJaMa: something like this, git show | curlpaste17:53
rburtondanielki: in poky psplash does a chvt, so you can't see any text output until X starts17:54
rburtonall you can see is the splash until X does a chvt17:54
lpapplpapp ~/Projects/openembedded-core $ . oe-init-build-env17:54
lpappError: The bitbake directory (/home/lpapp/Projects/openembedded-core/bitbake) does not exist!  Please ensure a copy of bitbake exists at this location17:54
rburtonlpapp: oe-core doesn't contain bitbake17:55
*** vicenteolivert <vicenteolivert!57c2b5c3@gateway/web/freenode/ip.> has joined #yocto17:55
danielkiah ok, then my problem is probably that I need to get the custom app executed before that chvt. Incidentally, where to best put a startup command? Classic init script?17:55
rburtondanielki: the chvt from X?17:56
lpapprburton: seems so, yes.17:56
danielkirburton: this device is not running X17:56
*** dguthrie <dguthrie!> has quit IRC17:56
rburtondanielki: what are you using for splash?17:56
rburtonhm, can't recall what the procedure is for non-x boots17:57
danielkimaybe I should simply disable the framebuffer console in the kernel config17:57
*** zenlinux_ <zenlinux_!> has quit IRC17:59
*** zenlinux_ <zenlinux_!> has joined #yocto17:59
khem`rburton:  splash with systemd needs love in OE18:01
khem`rburton: I have dietsplash working but something more robust would be nicer18:01
lpappin general, systemd needs love IMHO. :)18:01
lpapprburton: if I understand correctly, for a real minimal distribution, you only need your own layer, openembedded-core and bitbake. Is that right?18:02
rburtonlpapp: correct18:03
rburtonlpapp: that's all poky is, after all18:03
lpappyes, but I do not need poky in the future. Currently, we require it in our distro config, but I would like to eliminate it.18:04
lpappIt is probably not a big work... probably a bit of fiddiling in the layers config and removing the requires from our distro config, and that is pretty much it?18:04
rburtonsure, it's trivial18:05
lpappwe would still get the Yocto release though, I guess?18:07
lpappbecause Yocto puts openembedded-core and bitbake together to work.18:07
lpappI think it was something like LCONF_VERSION = "5" instead of "6"18:08
lpappif I get rid of poky, right?18:08
rburtonthe bump was due to poky splitting layers18:09
rburtonwhen the YP does a release cycle you'll get new bitbake and oe-core alongside poky releases, all simultaneously (as poky is simply the union of other repos)18:09
lpappbut it is still recommended to stick to those releases for oe-core users, right?18:10
lpappI am not even sure if oe-core is released separately...18:10
lpapp(or bitbake for that matter)18:10
*** balister_ is now known as Crofton18:10
rburtonreleased, yes.  tarballs of said releases, maybe not for oe-core.18:10
rburtoni tend to recommend git clones following the stable branches.18:12
lpapprburton: is there any other place where I need to look for modifications others than the distro.conf and bblayers.conf to eliminate the needless in-between poky layer?18:13
rburtononce you've fixed bblayers.conf its entirely in your distro conf18:14
rburtonjust copy into it the pieces you want from poky.conf18:15
JaMalpapp: that paste doesn't show .bb change, but something like that18:15
JaMalpapp: image postprocess function don't play nice with package-management18:15
JaMafirst base-passwd upgrade on target would break root account18:15
lpappJaMa: yes, I have done the .bb change after posting that.18:16
lpappJaMa: I think you addressed the second to khem?18:16
lpappJaMa: why was the bash to sh change not upstreamed?18:16
*** gmacario <gmacario!> has joined #yocto18:16
lpappno one has cared yet, or it is invalid upstream?18:17
lpapprburton: ok, thanks18:17
lpappbtw, openembedded-core does not build here from master,
lpappwith master bitbake, literally cloned both a few minutes ago.18:18
*** nitink <nitink!nitink@nat/intel/x-krbzynydjmoglsjd> has joined #yocto18:18
rburton1.| line 65: /tmp/ldt.cfrIky9Jqa/linuxdoc: Permission denied18:18
rburtoncan you check permissions on your /tmp?18:18
* rburton afk18:19
lpappls -ld /tmp18:21
lpappdrwxrwxrwt 15 root root 420 Jan 30 18:10 /tmp18:21
lpapp1777, as it should.18:22
lpapptouch /tmp/foo works18:22
*** zenlinux_ <zenlinux_!> has quit IRC18:22
*** zenlinux_ <zenlinux_!> has joined #yocto18:22
JaMalpapp: ah sorry, yes it was for khem18:28
JaMaI didn't notice it was him speaking in the middle as you both have nick with the same length :)18:28
khem`JaMa: hmm yes O_P_M will miss out18:28
khem`use colors18:28
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC18:29
JaMaall people are yellow when talking to me :)18:29
khem`irssi ?18:30
lpappJaMa: maybe he meant different yellows. :)18:31
*** mr_science <mr_science!> has joined #yocto18:31
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has joined #yocto18:31
danielkirburton: Removing framebuffer console support from the kernel did the trick :)18:32
lpappso if I understand correctly, the bblayers.conf should not even be checked into our PDK repository. Is that correct?18:32
JaMakhem`: yes18:32
lpappIt will be generated on the fly out of the sample.18:32
*** danielki <danielki!~daniel@> has quit IRC18:35
*** khem` <khem`!~kraj@> has quit IRC18:38
*** khem` <khem`!> has joined #yocto18:39
-YoctoAutoBuilder- build #6 of nightly-x86-64-lsb is complete: Success [build successful] Build details are at
*** galak_pb <galak_pb!> has joined #yocto18:55
-YoctoAutoBuilder- build #6 of nightly-multilib is complete: Success [build successful] Build details are at
JaMalpapp: noshadow.patch should probably mention Kevin Tian, but otherwise looks good18:58
*** Garibaldi|work_ <Garibaldi|work_!~andydalt@nat/cisco/x-wmtnnmqpmnjjrsxp> has joined #yocto18:59
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC19:00
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-zrncjzsnabgtjzcv> has quit IRC19:00
*** Garibaldi|work_ is now known as Garibaldi|work19:00
*** onoffon <onoffon!~kraj@> has joined #yocto19:06
*** khem` <khem`!> has quit IRC19:06
*** onoffon is now known as khem`19:08
*** belen <belen!~Adium@> has quit IRC19:09
*** rainerschuster <rainerschuster!> has joined #yocto19:15
*** rainerschuster <rainerschuster!> has left #yocto19:16
*** Marex <Marex!~Marex@> has quit IRC19:29
*** Marex <Marex!~Marex@> has joined #yocto19:30
*** sgw_ <sgw_!~sgw@> has quit IRC19:34
*** Marex <Marex!~Marex@> has quit IRC19:37
*** fray <fray!> has joined #yocto19:40
*** JimBaxter <JimBaxter!> has quit IRC19:46
*** sroy_ <sroy_!~sroy@2607:fad8:4:6:6e88:14ff:feff:5374> has quit IRC19:47
*** Marex <Marex!~Marex@> has joined #yocto19:49
*** ploppy <ploppy!> has quit IRC19:53
*** mebrown <mebrown!> has joined #yocto19:58
mebrownkhem, ping. build worked with new patches, but it doesn't run:19:58
*** michael_e_brown_ <michael_e_brown_!~michaeleb@> has joined #yocto19:58
mebrown# python319:59
mebrownTraceback (most recent call last):19:59
mebrown  File "/usr/lib/python3.3/", line 69, in <module>19:59
mebrown    import os19:59
mebrown  File "/usr/lib/python3.3/", line 659, in <module>19:59
mebrown    from import MutableMapping19:59
mebrownImportError: No module named 'collections'19:59
*** SorenHolm <SorenHolm!> has joined #yocto19:59
*** michael_e_brown_ <michael_e_brown_!~michaeleb@> has left #yocto19:59
mebrowntaking a look now20:00
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto20:01
mebrownlooks like you need to have python3-misc installed by default or nothing will run. testing now.20:01
khem`mebrown: yes20:04
khem`thanks for reporting it20:05
khem`the packagegroup I have always installs python3-misc20:05
mebrownAnd I'm still using my old config of cherry picking just the modules I need.20:05
mebrownit works fine now.20:05
mebrownthanks for the help20:05
mebrownNow I can start the "real" work of porting my app.20:06
*** ploppy <ploppy!> has joined #yocto20:06
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has quit IRC20:06
*** khem` <khem`!~kraj@> has quit IRC20:09
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has joined #yocto20:10
*** cratthe <cratthe!> has joined #yocto20:15
*** cratthe <cratthe!> has joined #yocto20:16
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto20:30
*** SorenHolm <SorenHolm!> has quit IRC20:37
*** SorenHolm <SorenHolm!> has joined #yocto20:38
-YoctoAutoBuilder- build #6 of nightly-arm is complete: Success [build successful] Build details are at
*** SorenHolm <SorenHolm!> has quit IRC20:59
*** SorenHolm <SorenHolm!> has joined #yocto21:00
*** GusBricker <GusBricker!> has joined #yocto21:03
*** ant_home <ant_home!> has joined #yocto21:15
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC21:19
*** bluelightning <bluelightning!> has joined #yocto21:20
*** bluelightning <bluelightning!> has quit IRC21:20
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto21:20
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC21:22
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto21:22
*** gmacario <gmacario!> has quit IRC21:26
*** SorenHolm <SorenHolm!> has quit IRC21:27
*** GusBricker <GusBricker!> has quit IRC21:30
*** sgw_ <sgw_!~sgw@> has joined #yocto21:38
*** zenlinux_ <zenlinux_!> has quit IRC21:41
*** zenlinux_ <zenlinux_!> has joined #yocto21:42
*** SorenHolm <SorenHolm!> has joined #yocto21:50
*** SorenHolm <SorenHolm!> has quit IRC21:55
*** SorenHolm <SorenHolm!> has joined #yocto21:55
*** dlerner1 <dlerner1!~dlerner@> has quit IRC21:56
*** bluelightning_ <bluelightning_!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has joined #yocto21:58
*** bluelightning_ <bluelightning_!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has quit IRC21:58
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto21:58
*** bluelightning_ <bluelightning_!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has joined #yocto21:59
*** bluelightning_ <bluelightning_!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has quit IRC21:59
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto21:59
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC22:00
*** bluelightning_ is now known as bluelightning22:02
*** GusBricker <GusBricker!> has joined #yocto22:09
-YoctoAutoBuilder- build #5 of eclipse-plugin-kepler is complete: Success [build successful] Build details are at
*** Marex <Marex!~Marex@> has quit IRC22:17
*** Marex <Marex!~Marex@> has joined #yocto22:18
*** weebet <weebet!> has quit IRC22:28
*** zenlinux_ <zenlinux_!> has quit IRC22:28
*** sgw_ <sgw_!~sgw@> has quit IRC22:29
*** smartin_ <smartin_!> has joined #yocto22:31
*** sameo <sameo!~samuel@> has joined #yocto22:35
*** zenlinux_ <zenlinux_!> has joined #yocto22:37
*** sgw_ <sgw_!~sgw@> has joined #yocto22:40
*** SorenHolm <SorenHolm!> has quit IRC22:45
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-wmtnnmqpmnjjrsxp> has quit IRC22:57
*** galak_pb <galak_pb!> has quit IRC22:58
*** bfederau <bfederau!> has quit IRC23:01
*** bfederau <bfederau!> has joined #yocto23:01
*** cratthe <cratthe!> has quit IRC23:03
*** Jefro <Jefro!> has quit IRC23:03
*** stryx` <stryx`!~stryx@> has quit IRC23:07
*** stryx` <stryx`!~stryx@> has joined #yocto23:09
*** OutBackDingo <OutBackDingo!~quassel@unaffiliated/outbackdingo> has quit IRC23:25
*** zenlinux_ <zenlinux_!> has quit IRC23:27
*** sjolley <sjolley!sjolley@nat/intel/x-tyczzjisoqqumyyx> has quit IRC23:46
*** agust <agust!> has quit IRC23:49
*** sjolley <sjolley!sjolley@nat/intel/x-ydcscaheohzzxpfr> has joined #yocto23:51
*** ant_home <ant_home!> has quit IRC23:52
*** sjolley <sjolley!sjolley@nat/intel/x-ydcscaheohzzxpfr> has quit IRC23:53
*** seebs <seebs!> has quit IRC23:56
*** seebs <seebs!> has joined #yocto23:57
*** Squix <Squix!> has joined #yocto23:59
*** sgw_ <sgw_!~sgw@> has quit IRC23:59
*** seebs <seebs!> has joined #yocto23:59

Generated by 2.11.0 by Marius Gedminas - find it at!