Thursday, 2013-08-22

*** smartin <smartin!> has quit IRC00:00
*** sameo <sameo!~samuel@> has quit IRC00:02
*** mulhern <mulhern!> has joined #yocto00:07
*** mulhern <mulhern!> has quit IRC00:08
*** mulhern <mulhern!> has joined #yocto00:08
*** andyross <andyross!> has quit IRC00:15
*** oscailt <oscailt!~oscailt@unaffiliated/oscailt> has quit IRC00:17
*** oscailt <oscailt!~oscailt@unaffiliated/oscailt> has joined #yocto00:18
*** _julian_ <_julian_!> has joined #yocto00:24
*** _julian <_julian!> has quit IRC00:24
sgw_bozojoe: mark is fray00:26
*** pidge <pidge!~pidge@> has quit IRC00:27
*** swex__ <swex__!~swex@> has quit IRC00:36
*** swex__ <swex__!~swex@> has joined #yocto00:37
bozojoeanyone from intel or windriver here?00:45
seebsI deny everything.00:45
bozojoei'm a MCG guy from intel... trying to find out about yocto inside the company00:46
bozojoei've asked in our kernel mailing list but haven't heard anything yet00:47
bozojoeany use of yocto on android targets here?00:55
*** mulhern <mulhern!> has quit IRC01:04
*** Jefro <Jefro!> has quit IRC01:05
*** davest <davest!Adium@nat/intel/x-avjfwtvgxlbpoavo> has quit IRC01:06
*** b1gtuna <b1gtuna!~adam@> has quit IRC01:07
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto01:21
*** bozojoe <bozojoe!4475c643@gateway/web/freenode/ip.> has quit IRC01:23
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC01:37
*** mulhern <mulhern!> has joined #yocto01:45
*** Jefro <Jefro!> has joined #yocto01:46
*** mitz <mitz!> has quit IRC01:54
*** Jefro <Jefro!> has quit IRC01:57
*** mechnode <mechnode!> has joined #yocto01:58
*** silviof1 <silviof1!~silviof@unaffiliated/silviof> has joined #yocto02:01
*** nitink <nitink!~nitink@> has quit IRC02:02
*** nitink <nitink!~nitink@> has joined #yocto02:02
*** silviof <silviof!~silviof@unaffiliated/silviof> has quit IRC02:04
*** nitink <nitink!~nitink@> has quit IRC02:05
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto02:07
*** brm <brm!da653619@gateway/web/freenode/ip.> has quit IRC02:09
*** mechnode <mechnode!> has quit IRC02:30
*** mulhern <mulhern!> has quit IRC02:32
*** mulhern <mulhern!> has joined #yocto02:34
*** mulhern <mulhern!> has quit IRC02:34
*** ka6sox is now known as zz_ka6sox02:48
*** Jefro <Jefro!> has joined #yocto02:50
*** Jefro <Jefro!> has quit IRC02:53
*** hyang2 <hyang2!~hyang2@> has joined #yocto03:00
*** andyross <andyross!> has joined #yocto03:08
*** mitz_ <mitz_!> has joined #yocto03:30
*** amarsman <amarsman!> has quit IRC03:35
*** dv_ <dv_!> has quit IRC03:49
*** dv_ <dv_!> has joined #yocto03:51
*** zz_ka6sox is now known as ka6sox04:06
*** smartin <smartin!> has joined #yocto04:14
*** smartin_ <smartin_!> has quit IRC04:15
*** Jefro <Jefro!> has joined #yocto04:21
*** thaytan <thaytan!> has quit IRC04:24
*** thaytan <thaytan!> has joined #yocto04:25
*** andyross <andyross!> has quit IRC04:28
*** mihai <mihai!~mihai@> has quit IRC04:28
*** ftonello_ <ftonello_!> has joined #yocto04:31
*** ftonello <ftonello!> has quit IRC04:31
*** smartin_ <smartin_!> has joined #yocto04:37
*** smartin <smartin!> has quit IRC04:40
*** Jefro <Jefro!> has quit IRC04:53
*** nitink <nitink!~nitink@> has joined #yocto04:55
-YoctoAutoBuilder- build #257 of nightly-x86-64 is complete: Success [build successful] Build details are at
*** blloyd <blloyd!~blloyd@> has joined #yocto05:03
-YoctoAutoBuilder- build #238 of nightly-oecore is complete: Failure [failed Running Sanity Tests] Build details are at
*** Jefro <Jefro!> has joined #yocto05:24
*** tor <tor!~tor@> has joined #yocto05:27
*** amarsman <amarsman!> has joined #yocto05:27
*** vicky_ <vicky_!~vicky@> has joined #yocto05:37
vicky_Hi yocto. I successfully  compiled  toolchain-qte and i installed it in opt directory.But when i try to run qmake from/opt/poky/1.4.1/sysroots/x86_64-pokysdk-linux/usr/bin/qmake2 , i got "sh: 1: -list: not found"05:39
vicky_My host is ubuntu_12.04 x64.05:40
vicky_I tried sample qt applications. That also results with same error.05:41
*** mihai <mihai!~mihai@> has joined #yocto05:50
*** zeeblex <zeeblex!apalalax@nat/intel/x-qdzhhgtdniupgsya> has joined #yocto05:52
*** silviof1 is now known as silviof05:55
*** nitink <nitink!~nitink@> has quit IRC06:11
*** zecke <zecke!> has joined #yocto06:14
*** smartin <smartin!> has joined #yocto06:29
*** smartin_ <smartin_!> has quit IRC06:30
*** ant_home <ant_home!~andrea@> has quit IRC06:30
*** jeremiah <jeremiah!> has joined #yocto06:31
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC06:36
*** jonatan is now known as jonte06:38
*** yzhao2_ <yzhao2_!~yzhao2@> has joined #yocto06:39
*** mankku <mankku!> has joined #yocto06:41
*** yzhao2 <yzhao2!~yzhao2@> has quit IRC06:42
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has quit IRC06:44
*** cjosephson <cjosephson!> has quit IRC06:48
*** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has joined #yocto06:51
*** cjosephson <cjosephson!> has joined #yocto06:52
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto06:53
-YoctoAutoBuilder- build #263 of nightly-x86 is complete: Failure [failed Running Sanity Tests] Build details are at
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has joined #yocto06:59
*** rikroled <rikroled!~tbn@> has joined #yocto07:10
*** ka6sox is now known as ka6so-away07:19
thesignalhi, i want to build the cross-compiler for fortran, so i took a look at the gcc-cross recipe and figured out that it requires, there i set the FORTRAN variable to ",fortran", everything builds fine, (with bitbake -f -c compile gcc-cross & crosssdk) but when i try to compile a package which need gfortran as a compiler, the gfortran compiler is not found07:27
thesignali took a look at but somehow i don't really understand what i have to do to get the gfortran cross compiler working07:28
*** slaine <slaine!~slaine@> has joined #yocto07:28
thesignalin the sysroots directory i found a cross-gfortran compiler, which is executable (tried with arm-*something-gfortran -v)07:29
*** slaine <slaine!~slaine@> has quit IRC07:40
tfthesignal: is the pacakged using autotools?07:42
thesignaltf: which one? the one which needs gfortran?07:43
thesignalno it isn't07:44
tfyou might have to patch it, it's probably looking for gfortran, not arm-bla-bla-gfortran07:45
thesignaldo you know a recipe where this has been done? so i can take an idea how to do this07:46
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:46
tfthesignal: no, sorry07:46
thesignalkk, but thanks for the hint07:47
tfthesignal: you should find more details in the error log07:47
*** florian_kc is now known as florian07:48
thesignaltf: it just says "gfortran: command not found" but i'll take a look at the run.do_configure07:49
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has quit IRC07:52
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto07:52
tfthesignal: probably the makefile is referring to gfortran, it should be using a variable; I don't know what that would be with fortran, but for C, you would call the compiler as $CC, not gcc07:55
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC07:55
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has joined #yocto07:58
thesignaltf: thanks, i already took a look at the makefile and it's exactly like you thought :)07:59
*** ant_work <ant_work!> has joined #yocto08:00
thesignaland the toolchain and everything needed should be compiled with bitbake -f -c compile gcc-cross, right?08:00
tfthat will just compile it, not install it08:01
tf'bitbake gcc-cross' will build and install, and package it08:02
*** slaine <slaine!~slaine@> has joined #yocto08:02
bluelightningmorning all08:03
*** darknighd <darknighd!> has joined #yocto08:05
*** darknighte_znc <darknighte_znc!~darknight@pdpc/supporter/professional/darknighte> has quit IRC08:05
*** darknighd is now known as darknighte08:06
*** darknighte <darknighte!~darknight@pdpc/supporter/professional/darknighte> has joined #yocto08:06
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto08:06
*** slaine <slaine!~slaine@> has left #yocto08:08
*** melonipoika <melonipoika!> has joined #yocto08:08
*** slaine <slaine!~slaine@> has joined #yocto08:12
*** Iv_ <Iv_!53915b2e@gateway/web/freenode/ip.> has joined #yocto08:25
Iv_Hi everybody,does anyone know how to modify the root file system before it's built in the ramdisk image? thks08:28
*** honschu <honschu!~honschu@shackspace/j4fun> has joined #yocto08:31
*** jeremiah_ <jeremiah_!> has joined #yocto08:33
*** honschu_ <honschu_!~honschu@shackspace/j4fun> has quit IRC08:34
*** jeremiah <jeremiah!> has quit IRC08:35
*** gaby <gaby!> has joined #yocto08:35
*** jeremiah_ <jeremiah_!> has quit IRC08:35
*** jeremiah <jeremiah!~jeremiah@> has joined #yocto08:38
vicky_I want to add my own sysroot in meta-toolchain. Is it possible?08:39
*** mitz_ <mitz_!> has quit IRC08:48
*** JimBaxter <JimBaxter!> has joined #yocto08:49
*** mitz_ <mitz_!> has joined #yocto08:50
*** sameo <sameo!~samuel@> has joined #yocto08:50
*** belen <belen!~Adium@> has joined #yocto08:52
*** Iv_ <Iv_!53915b2e@gateway/web/freenode/ip.> has quit IRC08:55
*** Stygia <Stygia!> has joined #yocto09:00
*** amarsman <amarsman!> has quit IRC09:01
*** jackmitchell <jackmitchell!> has quit IRC09:02
*** jackmitchell <jackmitchell!~Thunderbi@> has joined #yocto09:03
bluelightningvicky_: you mean an additional separate sysroot? or do you mean customise the target part of the SDK to add additional components?09:08
*** blitz00_ <blitz00_!~stefans@> has joined #yocto09:20
*** mike <mike!c2881242@gateway/web/freenode/ip.> has joined #yocto09:21
*** mike is now known as Guest2664409:21
*** cjosephson <cjosephson!> has quit IRC09:24
*** cjosephson <cjosephson!> has joined #yocto09:24
*** uvan <uvan!7645dbc5@gateway/web/freenode/ip.> has joined #yocto09:27
uvanHi all09:28
uvancurrently UBOOT_ARCH was exported from meta/classes/kernel-arch.bbclass09:28
uvanexport UBOOT_ARCH = "${@map_uboot_arch(d.getVar('ARCH', True), d)}"09:28
uvanso it always get UBOOT_ARCH= $ARCH}09:29
uvanin my case i want UBOOT_ARCH difference from ARCH09:29
uvanthen i comment out this export statement in kernel-arch.bbclass09:29
uvanbut i think it is not the right way09:30
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has quit IRC09:30
uvancould any one give me an idea?09:30
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has joined #yocto09:30
ant_workwhat are you trying to do? Try just setting UBOOT_MACHINE09:32
uvani want to generate u-boot image. and in image_types_uboot.bbclass using mkimage -A ${UBOOT_ARCH} -O linux -T ramdisk -C $2 -n ${IMAGE_NAME}09:33
uvanbut because UBOOT_ARCH was set by ARCH so it can not create as i expected09:34
ant_worksee, you are using mkimage *native* on your host..what is wrong with that?09:44
ant_workyou ar ebuilding for a target belonging to ARCH, isn't?09:45
uvanant_work: my work right now is ARM6409:46
uvanbut for uboot, ARM64 also use the same arch with ARM09:46
uvanso linux, uboot use difference $ARCH09:46
uvanthat's why UBOOT_ARCH=$ARCH make me to problem. other architecture will not have that problem09:47
ant_workah, I see, arm64/aarch64 is new stuff09:50
ant_workas far as I see Khem is already working on it09:51
ant_work[Angstrom-devel] [meta-angstrom] angstrom-next: add versions to build for aarch6409:51
ant_workbesides u-boot support you need a proper ARCH set in OE/Yocto09:52
uvanyes, right now i can build uboot, linux, core-image-minimal and all work. but i just want to ask the right way to set UBOOT_ARCH09:53
uvanbecause i set in local.conf it will be overrwite by kernel-arch.bbclass09:53
*** jkridner|work <jkridner|work!~jkridner@nat/ti/x-hzgsmswpdogrtrfn> has quit IRC09:57
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto10:03
*** uvan <uvan!7645dbc5@gateway/web/freenode/ip.> has quit IRC10:14
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has quit IRC10:27
*** Anusko <Anusko!~anusko@> has joined #yocto10:28
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC10:30
-YoctoAutoBuilder- build #258 of nightly-world is complete: Success [build successful] Build details are at
*** dany <dany!> has quit IRC10:47
*** dany <dany!> has joined #yocto10:48
*** Corneliu <Corneliu!c0c6972b@gateway/web/freenode/ip.> has joined #yocto10:56
*** tinti_ <tinti_!~tinti@> has joined #yocto11:30
*** tinti_ <tinti_!~tinti@pdpc/supporter/student/tinti> has joined #yocto11:30
*** linu1 <linu1!~linu1@> has joined #yocto11:31
linu1hi i got this error while executing the  bitbake at91bootstrapn  on poky atmel layer,even i changed the appropriate changes in conf files.can you tell me what is that issue11:31
vicky_bluelightning: yes. I need the additional sysroot11:41
*** khohm <khohm!> has quit IRC11:45
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto11:56
vicky_bitbake image is not updating kernel modules into the image11:58
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has joined #yocto11:58
lpappanyone can tell me why the tunctl recipe has an include file ?12:05
lpappfor convenience, here is the link:
Crofton|workprobably for when there were multiple versions12:07
lpappthere were?12:07
*** khohm <khohm!> has joined #yocto12:09
lpappwill configure run automatically before make without a dedicated section if the software requires that?12:11
*** khohm <khohm!> has quit IRC12:12
*** khohm <khohm!> has joined #yocto12:13
bluelightningvicky_: I don't think we currently support that12:17
lpappdo_configure () { oe_runconf12:18
lpappdo I need to put that into the file explicitly?12:18
lpappto get ./configure run before make?12:18
bluelightninglpapp: if you inherit autotools, no, but note that running oe_runconf is not the same as what autotools.bbclass does by default12:18
bluelightninglpapp: oe_runconf will just run configure, skipping out the normal autoreconf step12:19
vicky_what i did was bitbaked meta-toolchain-qte but it doesnt included my custom packages at layer meta-atmel12:19
bluelightningvicky_: right, it won't; you may wish to use bitbake -c populate_sdk <image name> instead12:19
bluelightningvicky_: but then you'd also need to add the tools back into the host side of the SDK; for that you can append the names of the appropriate packages to TOOLCHAIN_HOST_TASK12:20
lpappbluelightning: I am not using autotools.12:20
bluelightninglpapp: right then oe_runconf won't help you12:20
lpappbluelightning: hmpf12:20
lpappso what will ?12:20
*** khohm <khohm!> has joined #yocto12:20
bluelightninglpapp: you'll need to define do_configure and in it run the configure script yourself12:21
lpappI mean ./configure is autotools.12:21
bluelightning(or, do whatever is needed for the particular piece of software to configure it before building, if it doesn't use a configure script)12:21
*** khohm <khohm!> has quit IRC12:22
*** khohm <khohm!> has joined #yocto12:22
lpappbluelightning: it uses a configure script.12:23
lpappbut in general, I saw "configure scripts" without autotools.12:23
lpappanyway, so what then?12:23
bluelightningso, as above12:23
lpapphow to run ./configure?12:23
lpappwithout autotools stuff like m4, ac etc?12:23
*** oscailt <oscailt!~oscailt@unaffiliated/oscailt> has quit IRC12:24
lpappoe_runconf should run ./configure, no?12:24
bluelightningdon't inherit autotools, and define do_configure that calls the configure script with whatever arguments are appropriate12:24
bluelightningoe_runconf is designed for autotools and is in fact defined in autotools.bbclass so you will not be able to use it for non-autotools configure scripts12:25
lpappbluelightning: why ?12:25
lpappactually, I had taken a look into it, and it does not do much else than running the configure script.12:25
lpappso it looks feasible to me for running the configure script in the source folder ...12:25
bluelightningbecause there's no commonality in other likely hand-coded configure scripts that we can support in some hypothetical non-autotools oe_runconf function12:26
bluelightningjust run the configure script with the appropriate arguments from your own do_configure12:26
lpappI only need to run ./configure, and based on the autotools class, it just does that.12:26
lpappwith the convenience of printing the config log in case of failure.12:26
bluelightningthat's autotools-specific behaviour12:27
lpappwhy would it12:27
lpappalthough it does not support arguments for configure.12:27
lpappnot that I need those, but still.12:27
lpappbluelightning: what is autotools specific ?12:29
bluelightningdoes every non-autotools configure script output a config.log? no12:30
lpappthat is what people do when there is an error, yes.12:30
lpappregardless autotools.12:30
lpappsure, yes.12:30
lpapp| ERROR: Function failed: do_configure (see  ...12:31
lpappoe_runconf: not found12:32
lpappwhy not?12:32
bluelightningbecause as I already said above it's defined in autotools.bbclass12:32
bluelightningif you're not inheriting autotools you won't have access to it12:32
lpappwhat is the point of inherit?12:35
*** musdem <musdem!> has joined #yocto12:35
*** belen <belen!~Adium@> has quit IRC12:35
lpappwhy do we even need to inherit rather than just being available by default?12:35
cfo215anyone know of a yocto-poky specific uEnv.txt file for beaglebone black?  It doesn't get created by the bitbake for beaglebone.12:36
bluelightninglpapp: as above, if it's not autotools we can't expect any kind of commonality that would merit such a common function12:36
cfo215needed for u-Boot to work properly.12:36
*** musdem <musdem!> has quit IRC12:36
bluelightninglpapp: why is it a problem to just run ./configure?12:37
*** belen <belen!Adium@nat/intel/x-qnmvkhxbphewqofk> has joined #yocto12:38
lpappbluelightning: I am not sure if it is autotools or not, to be honest.12:40
lpappI was merely referring to that, it does not use any other autotools stuff.12:40
lpappm4, ac, libtools, etc12:40
lpappother than that, I am not sure what makes a configure script "autotools".12:40
lpappI have not used autotools (luckily) the last 5-6 years.12:41
lpappoh, it has and Makefile.am12:41
lpappmaybe, it is autotools then.12:42
lpappand aclocal.m4, meh.12:42
lpappanyway, it does not build.12:42
*** linu1 <linu1!~linu1@> has quit IRC12:43
bluelightningright, you should be inheriting autotools then12:45
bluelightningcan't tell what the error is there12:45
lpappme neither ...12:47
lpappcan I simply pass arguments to oe_runconf ?12:47
bluelightningjust add whatever arguments you need to EXTRA_OECONF12:47
lpappfwiw, it works if I build on the host.12:50
lpappsure it is not a recipe issue?12:51
lpapphere is the recipe:
bluelightninglpapp: well you should definitely start without your do_configure there12:53
bluelightningdrop you definition of do_configure, autotools.bbclass provides it already12:57
lpappsure, but that should not cause such issues.12:57
lpappand yes, it is the same without.12:57
bluelightningsure, I'm just making a recommendation12:58
lpapplpapp: ok, any recommendation for the error? ;-)12:58
bluelightningit's a compilation failure with stunnel itself, you'll have to debug it like any other compilation failure12:59
bluelightningI'd start by making sure there are no clues in the do_compile (such as errors not shown in the snippet you pasted) or anything unusual in the do_configure log13:00
bluelightnings/do_compile/do_compile log/13:00
lpappI dropped an email to the stunnel-users mailing list in the meantime ...13:01
*** zenlinux <zenlinux!> has quit IRC13:01
Guest26644You could try to go those where the source is downloaded and manually try to compile it13:02
Guest26644and see what errors it produces13:03
Guest26644when you know correction then you can make a patch and include that to SRC_URI13:04
lpappbluelightning: Guest26644 this is suspicious at the end of configure,
Guest26644at least I have done a a couple of times13:04
lpappmayhaps I am missing something?13:04
bluelightningthat is odd... never seen that before13:05
lpappkinda me neither ...13:06
lpapp/bin/bash: ../-libtool: No such file or directory13:06
lpappI think running "make" manually will not try to use the cross autotools?13:06
erboanyone know the status of icecc support? saw an old mailthread for aug/sept 2012 where someone had issues but nothing after that13:06
lpappso it is not simply going into the work folder, and "./configure && make", right ?13:07
Guest26644you need to do the settings first13:07
Guest26644I'm not sure about running the configure steps.. I was just talking about compiling the code13:08
*** cfo215 <cfo215!> has left #yocto13:10
Guest26644but anyway in order to get my code to compile  I needed to modify the .am file to include one setting and I done that with patch13:11
lpappGuest26644: I do not know how to do any settings in there...13:12
lpappand what exactly, etc.13:12
lpappGuest26644: archlinux seems to have a makefile patch, but it is about install, so I believe it is not related,
Guest26644You can do a patch for any file. That was just example13:13
lpappof course... no doubt in there.13:14
Guest26644if you can somehow find the what the error is ..13:14
lpappI am just trying to solve this stuff. :)13:14
Guest26644then you can try to google that and try patch to fix it13:14
lpappwell, packager life is not easy I guess.13:15
ant_worklpapp: Gentoo has similar patch
ant_workyou could add it in do_configure_prepend13:16
lpappant_work: what patch?13:16
*** mulhern <mulhern!> has joined #yocto13:27
lpappant_work: related to this issue I am facing, or you mean the Makefile am stuff?13:29
*** cfo215 <cfo215!> has joined #yocto13:35
cfo215my yocto kernel keeps getting stuck at "Starting kernel ..." on beaglebone black using core-image-minimal. Anyone run into this? has boot log from BBB.13:43
ant_worklpapp: obvioulsy I was referring to the arch linux patch you showed13:43
lpappant_work: ok, that would not help in here, I believe.13:44
lpappnor did EXTRA_OECONF += "--disable-fips"13:44
ant_worklpapp: have you tried removing your do_configure ?13:44
lpappant_work: yes13:44
ant_workah, ok, this was th enext step: customize it13:44
lpappcustomize what exactly?13:45
simar_cfo215: could you verify that your console output is on ttyS0?13:45
ant_worklpapp: one way is as you did, with13:46
lpappant_work: no, I mean what flags, etc.13:46
lpappanyway, I am waiting for the authors to reply, I believe.13:46
lpappI have no clue in here.13:46
lpappI wonder if anyone else could test my recipe on desktop.13:46
lpappwithout external toolchain, arm board etc.13:46
cfo215simar_: sorry I'm a newb... how do I go about that?  I got the output for the pastebin from gtkterm connected to the console port on the black.13:47
lpappthis is the latest variant,
lpappfile name is stunnel_4.56.bb13:47
lpappit only depends on openssl.13:47
cfo215simar_: i'm pretty sure I'm not understanding the question?  I followed the instructions at
simar_it seems your console line isn't correct.13:51
cfo215I don't have SERIAL_CONSOLE_beagleboard = "115200 ttyS2" in my local.conf.  Should I add "SERIAL_CONSOLE_beaglebone = "115200 ttyS0"? to local.conf and rebuild the image.13:51
thesignalhi, I'm trying to compile a package (octave) but the compilation fails, in the log i found "error: ::gmtime has not been declared", i think i have a mistake with my sysroots configuration, any ideas?13:52
simar_cfo215: I see it as bootargs=console=ttyO0,115200n8 in the pastebin that you sent me.13:52
cfo215simar_: ic.  so I need to change my uEnv.txt file.13:52
tfthesignal: you probably miss in DEPENDS some package it depends on13:54
thesignalthe error refers to /usr/include/c++/ctime13:54
thesignaltf: how do i find out which packages that are?13:55
tfthesignal: libc++ or whatever it's called?13:56
thesignalhm, good point, i'll try some13:57
cfo215simar_:Should I add "SERIAL_CONSOLE_beaglebone = "115200 ttyS0"? to local.conf and rebuild the image.13:58
*** jmpdelos <jmpdelos!> has quit IRC13:59
*** jmpdelos <jmpdelos!> has joined #yocto14:00
simar_cfo215: console=ttyO2,115200n814:00
cfo215simar_ do I use beagleboard or beaglebone in the local.conf?  my target is beaglebone.14:03
*** walters <walters!walters@nat/redhat/x-kyuzbuehngamvuaq> has joined #yocto14:03
*** Anusko <Anusko!~anusko@> has quit IRC14:03
simar_cfo215: you can also check in meta-yocto-bsp/conf/machine/beagleboard.conf to see what console line you have.14:04
*** Anusko <Anusko!~anusko@> has joined #yocto14:04
cfo215simar_: thanks.14:04
bluelightningcfo215: beaglebone surely - but then of course you'll need a layer providing the beaglebone machine (e.g. meta-beagleboard - confusing naming perhaps)14:05
*** cfo215 <cfo215!> has quit IRC14:12
*** Krz <Krz!c0c6972b@gateway/web/freenode/ip.> has joined #yocto14:13
KrzHi there, how do I extend uclibc to add libstdc++ ?14:13
*** cfo215 <cfo215!> has joined #yocto14:16
cfo215blueligtning: so I need to download meta-beagleboard; change it to dylan; update my local.conf to include 'SERIAL_CONSOLE_beaglebone = "115200 ttyO2"' and re-run bitbake and recreate the SD card.14:18
cfo215is there a better irc chat program than empathy on ubuntu?  I really don't like it...14:19
rburtoncfo215: xchat is the usual14:20
rburtonempathy isn't great for IRC14:20
*** oscailt <oscailt!~oscailt@unaffiliated/oscailt> has joined #yocto14:20
cfo215rbuton: thanks, installing it now.14:20
tfirssi best of all :)14:22
lpappcfo215: you can use completion with tabs. it is "rburton". :)14:22
*** cfo215_ <cfo215_!> has joined #yocto14:22
*** cfo215 <cfo215!> has left #yocto14:23
*** cfo215_ <cfo215_!> has quit IRC14:23
*** cfo215_ <cfo215_!> has joined #yocto14:26
sgw_bluelightning: I wonder if the updated libX11 will help marko's issue, I am sending email.14:27
bluelightningsgw_: not sure...14:28
*** lpapp <lpapp!~lpapp@kde/lpapp> has left #yocto14:28
cfo215_rburton: thanks for your help.  did you happen to get my last message before my empathy crashed?14:28
rburtoncfo215_: last i saw was thanks, installing it now14:29
*** jmpdelos <jmpdelos!> has quit IRC14:29
cfo215_rburton: I need to git clone meta-beagleboard; change it's branch to dylan; add it to bblayers.conf; update local.conf with ttyO2 stuff and rerun bitbake for my image.14:31
bluelightningcfo215_: that sounds reasonable14:31
cfo215_bluelightning, rburton : I'll try those.. and recreate the SD card of course.14:33
*** mulhern <mulhern!> has quit IRC14:33
*** mulhern <mulhern!> has joined #yocto14:34
*** Corneliu <Corneliu!c0c6972b@gateway/web/freenode/ip.> has quit IRC14:35
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto14:37
lpappbluelightning: how can I get the proper include path?14:37
bluelightninglpapp: figure out how that path is getting in there and fix it14:38
bluelightninglpapp: it'll be specific to this particular piece of software14:38
lpappbluelightning: really ? :O14:38
lpappbluelightning: what is the "proper way" for upstream?14:39
lpappbluelightning: first of all, what should be the include path?14:40
bluelightninglpapp: ${STAGING_INCDIR} I would think14:41
lpappbluelightning: that variable is empty if I print it on the command line...14:41
lpappwhich might be expected, so is it not a relatively clear path which should be the same from the projectroot?14:41
*** jmpdelos <jmpdelos!> has joined #yocto14:42
cfo215_bluelightning, rburton: to be clear, do I then remove meta-ti from bblayers.conf14:43
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto14:44
tfcfo215_: does meta-beagleboard require meta-ti?14:45
tfif not, then remove it14:45
cfo215_tf, not according to the README.md14:46
*** bozojoe <bozojoe!4475c643@gateway/web/freenode/ip.> has joined #yocto14:50
cfo215_ERROR: Unable to parse /media/toshiba-usb3/work/poky/meta-beagleboard/conf/layer.conf: [Errno 2] No such file or directory: '/media/toshiba-usb3/work/poky/meta-beagleboard/conf/layer.conf'14:50
bozojoeanyone building android systems with yocto here?14:51
cfo215_do I need to copy one from the common-bsp/conf/ or meta-beagleboard-extras/conf?14:51
lpappbozojoe: systems?14:51
rburtonbozojoe: haven't heard of anyone doing it, but it should be perfectly doable if you fancy the challenge14:51
bozojoe"android systems" i mean using yocto for commercial android phone or tablet kernels/rootfs/etc14:53
tfcfo215_: no, each layer needs to provide a layer.conf, it should be there14:54
lpappbozojoe: I do not think oe-core, or even oe would have the packages to do so.14:55
rburtonlpapp: sure, any android support would be a separate layer14:55
rburtonits been mulled over numerous times by various people, but nothing (afaik) has actually happened14:56
lpappincluding bionic14:56
*** blitz00_ <blitz00_!~stefans@> has quit IRC14:56
lpappso it would be quite a bit of investment.14:56
*** mulhern <mulhern!> has quit IRC14:56
*** andyross <andyross!> has joined #yocto14:56
cfo215_It doesn't.  I used git clone git://
lpappso where are the cross-compiler include files with Yocto ?14:57
cfo215_I'm very frustated now.  It's supposed to be "The official OpenEmbedded/Yocto BSP layer for platforms."14:57
lpappwhat is STAGING_INCDIR falling to, compared to the TOPDIR for instance, or well, even build dir.14:57
bozojoethanks all... i learned of yocto yesterday... i need to ask around our org to see if anyone has seriously contemplated this.14:58
rburtonlpapp: STAGING_INCDIR is a variable in .bb scope14:58
RPbozojoe: FWIW I like the idea but have never had the time to look at it. The system itself should be able to support it quite well14:59
lpapprburton: can you try to verify the cross compilation issue with stunnel?14:59
rburtonlpapp: not at the moment, sorry.14:59
lpappbozojoe: if you are not google, I would not probably bother...14:59
lpappit is not using GNU Linux.14:59
lpappno busybox, etc.15:00
*** tomz <tomz!> has joined #yocto15:00
bozojoelpapp: lol... i know... if you != google then all_bets = off15:00
lpappwell, google or some google affilated partner.15:00
*** tomz is now known as Guest7979715:00
ndeccfo215_: the layer is in common-bsp folder, you need to add it in bblayer.congf15:01
cfo215_ndec, change /poky/meta-beagleboard to /poky/meta-beagleboard/common-bsp in bblayers?15:02
cfo215_ndec, I'll try that.15:03
*** mulhern <mulhern!> has joined #yocto15:03
lpappbozojoe: I would not like to discourage you ... go ahead by all means if you like, but well, it is not a simple job.15:04
cfo215_ERROR: ParseError at /media/toshiba-usb3/work/poky/meta-beagleboard/common-bsp/recipes-kernel/linux/ Could not inherit file classes/machine_kernel_pr.bbclass15:04
cfo215_ERROR: Command execution failed: Exited with 115:04
lpappbozojoe: even getting a lot simpler stuff is painful with Yocto at times, like external cross compiler.15:04
lpapphere, you would replace the gnu userspace.15:04
*** panda84kde <panda84kde!> has joined #yocto15:05
*** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has quit IRC15:06
bozojoelpapp: luckily, my dev environment and target are both x86... hopefully that will make things easier15:08
cfo215_I'm ready to give up on Yocto/OE.. it shouldn't be this hard to set up.  I've wasted so much time chasing down "undocumented" features.  All you people have been very helpful but it's been a few weeks now and still don't have a bootable  machine.15:09
lpappbozojoe: you cannot avoid the non-gnu userspace... or you cannot call it android otherwise. :)15:09
lpappmaybe gnudroid.15:09
kergothcfo215_: iirc machine_kernel_pr is in meta-oe. i'm surprised, if it needs that, the readme should list it15:09
cfo215_my mistake... I have the folder. don't have it in my bblayers15:11
*** zenlinux <zenlinux!> has joined #yocto15:11
*** Stygia <Stygia!> has quit IRC15:13
*** hollisb <hollisb!> has joined #yocto15:13
rburtoncfo215_: you might have better luck in the beagleboard support channels as they'll know how their layer is meant to work15:14
cfo215_i added .../meta-oe/meta-oe to my bblayers.conf and it's now parsing recipes..15:14
*** davest <davest!Adium@nat/intel/x-wukbmwychpwmrgsr> has joined #yocto15:15
ant_workseems one day beagle* will use linux-yocto15:16
cfo215_ant_work, thats why I'm here... trying to use poky to build an image for my BBB.15:17
cfo215_ERROR: No recipes available for:15:17
cfo215_  /media/toshiba-usb3/work/poky/meta-oe/meta-oe/recipes-core/busybox/busybox_1.21.1.bbappend15:17
cfo215_ERROR: Command execution failed: Exited with 115:17
cfo215_at least with meta-ti I was able to "build' an image.  it just wouldn't boot on the BBB.15:18
kergothlayer branch mismatch?15:18
* kergoth shrugs15:18
ant_workthe point is, main kernel dev is done outside Yocto but talking with one lead devel I can say there is interest15:18
denixI'm not going to help or comment - it's unappreciated job here, apparently...15:18
ant_workit's a bit uncomfortable to have a beagleboard machine listed in compatibility and then needing extra-layers...15:19
denixant_work: beagleboard is supported in yocto directly15:20
denixant_work: don't confuse the matter with beaglebone15:20
ant_workyes, in linux-yocto15:20
cfo215_denix, how about bone?  is it or isn't it doable out of the box" .i.e. fresh download of poky?15:21
denixant_work: and if needing extra-layers is a problem, then you shouldn't use yocto at all15:22
*** mulhern <mulhern!> has quit IRC15:22
denixpoky? don't know. I'm sure it's not. it's a _reference_ distro - don't expect it to support everything and a kitchen sink15:23
ant_workdenix: I was just talking with Koen about how you can quickly put together kernel and share patches without git branches and stuff for a pool of machines (SOC)15:23
cfo215_denix, ant_work: if the bottom line is that I can't use Yocto to build an image, extra-layers or not, then I need to move on and quit wasting my time trying.15:23
*** zaif <zaif!83ea1615@gateway/web/freenode/ip.> has joined #yocto15:24
* jkridner would still like to see Yocto switch from BeagleBoard to BeagleBone Black to make the entry cost lower, especially since the stock Yocto multimedia support isn't very strong.15:24
tfcfo215_: it's pretty simple; for a machine, you need a bsp that supports that machine; for bone that's meta-beagleboard15:24
ant_workall can be in a linux-yocto_x.y.bbappend15:24
denixcfo215_: you can definitely use Yocto with extra layers to get BBB up and running - either meta-ti or meta-beagle is needed15:25
*** smartin_ <smartin_!> has joined #yocto15:25
ant_workand a proper dir structure15:25
zaifWhat are the cmake parameters that needs to be included in my recipe?15:25
lpappcan anyone try to build my recipe?15:25
denixant_work: why centralized place?15:25
ant_worklpapp: sure, later home15:25
lpappant_work: I will not be available later.15:25
cfo215_tf, denix: i tried with meta-ti and got an image built but it wouldn't boot off the SD card.15:25
cfo215_got stuck at "Starting kernel ..."15:26
ant_workdenix: you would still need a BSP layer15:26
*** smartin <smartin!> has quit IRC15:26
denixcfo215_: there is a mailing list for meta-ti. as well as the one for meta-beagle - have you tried asking there?15:26
cfo215_denix, no but I will.15:27
denixcfo215_: there are many variables - have you preped your SD properly? MLO, u-boot, uImage, DTB?15:27
bluelightningjkridner: I think zeddii is planning on refreshing the reference hw soon, but it's almost certainly too late for 1.515:29
cfo215_I followed (partially) the instructions for beagleboard on Yocto-Progject website.15:29
tfcfo215_: beableboard is not beaglebone15:29
*** blloyd <blloyd!~blloyd@> has quit IRC15:29
cfo215_tf,  yeah, got that.  I have one of each.15:30
ant_workcfo215_: here, from our point of view it is the same..kernel + patches15:30
*** vicky_ <vicky_!~vicky@> has quit IRC15:30
denixant_work: and from another point of view it's just a PCB with some components on it...15:31
ant_workdenix: see how different machines can convive:
*** zeeblex <zeeblex!apalalax@nat/intel/x-qdzhhgtdniupgsya> has left #yocto15:33
cfo215_denix, do you have a working SD card for a BBB that uses yocto-poky-linux?15:33
*** mihai <mihai!~mihai@> has quit IRC15:33
denixant_work: I'm not arguing it's possible. I'm saying there are many reasons to not do it that way (mostly political, that you don't have control over...)15:34
cfo215_denix, i'm rebuilding my image using meta-ti.  I'll work on finding an answer to my SD card issue.15:34
denixcfo215_: I don't currently have an image from poky - I don't use that distro. again, yocto != poky15:36
*** nitink <nitink!~nitink@> has joined #yocto15:39
*** BCMM <BCMM!> has joined #yocto15:40
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto15:40
*** mulhern <mulhern!> has joined #yocto15:44
cfo215_denix, thanks.  I'd be happy with any distro that works on BBB with Qt4 or Qt5 on it.  Console only.  No X11 stuff here.15:44
cfo215_i was hoping to save time with Yocto for building images.15:45
*** seebs <seebs!> has quit IRC15:47
jkridnerbluelightning: does that also mean moving the x86 reference to MinnowBoard?15:48
*** ka6so-away is now known as ka6sox15:48
bluelightningjkridner: I'm not sure... I'm not really involved in that side of things, I just know Bruce has mentioned refreshing the reference hardware15:49
*** seebs <seebs!> has joined #yocto15:53
*** belen <belen!Adium@nat/intel/x-qnmvkhxbphewqofk> has quit IRC15:54
denixcfo215_: and it should work. for example, our Arago distro works on all supported TI platforms from meta-ti with Qt4, no X1115:54
*** tbn_ <tbn_!~tbn@> has joined #yocto15:55
*** nitink <nitink!~nitink@> has quit IRC15:55
denixcfo215_: although, meta-beagle might have better cape support, if you require that15:55
*** bluelightning_ <bluelightning_!~paul@> has joined #yocto15:57
*** bluelightning_ <bluelightning_!~paul@> has quit IRC15:57
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto15:57
*** rikroled <rikroled!~tbn@> has quit IRC15:58
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC15:59
*** bluelightning_ is now known as bluelightning15:59
*** belen <belen!~Adium@> has joined #yocto15:59
*** thaytan <thaytan!> has quit IRC16:00
ant_workcfo215_: take advantage of koen help on #beagle. Keep the logs ;)16:03
ant_work...and ignore the funny people :D16:05
*** vmeson <vmeson!~quassel@> has joined #yocto16:08
denixant_work: ?16:10
ant_workdenix: he's getting red carpet...plenty of help...a #beagle chat could have been much worse... ya know16:12
ant_workI get my daily dose of humor there16:13
denixant_work: ah, you mean regular trolls there... :)16:13
denixyes, #beagle could be very intimidating for newbies! :)16:14
*** tbn_ <tbn_!~tbn@> has quit IRC16:14
lpappant_work: I will try to be available later ... feel free to ping me.16:19
lpappif I am up...16:19
ant_worksorry I don't have toolchain here16:20
ant_workjust Gentoo x8616:20
lpappno, at home16:20
lpappbut I might not be able to provide the recipe, so better if you can back it up16:21
ant_workseems (as always) straigthforward at first sight ;)16:21
lpappwhat does?16:21
ant_workI'd have expected it to compile flawlessy16:21
lpappwell, it depends on upstream, I guess.16:22
ant_workI'm familiar with stubborn recipes anyway16:22
lpapp -> here is the recipe again.16:22
lpappthe first step would be to figure out where Yocto looks for the cross-compilation includes.16:22
ant_workyes, is the same version as Gentoo has16:22
lpappwhich path compared to the build dir, etc.16:22
tflpapp: no, you get that wrong way round, you need to work out where the upstream package looks for the includes16:23
lpappno no16:24
lpappthat one clear already, see the build output.16:24
lpappand it is apparently wrong as it is /usr/include16:24
lpappwhich probably should be somewhere inside the build directory.16:24
tfinclude failing is almost always down to two things: a missing dependency from DEPENDS or hardcoded path in the upstream project16:24
lpappbut I would like to know where exactly.16:24
*** mulhern <mulhern!> has quit IRC16:25
tflpapp: have fun :)16:26
ant_worklpapp: my workflow is usually to patch the Makefile an then if possible to transfer the changes in the recipe via EXTRA_OE.. or custom tasks16:26
Krzdoes anybody know how to add libstdc++ to uclibc based image?16:26
tfKrz: there is uclibc++ iirc16:27
lpappant_work: I am interested in any workaround. :)16:27
Krztf: what's the channel name? #uclibc ?16:27
lpappbut it works for arch-arm fwiw which is also using arm 32.16:27
lpappKrz: iirc != irc. :)16:28
ant_workKrz: ping Khem in some hour. He is UT-9 iirc16:28
*** mulhern <mulhern!> has joined #yocto16:28
Krzok, what is iirc then? :)16:28
lpappKrz: check urban dictionary.16:28
rburtonKrz: if i recall correctly16:29
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC16:29
cfo215_ant_work, "koen to me: cfo215_: what the fuck are you touching local.conf and bblayers.conf for?"16:29
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto16:29
cfo215_ant_work, very helpful.16:30
kergothyikes, he's even worse than I used to be back in the day16:30
bluelightningcfo215_: don't put up with that kind of behaviour... I wouldn't16:30
ant_workif you don't know exactly what the implications are, just follow the steps listed in Angstrom instructions16:30
ant_workthey use a strange wrapper16:30
rburtonah, koen.16:30
ant_workbut surely, once you discover oe-core / Yocto under the skin you can customize it16:30
lpappant_work: -> looks like configure needs to get the --host=arm-linux stuff?16:31
cfo215_ant_work, I've done that.  I get an image.  But it's not exactly what I need.16:31
lpapp--host=arm-linux-gnueabi to be precise.16:32
ant_workcfo215_: do you have a list of packages youwant to install ?16:32
ant_workdefine needed image16:32
*** blitz00_ <blitz00_!~stefans@> has joined #yocto16:32
ant_workit's there that you have toplay, not in the .conf files16:32
cfo215_bluelightning, "it is better to stay quiet and be judged a fool, than to open your mouth and eliminate all doubt."  I let that stuff slide off.  I'm too old to care.16:33
ant_workthat's what Koen was politely saying16:33
bluelightninglpapp: if you have a look at your log.do_configure you'll see that will already be being sent to the configure script by default16:33
* lpapp is trying EXTRA_OECONF += "--host=arm-linux-gnueabi --disable-fips"16:33
cfo215_bluelightning, it's certainly not addressing my questions.  Just useless jabber.16:33
bluelightningcfo215_: I mean, there are polite ways of pointing out when someone is doing something wrong, and that is not politeness16:33
tflpapp: the autotools class already does that16:33
lpappbluelightning: by?16:33
bluelightningcfo215_: language like that is not acceptable in my book16:33
lpapptf: that is bad16:33
ant_worklpapp: just grep the recipes for  EXTRA_  and see the examples16:34
lpappbecause it should not be arm-linux16:34
bluelightningcfo215_: at least, not on public IRC16:34
lpappit should be arm-linux-gnueabi16:34
cfo215_bluelightning, you're correct there.16:34
tflpapp: it does whatever is right16:34
lpappso if it does the wrong thing by default, it is not wonder it does not owrk.16:34
bluelightninglpapp: check what arguments actually are being supplied16:34
cfo215_bluelightning, so he "opened his mouth"... ;)16:34
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC16:34
lpappbluelightning: it is passing, yea.16:36
ant_workcfo215_: anyway, the Angstrom script does create local.conf for you and stacks up and fetches many layers16:36
ant_workcfo215_: you can obviously do that by yourself16:37
*** slaine <slaine!~slaine@> has quit IRC16:37
ant_workcfo215_: subtle difference is you have to pass MACHINE to the script, because none is defined in local.conf16:37
tfKrz: I don't think there is uclibc++ recipe in current Yocto, but there is one in oe-classic,
bluelightningI'm not there to see it but I hope he's not saying meta-beagle must be used with Angstrom and you're doing it wrong if you're not using that distro...16:37
ant_work(bad imho)16:37
ant_workant_work: cfo215_ so finally I don't see anything wrong in the local.conf you posted, just the lack of a MACHINE16:38
tfKrz: obvkously, you would need to fix that up for Yocto, but it's a start16:38
Krztf: I didn't find it either16:38
Krztf: can't I just c++ support to uclibc?16:39
tfwell now, it's a different library16:39
bluelightningKrz: I'm sure khem had a comment about uclibc++ a while back but I don't recall exactly what he said - khem?16:39
ant_workcfo215_: obviously the IMAGE_INSTALL_append are unforgivable ;)16:39
cfo215_bluelightning, I'm just trying to get any image on my BBB.  All in need is to support the lcd/touchscreen (LCD CAPE7), boot into my Qt 4 app, and allow my Qt 4 app to access the GPIO and Analog imputs, also, support for wlan.16:39
cfo215_ant_work, must be... though it works :)16:40
ant_workbluelightning: that cape stuff and it's bunch of patches are the matter16:40
bluelightningant_work: that should be provided by meta-beagleboard surely16:41
tfI have had Poky images working on the Bone White in the past, but always using meta-ti for kernels16:41
lpappthat change solves a similar issue that I have ...
bluelightningcfo215_: sounds like a reasonable expectation16:41
ant_workbluelightning: yes16:41
bluelightningI recently built an image for my beaglebone (white) as well; unfortunately X doesn't start, I keep meaning to report that as a bug16:41
lpapphere is the change.16:42
cfo215_bluelightning, I don't need X11, just shell into "my-qt-application -qws".16:42
*** eren <eren!~eren@unaffiliated/eren> has quit IRC16:42
bluelightningcfo215_: ok, was just mentioning a data point16:42
ant_worklpapp: nice catch16:43
cfo215_bluelightning, np16:43
lpappant_work: ?16:43
*** zecke <zecke!> has quit IRC16:43
ant_workit looks like same thing happens16:43
bluelightningcfo215_: the image did boot at least and the LCD part of the cape seemed to be working at least (lcd3 though in my case)16:43
lpappincludedir = /usr/include16:44
*** nitink <nitink!~nitink@> has joined #yocto16:44
lpappinside the generated Makefile16:44
lpappnow, the question where it is emanating frmo?16:44
* kergoth is happy to no longer see Error highlights in his recipes and classes16:44
lpappanyone with autotools experience?16:44
ant_workcheck the initial sources16:44
tfMakefile.am16:45 does not have any includedir entry.16:45
zibrikergoth: awesome :)16:45
* ant_work heading home, bye16:45
lpappthat is pretty much it:
*** ant_work <ant_work!> has quit IRC16:46
tflpapp: that's what Makefile is generated from16:46
tflpapp: src/, no?16:47
lpappstunnel_CPPFLAGS += -I$(SSLDIR)/include16:47
lpappWINCPPFLAGS = -I$(OPENSSLDIR)/include16:48
tfthe latter is presumably for windows, but the former is your problem, I think16:48
lpappwhy is that a problem?16:49
tfSSLDIR will be worked out in some way that does not work when crosscompiling16:49
rburtoncristianiorga: channelling the spirit of koen?16:49
lpapptf: the issue is not related to openssl16:49
lpappit fails at /usr/include/features.h16:50
tfdoesn't matter16:50
tfif the makefile injects /usr/include into the include path, you are screwed16:50
cristianiorgano, it is just that I tried to search for the term, and entered text in the wrong place :-)16:50
lpapptf: SSLDIR is not /usr/include/16:50
lpappcristianiorga: lol16:50
tflpapp: what is it then?16:51
lpapptf no clue, sorry.16:51
tfso how do you know it's not /usr/include ?16:51
cristianiorgaand it happened to me twice :-) oops again16:51
lpappbecause it is followed by /include16:51
lpappand it is not looked as /usr/include/include for the features.h16:52
tflpapp, you work from the Makefile back to, but most likely you will end up in, where there will be some home-grown check for some include location that is broken when crosscompiling16:52
lpapptf> the weird thing is the fact it seems to work for others on arm16:53
tfand what does that prove? :)16:54
lpappbuildsystem is not b0rked.16:54
tfno, it does not16:54
lpappbtw, there is also an option called --with-ssl.16:54
lpappwhere the SSLDIR comes from.16:55
lpappmaybe I should supply the poky thingie ?16:55
lpappit is also used on gentoo what ant_work linked before.16:55
tfyou could try that, but you really need to work out where in the Makefile the /usr/include comes from, it's nto that hard16:55
lpappto be more complex, it is not used on arch though.16:55
lpapptf: you are welcome to help with that.16:55
lpappnothing I found the last 10-20 minutes.16:55
tflpapp: you look into the Makefile and find where the -I/usr/include is16:57
lpappI already grepped for that, nothing really.16:57
lpappit is more complex than that.16:57
lpappwhat might be related from is this:
tflpapp: which is what I told you ages ago16:58
tfyour best option is to use the --with-ssl argument then16:58
lpappwhich I mentioned above.16:58
lpapphowever, that is not a solution itself.16:58
lpappas it still needs to receive the proper path which I would not be sure what is.16:59
cfo215_bluelightning, that's hopeful.  I'm trying a cfo215_ customized angstrom image right now.  preping the sd card.  I'll see how that goes.16:59
cfo215_bluelightning, i'd still like to get the poky booting though.17:00
rburtonlpapp: see bitbake.conf.  STAGING_EXECPREFIXDIR might be the right value for that test.17:00
lpappI do not find ant_work's gentoo log anymore. :(17:00
lpappgentoo does: --with-ssl="${EPREFIX}"/usr \17:01
tflpapp: probably ${STAGING_INCDIR}/17:01
lpappwhat is the equivalence for Yocto, STAGING_EXECPREFIXDIR ?17:01
*** bluelightning_ <bluelightning_!~paul@> has joined #yocto17:02
*** bluelightning_ <bluelightning_!~paul@> has quit IRC17:02
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto17:02
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC17:02
lpapptf: forward slash ?17:02
lpappEXTRA_OECONF += "--disable-fips --ssl-dir='${STAGING_INCDIR}'" ? -> something like this ?17:03
*** belen <belen!~Adium@> has quit IRC17:03
lpappEXTRA_OECONF += "--with-ssl='${STAGING_INCDIR}' --disable-fips"17:04
lpappsorry, that one.17:04
*** thaytan <thaytan!> has joined #yocto17:04
lpappNOTE: Executing RunQueue Tasks17:05
lpappNOTE: Tasks Summary: Attempted 568 tasks of which 555 didn't need to be rerun and all succeeded.17:05
Krzkhem: hi there, do you know how to add libstdc++ to uclibc based image?17:05
lpappbut I cannot find the stunnel binary anywhere ?17:05
lpappso why am I not getting errors if I cannot find that anywhere either?17:06
RPKrz: is there anything linking against it or you just want to add the library?17:07
lpappfile ./tmp/pkgdata/armv5te-linux-gnueabi/stunnel17:07
lpapp./tmp/pkgdata/armv5te-linux-gnueabi/stunnel: Quake I or II world or extension, 1953701946 entries17:07
lpappQuake ??17:07
* lpapp is full of confused17:07
*** darknighte is now known as darknighte_znc17:08
lpappstrange, I have those.17:10
lpappbut not the binary itself.17:10
lpappdo I need to have a do_install for get everything just right?17:10
KrzRP: I want library, since we develop some code in C++17:13
cfo215_bluelightning_, angstrom booted.  now to put my Qt app on it and see how well it plays with the touch screen.17:14
RPKrz: just add the lib to the IMAGE_INSTALL line?17:14
lpappseems stuff is built.17:14
KrzRP: Easy one. I thought there is some magic behind it.17:15
lpappbut how can I get everything into the right place?17:15
lpappi.e. including bin, not just the library17:15
KrzRP: don't I have to change uclibc flags?17:15
lpappI thought it would be automatic?17:15
RPKrz: I don't think so, IMAGE_INSTALL += "libstdc++" should work17:15
RPKrz: could be wrong though17:15
KrzRP: ok, will give it a go17:16
KrzRP: will let you know if it fails, thanks17:16
RPKrz: there is also libstdc++-dev in case you want that17:16
KrzRP: no, we just want to run binaries on target compiled outside17:17
lpapphere you can see the built stuff, and then the output into the sysroot:
lpapptf: rburton bluelightning_ ^17:20
lpappoh, I have ./tmp/deploy/rpm/armv5te/stunnel-4.56-r0.armv5te.rpm17:21
lpapphow can I check what it contains?17:21
*** belen1 <belen1!Adium@nat/intel/x-zisdtscqtclpymyi> has joined #yocto17:21
bluelightning_lpapp: one way is to look in packages-split/stunnel/17:21
*** bluelightning_ is now known as bluelightning17:21
lpappbluelightning: packages-split where ?17:21
bluelightninglpapp: under the workdir for the recipe, it's shown in your paste17:22
lpappwork ?17:22
lpappok, then all fine, thanks.17:22
lpappsubmit time, I guess.17:22
*** pidge <pidge!pidge@nat/intel/x-bmedpklaofbtxsjf> has joined #yocto17:22
lpappI guess it is ok if I submit it created in the read only repo.17:23
lpappwill there be problem out of that ?17:23
*** zecke <zecke!> has joined #yocto17:29
*** ka6sox is now known as ka6sox-away17:30
lpappsent against the write stuff; thanks again everyone involved.17:31
*** lpapp <lpapp!~lpapp@kde/lpapp> has left #yocto17:31
*** panda84kde <panda84kde!> has quit IRC17:32
*** smartin <smartin!> has joined #yocto17:35
*** nitink <nitink!~nitink@> has quit IRC17:36
*** smartin_ <smartin_!> has quit IRC17:37
*** mihai <mihai!~mihai@> has joined #yocto17:39
*** mulhern <mulhern!> has quit IRC17:42
*** belen1 <belen1!Adium@nat/intel/x-zisdtscqtclpymyi> has quit IRC17:44
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC17:46
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC17:58
*** ka6sox-away is now known as ka6sox18:03
*** smartin <smartin!> has quit IRC18:14
*** zaif <zaif!83ea1615@gateway/web/freenode/ip.> has quit IRC18:14
*** smartin <smartin!> has joined #yocto18:16
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto18:22
*** cfo215_ <cfo215_!> has quit IRC18:23
*** alex_kag <alex_kag!~alex_kag@> has joined #yocto18:33
*** sameo <sameo!~samuel@> has quit IRC18:37
*** Anusko <Anusko!~anusko@> has quit IRC18:41
*** Anusko <Anusko!~anusko@> has joined #yocto18:41
*** amarsman <amarsman!> has joined #yocto18:48
*** simar_ <simar_!~simar@> has quit IRC18:49
*** simar_ <simar_!~simar@> has joined #yocto18:49
*** smartin_ <smartin_!> has joined #yocto18:50
*** simar_ is now known as simar18:50
*** smartin <smartin!> has quit IRC18:51
*** mulhern <mulhern!> has joined #yocto18:52
*** alex_kag <alex_kag!~alex_kag@> has quit IRC18:52
*** alex_kag <alex_kag!~alex_kag@> has joined #yocto18:52
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto18:58
lpapphi, I wonder why packages do this all around: "${SOURCEFORGE_MIRROR}/tunctl/tunctl-${PV}.tar.gz18:58
lpapprather than using ${PN} for /tunctl/ etc18:59
*** swex__ <swex__!~swex@> has quit IRC18:59
fray${PN} can change when using multilib builds or native/nativesdk builds..19:00
fray${BPN} will not change, and likely could be used as a substitute19:00
lpappwell, the point is why hard code?19:01
*** swex__ <swex__!~swex@> has joined #yocto19:01
fraylikely so if someone renames the component the right file is still downloaded.. but it's convention vs necessity19:01
lpappwhy would you rename foo to bar?19:02
sgw_you can also you ${BP} which is ${BPN}-${PV}19:02
lpappsgw_: yeah, I know.19:02
frayno, someone might rename to so they could have multilib versions..19:03
lpappthe point is why there are so many hard coded recipes around19:03
lpappfray: that would not make so much sense19:03
fraylpapp, because that is how the original writer of the recipe did it.. and it doesn't really matter19:03
fraylpapp sure it does.. if I need to have both version 1.0 and 2.0 of a package (usually a library) thats the way you do it, via rename method..19:03
lpappI do not follow19:04
fraypoint is, there is nothing stopping a switch from explicit name to using BPN or BP or anything else.. it's just not what the authors of the individual recipes have done.19:04
lpappif you rename due to version ${BP} will just work (tm).19:04
*** mebrown <mebrown!> has joined #yocto19:04
*** zecke <zecke!> has quit IRC19:09
fraya partial example..19:09
fraywe have two copies of libpng that we want both installed.. one is called, the other is libpng12_1.2.50.bb19:09
frayif both were simply  then only one could be built and installed at a time..19:09
frayso there are cases where the recipe name is NOT the same as the package name being downloaded..  that used to be a lot more common then it is today..19:10
frayand yes, many of the cases could be changed to ${BP} and work just fine.. on an uprev, that would probably be an acceptable change19:10
*** tor <tor!~tor@> has quit IRC19:46
*** amarsman <amarsman!> has quit IRC19:46
*** amarsman <amarsman!> has joined #yocto19:47
*** amarsman <amarsman!> has quit IRC19:48
*** jeremiah <jeremiah!~jeremiah@> has quit IRC19:49
*** ant_home <ant_home!> has joined #yocto19:55
*** LiangC <LiangC!~Leon@> has joined #yocto20:03
*** madman-alex <madman-alex!~luccisa@nat/cisco/x-gfvoqrqrjnxzsarm> has quit IRC20:08
*** madman-alex <madman-alex!~luccisa@nat/cisco/x-acmswmzmkshpshoo> has joined #yocto20:12
lpappsgw_: so I have only a few days left to get u-boot in to make the update for the next release?20:18
sgw_lpapp: right to make 1.5 updates and feature freeze is Sunday Midnight PST.20:20
sgw_lpapp: your last version you withdrew because of some issues, right?20:20
lpappyes, me and the u-boot guys have had no any idea why fw-utils fails.20:21
lpappso I am about to update it leaving that out20:21
lpapponly u-boot and the mkutils20:21
lpappto be honest I do not even know what the fw-utils was meant to do20:21
lpappusually people need the u-boot image and the mkutils stuff to build the kernel for uImage20:22
lpappnothing more.20:22
lpappalso, someone had a minor nitpick.20:22
lpappsgw_: will there be any consolidated pull until Sunday?20:23
sgw_lpapp: There will be one tomorrow and then Monday after I do initial testing with everything that comes in for our build Tuesday20:25
lpappwell, I am pushing it now then20:25
lpappwithout fw-utils20:25
sgw_tommorows is based on what I am building now, so this will be in monday's likely.20:26
sgw_but I will review it after I get back from my run!20:26
lpappok for me if that does not mean it misses 1.520:26
lpappJaMa: ping20:34
lpappJaMa: meta-qt5 seems to be broken,
JaMalpapp: it looks you've downloaded only HTML redirect, right?20:36
JaMayou should try with newer meta-qt5..20:36
*** Rootert <Rootert!> has quit IRC20:37
*** RagBal <RagBal!> has quit IRC20:37
lpappwell, it is ten days old.20:37
JaMawell structure on was changed few days ago and was immediately updated in meta-qt5..20:38
*** Krz <Krz!c0c6972b@gateway/web/freenode/ip.> has quit IRC20:38
lpappsgw_: submitted, but it is bloated now due to the removals.20:39
*** eren <eren!~eren@unaffiliated/eren> has quit IRC20:40
*** Rootert <Rootert!> has joined #yocto20:42
*** RagBal <RagBal!> has joined #yocto20:42
*** mulhern <mulhern!> has quit IRC20:45
*** alex_kag <alex_kag!~alex_kag@> has quit IRC20:54
*** blitz00_ <blitz00_!~stefans@> has quit IRC20:55
reevedoes anyone one how to specify rpm encoding? means utf8 or ISOxxx"21:00
BCMMhow does the PACKAGECONFIG variable work? from reading libav's recipe, it looks like there is a mechanism to build it without libx11, but i don't know where/how to set it21:02
lpappBCMM: it is mapping to the config options.21:03
BCMMlpapp: yeah, i mean, where do i set it?21:04
lpappsee the description.21:04
lpappBCMM: you set it in the recipe, for instance .bbappend21:04
BCMMlpapp: so sorry, i thought i'd searched that page, but clearly i hadn't21:04
lpappthe description at the bottom in the glossary.21:05
BCMMlpapp: actually, that just describes what the variable does...21:05
BCMMlpapp: are you saying that editing the recipe is the correct way to change it?21:05
lpappwell, .bbappend to be precise, in your layer.21:06
lpappif you wanna modify an existing package... otherwise if it is new, I guess you can do in your .bb21:07
ndecBCMM: lpapp: well, generally the default packageconfig rely on DISTRO_FEATURES. especially for x11, i really think libav should not do that, and instead do something like here
BCMMndec: in this case, it says it can't build ffmpeg without x11 in DISTRO_FEATURES21:07
-YoctoAutoBuilder- build #140 of nightly-qa-systemd is complete: Failure [failed Building Images Running Sanity Tests Building Images_1 Running Sanity Tests_1 Building Images_2 Running Sanity Tests_2] Build details are at
ndecBCMM: why so?21:09
BCMMndec: sorry, i mean libav (which provides ffmpeg)21:09
ndecto me it says, i want x11 by default. if your distro does use it, make a .bbappend...21:09
BCMMndec: i guess libav's default PACKAGECONFIG doesn't rely on distro features...21:09
ndecmy point is that it should ;-)21:09
ndeclike every other recipe.21:09
BCMMyeah, i'll use a bbapend21:09
BCMMndec: i quote: PACKAGECONFIG ??= "bzip2 x264 x11"21:10
BCMMso the right way to modify a recipe from somebody else's layer is to make my own layer with a bbappend containing the changes?21:11
BCMMthanks, i'll do that21:11
lpappunless you plan to upstream it asap.21:11
BCMMi started a build with libx11 stuff before realising i probably didn't have to do that. is there a clean way to avoid that stuff ending up in my final image?21:11
lpappwhich might be the case in here, actually.21:11
BCMMlpapp: i'm a complete newbie to yocto/oe - guess you're talking about what ndec said, that it shouldn't want x11 by default when DISTRO_FEATURES doesn't have x11?21:12
-YoctoAutoBuilder- build #264 of nightly-x86-lsb is complete: Failure [failed Building Images Building Images_1] Build details are at
-YoctoAutoBuilder- build #260 of nightly-arm is complete: Failure [failed Building Images Running Sanity Tests Building Images_1 Building Toolchain Images Building Toolchain Images_1 Publishing Artifacts] Build details are at
*** bluelightning <bluelightning!> has joined #yocto21:15
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto21:15
BCMMlpapp: do i need to basically duplicate the directory structure to make the bbappend apply to the right recipe?21:16
ndecyou only need to make sure that the .bbappend is parsed.21:17
ndece.g. conf/layer.conf file must reference it.21:18
ndecand the file name of the .bbappend is important, it must be the same as .bb21:18
BCMMndec: "conf/layer.conf file must reference it" - the layer, or the specific bbappend?21:19
ndecto make your own layer, you need to create conf/layer.conf in your layer.21:19
ndecthat file has the list of all recipes in your layer (through regexp).21:20
ndecyou don't even need to make any directory structure in fact. you could have a flat directory of recipes, it's just a convention.21:20
ndeconly the filename is important, not the dirname.21:20
*** mulhern <mulhern!> has joined #yocto21:21
*** mulhern <mulhern!> has quit IRC21:25
sgw_lpapp: just wanted to check you have removed some older versions of u-boot, are you sure that none of the bsps need those specific versions?21:26
-YoctoAutoBuilder- build #272 of nightly-x32 is complete: Failure [failed Building Images Running Sanity Tests] Build details are at
-YoctoAutoBuilder- build #261 of nightly-multilib is complete: Failure [failed Building Images Running Sanity Tests Building Images_1 Running Sanity Tests_1 Building Images_2 Running Sanity Tests_2 Building Images_3 Running Sanity Tests_3 Building Images_4] Build details are at
*** amarsman <amarsman!> has joined #yocto21:32
*** sameo <sameo!samuel@nat/intel/x-tetlhmiwjemdbjlq> has joined #yocto21:36
-YoctoAutoBuilder- build #102 of minnow-lsb is complete: Failure [failed Building Images] Build details are at
-YoctoAutoBuilder- build #230 of nightly-fsl-ppc-lsb is complete: Failure [failed Building Images Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #258 of nightly-x86-64 is complete: Failure [failed Building Images Running Sanity Tests Building Toolchain Images Building Toolchain Images_1 Publishing Artifacts] Build details are at
*** davest <davest!Adium@nat/intel/x-wukbmwychpwmrgsr> has quit IRC21:47
reeveseebs: are you here?21:50
* seebs exits, pursued by a bear.21:50
seebs... yes21:50
reeve<seebs> lol ... still continue on yesterday's issue about snappy. I feel the generated rpm shouldn't be used with ascii decoder. Is there anyway to specify the encoding is utf8?21:51
seebsI don't know. Thinking about it, I think there's a couple of separate questions here. The first is what exactly is triggering the encoding check -- what text is it that has this non-ASCII value, and where does it come from?21:52
*** Jay7 <Jay7!jay@> has quit IRC21:52
seebsThen we get the question of whether to just try to work around it by editing something so there's no non-ASCII value happening, or to try to change the policy.21:53
seebsMy guess would be that the policy comes from one of two sources: The first would be "it just happens to be the default and no one ever thought about it before", the second is "there are specific things we care about which break if there are non-ASCII values in certain fields".21:53
reevenon-ASCII in that created rpm I don't know ... it's mystery to me too, but using utf8 decode shouldn't have that error at least21:54
reevei checked the package itself, it doesn't specify any encoding or that 0xc1 byte, it's hard to edit the rpm either21:54
seebsSo is this an error you get from a specific RPM which was successfully created? If so, maybe someone who knows more about RPM than I do could stare at it a bit to try to determine whether it's contrary to the spec or whether this is a bug in the utility that's throwing the error.21:55
reeveseebs: yes, it's from libsnappy.x.x.x.rpm created ...21:58
reeveerror happening while rpm trying to install it into rootfs tarball21:58
reeveI saw backends/rpm/ has different encodings defined like utf8 or iso-8859-1, just don't know how to specify it at the beginning21:59
*** walters <walters!walters@nat/redhat/x-kyuzbuehngamvuaq> has quit IRC22:03
-YoctoAutoBuilder- build #255 of nightly-x86-64-lsb is complete: Failure [failed Building Images] Build details are at
seebsI do not know this code at all, but it seems to me that what's happening involves the reader/writer being initialized around line 271 of, in which case just adding ENCODING = "utf8" right after the existing setting of ENCODING would likely show you a possibly-different set of behaviors.22:04
-YoctoAutoBuilder- build #273 of nightly-mips-lsb is complete: Failure [failed Building Images Building Images_1] Build details are at
seebsIt appears that it's trying to determine the "preferred" encoding, and defaulting to ASCII. Without adding some classy debugging prints, I can't tell which one of those is happening. It looks like it might well be harmless to try changing it.22:06
seebsThis does look intentional though, so it may well be that tweaking that will result in strange failures elsewhere.22:07
reeveseebs: ok, I'll give it try but it's just some concept prove, the real fix might need to be fine tuned22:08
seebsYou could also, probably, change reader(open(rpmoutpath)) to reader(open(rpmoutpath), errors = "ignore")22:08
reeveseebs: that sounds better22:09
-YoctoAutoBuilder- build #234 of nightly-fsl-arm is complete: Failure [failed Building Images Building Toolchain Images Building Toolchain Images_1 Building Images_1 Building Images_2 Publishing Artifacts] Build details are at
seebsHmm. This has been this way forever, it seems.22:13
*** zenlinux <zenlinux!> has quit IRC22:14
seebsOkay, this code appears to come from revision 393 of smartpm, and the revision log is "Changed some bits in the rpm output parsing trying to solve encoding bugs." From 2005-01-19.22:16
reeveseeb: it went rhough with the change. To fix it permanently, shall I directly patch python for
seebsI would not recommend that without finding out why this was set up this way. The key point seems to be revision 389, "Use converting codecs when grabbing rpm output through sys.std{out,err}."22:18
*** Jay7 <Jay7!jay@> has joined #yocto22:19
seebsSo if you can find out why that change was needed, or what it was trying to solve, that'll give you a good starting point in figuring out what the "right" solution is.22:19
seebsI will say... My basic intuition is that it is almost certainly wrong for the interpretation of RPM output by smartpm to be contingent on the user's locale settings.22:19
reevealright, fair22:19
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC22:19
-YoctoAutoBuilder- build #261 of nightly-ppc is complete: Failure [failed Building Images Running Sanity Tests Building Images_1 Building Toolchain Images Building Toolchain Images_1 Publishing Artifacts] Build details are at
*** smartin <smartin!> has joined #yocto22:25
BCMMi've managed to successfully build an image (rpi-hwup-image). what's the correct way of doing it again, with an extra package (mpd) included? if i just do bitbake mpd then bitbake rpi-hwup-image again, will it be included in the new image?22:30
ndecBCMM: no.22:31
ndecthe package would be built, but not added in the image.22:31
ndecto add a package in an image, you need to explicitely request that.22:32
BCMMndec: so what exactly does the sysroot represent?22:34
*** seebs <seebs!> has quit IRC22:34
ndecit's where each package puts .h files and other development files.22:34
*** JimBaxter <JimBaxter!> has quit IRC22:34
ndecso that when building B, if B needs .h files from A, it will pick them there.22:35
ndecassuming A has 'installed' the .h files properly.22:35
BCMMah, it's somewhere for include paths, not install paths, to exist?22:35
ndecthe .h files are not used from their orginal $WORKDIR22:35
ndecwell, 'native' tools go there too for example.22:36
BCMMand it's only two lines to make my own image... bitbake seems to make basing stuff on other stuff pretty easy22:36
ndecon the shoulders of giants ;-)22:37
*** cbab <cbab!> has joined #yocto22:38
*** pidge <pidge!pidge@nat/intel/x-bmedpklaofbtxsjf> has quit IRC22:45
*** Guest79797 <Guest79797!> has quit IRC22:47
*** mulhern <mulhern!> has joined #yocto22:53
*** Hari_ <Hari_!83e6bf9e@gateway/web/freenode/ip.> has joined #yocto22:54
Hari_I am trying to make changes to u-boot and then recompile u-boot source. It looks like it is not taking any of the changes and it is generating the same u-boot binary all the time. My changes are not reflected in the u-boot binary22:56
-YoctoAutoBuilder- build #239 of nightly-oecore is complete: Success [build successful] Build details are at
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC22:59
*** smartin <smartin!> has quit IRC23:16
Hari_Can anyone help me with this>23:17
sgw_Hari_: with what?23:25
Hari_u-boot is not compiling properly, my changes are not reflected in the binary23:25
Hari_I did a clean build23:26
kergothtotally OT, but anyone had success with the rt2800usb driver? getting failed to init hw with my rt2870 adapter23:28
mranostaykergoth: pastebin?23:29
*** JaMa <JaMa!> has quit IRC23:30
kergothgah, ejected and re-inserted, and now getting a spinlock lockup, down for the count..23:31
* kergoth glares at his board23:32
*** Hari_ <Hari_!83e6bf9e@gateway/web/freenode/ip.> has quit IRC23:35
*** roric <roric!> has joined #yocto23:36
*** fitzsim <fitzsim!~user@nat/cisco/x-wqfrvsvcxwfvodjr> has quit IRC23:36
*** fitzsim <fitzsim!~user@nat/cisco/x-xpoqnndwjdfihzat> has joined #yocto23:36
*** musdem <musdem!> has joined #yocto23:43
*** ant_home <ant_home!> has quit IRC23:46
*** hollisb <hollisb!> has quit IRC23:51
*** fitzsim <fitzsim!~user@nat/cisco/x-xpoqnndwjdfihzat> has quit IRC23:57
*** fitzsim <fitzsim!~user@nat/cisco/x-tuzmlaanwvmtfddj> has joined #yocto23:57
*** mulhern <mulhern!> has quit IRC23:57

Generated by 2.11.0 by Marius Gedminas - find it at!