Thursday, 2014-07-24

*** fray_ <fray_!~mhatle@> has quit IRC00:17
*** sameo <sameo!~samuel@> has quit IRC00:20
*** coldnew <coldnew!> has quit IRC00:22
-YoctoAutoBuilder- build #181 of nightly-oecore is complete: Success [build successful] Build details are at
*** LCyrin_ <LCyrin_!~lynn@> has joined #yocto00:58
LCyrin_who's here?00:59
*** LCyrin_ is now known as lcyrin00:59
lcyrinaaahhhh wrong chat01:00
*** lcyrin <lcyrin!~lynn@> has left #yocto01:00
*** coldnew <coldnew!~user@> has joined #yocto01:01
*** Squix <Squix!> has joined #yocto01:03
*** manuel_ <manuel_!> has quit IRC01:07
*** manuel_ <manuel_!> has joined #yocto01:08
*** alimon <alimon!~alimon@> has joined #yocto01:09
*** manuel__ <manuel__!> has joined #yocto01:46
*** manuel_ <manuel_!> has quit IRC01:47
*** manuel__ is now known as manuel_01:47
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has quit IRC01:52
*** sjolley <sjolley!~sjolley@> has joined #yocto01:54
*** sjolley <sjolley!~sjolley@> has quit IRC01:57
*** sjolley <sjolley!~sjolley@> has joined #yocto01:57
*** staylor <staylor!> has joined #yocto02:02
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has joined #yocto02:04
*** fray <fray!> has quit IRC02:07
*** fray <fray!> has joined #yocto02:09
*** fray_ <fray_!~mhatle@> has joined #yocto02:13
*** manuel_ <manuel_!> has quit IRC02:20
*** Sput <Sput!~sputnick@quassel/developer/sput> has quit IRC02:47
*** Sput <Sput!~sputnick@quassel/developer/sput> has joined #yocto02:48
*** staylor <staylor!> has quit IRC03:06
*** ccube <ccube!> has quit IRC03:28
*** ccube <ccube!> has joined #yocto03:36
*** coldnew <coldnew!~user@> has quit IRC03:45
*** coldnew <coldnew!~user@> has joined #yocto03:47
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has quit IRC03:51
*** coldnew <coldnew!~user@> has quit IRC03:52
*** coldnew <coldnew!~user@> has joined #yocto03:52
*** coldnew <coldnew!~user@> has quit IRC03:58
*** coldnew <coldnew!~user@> has joined #yocto04:00
*** moto-timo <moto-timo!~moto-timo@> has quit IRC04:15
*** Crofton <Crofton!> has joined #yocto04:27
*** moto-timo <moto-timo!~moto-timo@> has joined #yocto04:28
*** Crofton <Crofton!> has quit IRC04:46
*** [Sno] <[Sno]!~Sno]> has quit IRC04:55
*** coldnew <coldnew!~user@> has quit IRC04:56
*** behanw <behanw!> has quit IRC05:03
*** coldnew <coldnew!~user@> has joined #yocto05:11
*** behanw <behanw!> has joined #yocto05:18
*** alexhairyman <alexhairyman!> has quit IRC05:33
*** cbzx <cbzx!> has joined #yocto05:35
*** cbzx <cbzx!> has quit IRC05:38
*** TobSnyder <TobSnyder!> has joined #yocto05:49
*** Jay7 <Jay7!jay@> has quit IRC05:50
*** Jay7 <Jay7!> has joined #yocto05:58
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC06:12
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto06:14
*** coldnew <coldnew!~user@> has quit IRC06:17
*** dvhart <dvhart!~dvhart@> has joined #yocto06:25
*** pidge <pidge!> has joined #yocto06:26
*** coldnew <coldnew!~user@> has joined #yocto06:26
*** elmi82 <elmi82!> has joined #yocto06:28
*** dvhart <dvhart!~dvhart@> has quit IRC06:34
*** alimon <alimon!~alimon@> has left #yocto06:35
*** diego_r <diego_r!> has joined #yocto06:36
*** ftonello <ftonello!> has quit IRC06:41
*** ftonello <ftonello!> has joined #yocto06:42
*** ftonello <ftonello!> has quit IRC06:48
*** ftonello <ftonello!> has joined #yocto06:48
*** embed <embed!~embed@> has joined #yocto06:49
embedHi yocto..06:49
*** roric <roric!> has joined #yocto06:50
*** eballetbo <eballetbo!> has joined #yocto06:53
embedHi yocto...I am trying to interface camera with beaglebone with support of mplayer but i am getting paste bin error how to rectify this error any one can help to resolve this.06:55
*** diego_r <diego_r!> has joined #yocto06:57
*** [Sno] <[Sno]!~Sno]> has joined #yocto06:57
*** ant_work <ant_work!> has joined #yocto06:59
*** TuTizz <TuTizz!~TuTizz@> has joined #yocto06:59
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has joined #yocto06:59
*** tasslehoff <tasslehoff!> has joined #yocto07:02
*** roric <roric!> has quit IRC07:04
*** embed <embed!~embed@> has quit IRC07:11
*** manuel__ <manuel__!> has joined #yocto07:12
*** embed <embed!~embed@> has joined #yocto07:16
*** mckoan|away is now known as mckoan07:17
mckoangood morning07:17
*** ftonello <ftonello!> has quit IRC07:19
*** ftonello <ftonello!> has joined #yocto07:20
*** freanux <freanux!~freanux@unaffiliated/freanux> has quit IRC07:24
*** andyj25 <andyj25!d23d430c@gateway/web/freenode/ip.> has joined #yocto07:26
andyj25Hi everyone07:27
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:28
*** florian_kc is now known as florian07:29
andyj25I'm getting this error when I build a custom image:07:31
andyj25arm-poky-linux-gnueabi-ld: unrecognized option '-Wl,-O1'07:31
andyj25anybody have an idea about where that originates?07:31
*** Crofton <Crofton!> has joined #yocto07:33
embedHi please any one help me to solve this camera issue.07:38
*** fray <fray!> has quit IRC07:44
*** Crofton <Crofton!> has quit IRC07:45
*** fray <fray!> has joined #yocto07:45
ant_workandyj25: which recipe is failing? What was it building? This is an option for CC (gcc) to be passed to the linker LD07:49
*** freanux <freanux!~freanux@unaffiliated/freanux> has joined #yocto07:50
*** Crofton <Crofton!> has joined #yocto07:50
andyj25Hi ant_work.  I made my own layer, and a recipe for a very simple image.07:51
andyj25When i do bitbake myimage, it fails during do_compile() saying "unrecognized option '-Wl,-O1'"07:52
andyj25is it something to do with LDFLAGS?07:52
andyj25I think the "-Wl, -O1" options come from poky/meta/conf/bitbake.conf07:53
*** freanux <freanux!~freanux@unaffiliated/freanux> has quit IRC07:53
andyj25should i be trying to overwrite that from my image recipe file?07:53
ant_workgcc -Wl,foo,bar  ->  ld foo bar07:53
ant_workyou must have changed LDFLAGS or EXTRA_OEMAKE07:54
ant_workin one recipe07:55
*** Crofton <Crofton!> has quit IRC07:55
ant_workwhich one is failing? the image itself does not compile anything07:55
andyj25the image recipe builds a bunch of libraries (which succeed) then it tries to build another recipe which I wrote07:57
andyj25that recipe is PJSIP07:57
andyj25and that's where it fails compiling07:57
andyj25I haven't written an LDFLAGS or EXTRA_OEMAKE in that recipe file07:59
*** sameo <sameo!~samuel@> has joined #yocto07:59
ant_workplease check the build logs and verify CFLAGS and LDFLAGS07:59
ant_workof that recipe08:00
andyj25OK. one moment.08:00
andyj25that one right?08:00
*** sameo <sameo!~samuel@> has quit IRC08:01
andyj25my temp/run.do_compile  says --->    export TARGET_LDFLAGS="-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed"08:03
andyj25and also  ---> export LDFLAGS="-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed"08:04
*** embed <embed!~embed@> has quit IRC08:04
*** kroon <kroon!> has quit IRC08:06
ant_workwhat is LD?08:06
ant_workthis would only work if you use gcc for linking08:07
ant_workI suspect you should verify the Makefile08:08
*** kroon <kroon!> has joined #yocto08:08
ant_workandyj25: I've never built this source. Seems it was an oe-classic recipe08:10
andyj25LD is this ---> LD="arm-poky-linux-gnueabi-ld --sysroot=/home/andrew/yocto-imx6/build/tmp/sysroots/imx6qsabresd"08:12
andyj25so the Makefile for the source code I'm compiling can also modify LDFLAGS?08:12
*** freanux <freanux!~freanux@unaffiliated/freanux> has joined #yocto08:13
andyj25Thanks for the pointer to that sflphone recipe.. i'm looking into it for clues08:17
*** sameo <sameo!samuel@nat/intel/x-eehubvyzdyqazbin> has joined #yocto08:18
ant_workandyj25: sorry, phone call08:19
ant_workyou should normally use the default flags passed by OE/Yocto toolchain08:19
ant_worksome sourcess though need to be patched or you can adjust in the recipe i.e. with EXTRA_OEMAKE08:20
andyj25could it be possible that the default flags don't work with that cross-compiler?08:21
andyj25or do you think the defaults are being overwritten by something08:21
ant_workplease check the logs of another recipe, you'll see08:21
*** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@> has quit IRC08:22
*** LocutusOfBorg1 <LocutusOfBorg1!~Gianfranc@> has joined #yocto08:25
andyj25alright. thanks for the tips.08:28
andyj25so you mean.. i should compile another recipe which works08:28
andyj25and then check its logs?08:28
*** manuel__ <manuel__!> has quit IRC08:31
ant_workyes, as general case every recipe should use the pre-defined  ${CC} ${CFLAGS} ${LDFLAGS}08:33
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto08:33
bluelightningmorning all08:36
mckoanhi bluelightning, all08:36
bluelightninghi mckoan08:36
ant_workgm bluelightning08:36
bluelightninghi ant_work08:37
ant_workandyj25: the story is a bit long, per default we pass '-e' to make08:41
ant_work"Give variables taken from the environment precedence over variables from makefiles"08:41
ant_workyou could try redefining the full EXTRA_OEMAKE08:42
andyj25ohh.. so Yocto passes "-e" by default?08:43
ant_workyes, check bitbake.conf08:43
ant_workbut there are exceptions, I can't find a better documents offhand08:44
ant_workcheck this old thread pls08:44
*** roric <roric!~roric@> has joined #yocto08:51
andyj25ok thanks : )08:52
*** g1zer0 <g1zer0!> has joined #yocto08:53
*** embed <embed!~embed@> has joined #yocto08:53
embedHi please any one help me to solve this camera issue.08:53
embed Hi yocto...I am trying to interface camera with beaglebone  with support of mplayer but i am getting paste bin error how to rectify this error any one can help to resolve this.08:54
embedHi please any one help me to solve this camera issue.08:54
*** belen <belen!Adium@nat/intel/x-ekejpjtkvmtacobb> has joined #yocto09:03
*** tmpsantos <tmpsantos!tmpsantos@nat/intel/x-objqnqxmfhxkjhys> has joined #yocto09:13
-YoctoAutoBuilder- build #180 of nightly-fsl-ppc-lsb is complete: Success [build successful] Build details are at
*** TheLost <TheLost!~TheLost@> has joined #yocto09:32
TheLostHi all =)09:32
andyj25ant_work, I found a thread from the mailing list which describes exactly the problem i'm getting09:41
andyj25According to kernel.bbclass, setting EXTRA_OEMAKE = ""  is one way to get rid of the "-e" option, but that didn't work for me09:42
*** fray <fray!> has quit IRC09:52
*** fray <fray!> has joined #yocto09:54
*** belen <belen!Adium@nat/intel/x-ekejpjtkvmtacobb> has quit IRC09:54
*** hsychla_ <hsychla_!> has quit IRC09:56
ant_workandyj25: is that source?
*** belen <belen!Adium@nat/intel/x-naayadgboaektxqi> has joined #yocto09:58
andyj25that link is a fork09:59
andyj25i'm using the official source code10:00
ant_workok, it is an auto-tooled recipe10:00
andyj25but anyway, it looks similar to that10:00
ant_workthis implies EXTRA_OEMAKE = ""10:00
ant_workbut that's not th epoint here10:00
ant_workthe recipe offers an hook, see user.mak.sample10:01
*** phantoxe <phantoxe!> has joined #yocto10:04
ant_workyou can probably patch that10:07
ant_workyou have to force  $(CC) $(LDFLAGS)10:07
*** coldnew` <coldnew`!> has joined #yocto10:24
*** coldnew <coldnew!~user@> has quit IRC10:28
andyj25hmm.. sorry but i don't quite understand10:30
andyj25does that mean i should make a user.mak file?10:30
andyj25in the pjsip source?10:30
*** henriknj <henriknj!> has joined #yocto10:31
*** manuel__ <manuel__!> has joined #yocto10:35
*** Squix <Squix!> has quit IRC10:35
*** fray <fray!> has quit IRC10:44
*** fray <fray!> has joined #yocto10:45
*** phantoxe <phantoxe!> has quit IRC10:47
*** AlexVaduva <AlexVaduva!c1ca1642@gateway/web/freenode/ip.> has joined #yocto10:47
*** phantoxe <phantoxe!> has joined #yocto10:52
*** Squix <Squix!> has joined #yocto10:52
*** motzer_ <motzer_!574f4685@gateway/web/freenode/ip.> has joined #yocto11:09
motzer_hey guys11:09
motzer_I've gtot another question. Should be really easy for you - if I want to clean up be deploay dir completely without touching any sources or fetched/compiled data while the build process, which bitbake -c clean command can I use to get all of it together11:11
*** coldnew`` <coldnew``!~user@> has joined #yocto11:11
*** coldnew` <coldnew`!> has quit IRC11:12
motzer_by now I just removed my /tmp dir to get back to a clean environment11:13
motzer_is it better to use a bitbake cmd ?11:13
bluelightningwhat's your reason for wanting to do the cleaning?11:17
*** vikko_ <vikko_!d4d9cc29@gateway/web/freenode/ip.> has joined #yocto11:23
motzer_just to delete all images which just were tests while the developing process, I allways add a package or a recipe and test it if it works I go on. So just not to mix images up because de date code is no really very clearly represented11:27
motzer_no special reason just for the overview =)11:27
RPJaMa: is that a record low for failed builds in world?11:35
*** msm` <msm`!> has joined #yocto11:41
ant_workandyj25: sorry but I cannot check the sources right now (nor the recipe you're building ;). You have to investigate the direct invocation to LD. Possible test: 1) set CFLAGS += LDFLAGS and  LDFLAGS="" in the recipe. This way LD should not protest. 2) Fix the sources, probably one Makefile 3) patch the autoconfig files to add LDFLAGS to CFLAGS like 1)11:41
ant_workandyj25: there are som eold recipes for oe-classic around, check how they did11:42
*** msm <msm!> has quit IRC11:44
andyj25thanks for all the tips!11:44
ant_worktry patching the user.mak in that way at first11:45
ant_workand verify the recipe inherits autotools11:45
ant_workbtw, this seems rather complicated recipe, with different flags for lib and apps11:46
ant_workit is not hello-world ;)ù11:46
*** coldnew`` <coldnew``!~user@> has quit IRC11:49
*** fray <fray!> has quit IRC11:53
*** fray <fray!> has joined #yocto11:55
bluelightningmotzer_: generally you can just delete the old images, there isn't a command to delete them on demand12:03
bluelightningmotzer_: however you can set RM_OLD_IMAGE = "1" in which case old images will be deleted automatically each time a new one is created12:03
JaMaRP: no, 2014-05-15 was better :)12:05
*** Squix <Squix!> has quit IRC12:06
RPJaMa: ah, true :). Its getting close again at least12:09
JaMaRP: and abiword + libssh were blacklisted because of libgrcypt upgrade since then
ant_workJaMa: hi. Unfair of you doubling the klibc-utils warning checking both 2.0.3 and 2.0.4 :p12:09
JaMaRP: thanks for all the patches you've sent12:09
RPJaMa: np, its good to see its helped a bit :)12:10
JaMaant_work: you'll get double kudos if you fix it :)12:10
RPJaMa: floating dependencies next I guess...12:10
* RP keeps fixing the oe-core ones he sees in local builds12:10
JaMaRP: I've included all recipes reported by insane_qa to next test-dependencies build to see why we're seeing different results from these 2 checks12:11
ant_workRP: I'm scared by that /bin/bash issue revealed by Robert's testing12:11
RPant_work: Sadly, I'm not, I've known we've had some issues there for a while. Its why bugs were opened and people are looking at it12:11
ant_workhe is using bash on his Ubuntu 12.04 afais12:11
JaMaRP: the sad part is that we're both quite busy with other patches, it would be great to get more fixes from people actually using these recipes on target12:12
ant_workRP: xz uses a posix-shell.m412:12
RPJaMa: yes, that is sad and frustrating12:12
RPant_work: I know I had to do some nasty things with libtool to resolve the problems there12:13
JaMaand I'm still a bit concerned about that foreign patch introducing new COPYING files with GPLv3 :/12:13
RP(it coded into the script whether /bin/sh handled bashisms or not)12:14
ant_workI've read about a checkbashism tool12:14
JaMabut I've finally fixed all our internal components to at least not fail in do_configure12:14
ant_workmaybe we could try to sanitize *some* scripts12:14
RPJaMa: in some ways it is better to expose this problem and deal with it rather than hiding it though...12:15
RPJaMa: you can't guarantee software would always be built by our hacked automake12:15
JaMayes, but sometimes it's exposed in "hidden" way :)12:15
RPJaMa: its far from perfect, I agree12:15
*** andyj25 <andyj25!d23d430c@gateway/web/freenode/ip.> has quit IRC12:16
*** andyj25 <andyj25!d23d430c@gateway/web/freenode/ip.> has joined #yocto12:17
ant_workJaMa: bluelightning: pls push klibc 2.0.4 so I can send the fix on top of it12:18
*** TRoGd0R <TRoGd0R!> has joined #yocto12:18
*** manuel__ <manuel__!> has quit IRC12:18
JaMaant_work: rebase your change on top of master-next12:19
ant_workmabe later today I'll send the quick fix then I'll see if a refactoring is possible12:19
JaMaant_work: I plan to push it after next build, if you send patch on top of it I'll include it as well12:19
ant_workthe split klibc / klibc-utils is OE specific. It is a single package in debian12:19
ant_work(we add klcc-cross and the -static utils)12:20
TRoGd0RI have been bitbakin qt 5.2.1 in my build without any issue until I added qtquickcontrols-qmlplugins.  Now I get this error: * opkg_install_cmd: Cannot install package qtquickcontrols-qmlplugins.  Is there a known issue with this?  Can someone point me to a patch I can apply?  Thanks!12:20
ant_workJaMa: ok12:20
JaMaTRoGd0R: check which packages were created by qtquickcontrols12:21
TRoGd0RHow do I do that?12:21
JaMaTRoGd0R: it could be empty (not created) with your qtbase's PACKAGECONFIG12:21
TRoGd0RSorry I am new to this12:21
JaMaeasiest would be find tmp-eglibc/deploy/ipk -name \*quickc\*12:22
JaMamore correct would be to check qtquickcontrols WORKDIR packages-split directory12:23
ant_workRP: about the tar packages, note there are layers carrying around "deltask do_package_write_tar"12:23
ant_work(maybe just meta-initramfs hopefully)12:23
RPant_work: it shouldn't cause any harm even if we do delete it12:25
ant_workand I was just hit by the changes to insane.bbclass adding do_package_qa... ;)12:26
ant_workJaMa: I'll send the possible fix for the kexecboot kernel together ^^12:27
RPant_work: the joys of maintainership! ;-)12:27
RPant_work: the improvements to dependency validation should make that worthwhile12:27
ant_workit would be easy if it were possible to grep on *all* layers ;)12:27
bluelightningant_work: if you want to add some kind of full-text-indexing + search to the layer index, please do ;)12:29
ant_workI can imagine it's mysql structure ;)12:30
bluelightningthe app uses django, but you'd have to add some kind of full-text-indexing engine to it12:32
bluelightningof which there are many off-the-shelf solutions12:32
embed Hi yocto...I am trying to interface camera with beaglebone  with support of mplayer but i am getting paste bin error how to rectify this error any one can help to resolve this.12:33
embedHi please any one help me to solve this camera issue.12:33
TRoGd0RIt took awhile becuase I searched the entire build directory, I didn't have a tmp-eglibc directory12:33
bluelightningembed: this isn't really the forum for such problems I'm afraid; you should try asking somewhere related to the software you are having problems with (mplayer?)12:34
ant_workbluelightning: I mean you should have every file stored as text in a field, then you can perform string search on it12:35
ant_workbluelightning: I guess layers-index just keeps th elinks12:35
bluelightningant_work: that's pretty slow to search though, you really need a proper index12:36
bluelightningant_work: that's correct12:36
ant_workbluelightning: there are powerful functions12:36
*** embed <embed!~embed@> has quit IRC12:37
*** dmoseley <dmoseley!> has quit IRC12:41
ant_workJaMa: more about /, do_package_qa12:45
ant_workthe exposed task reveals that qemux86 is trying to use 3.14 (preferred) kernel while building a 3.10 recipe12:46
ant_workIt could be interesting to understand why before silencing the QA12:46
*** zeddii <zeddii!~ddez@> has quit IRC12:55
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC12:56
*** bluelightning <bluelightning!~paul@> has joined #yocto13:00
*** bluelightning <bluelightning!~paul@> has quit IRC13:00
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto13:00
*** zeddii <zeddii!~ddez@> has joined #yocto13:01
*** phantoxe <phantoxe!> has quit IRC13:02
-YoctoAutoBuilder- build #177 of nightly-fsl-ppc is complete: Success [build successful] Build details are at
*** phantoxe <phantoxe!> has joined #yocto13:04
JaMaTRoGd0R: you probably don't have icu enabled in qtbase13:09
TRoGd0RI do I enable that?13:10
TRoGd0RAll I did was to add qtquickcontrols-qmlplugins to my IMAGE_INSTALL_append in local.conf13:11
TRoGd0RI didn't know there was another step :)13:11
TRoGd0RSo I just went into my qtbase_5.2.1.bbappend file and I see that I have this line DEPENDS += "icu libgles-omap3"13:13
JaMathat isn't correct, icu should be enabled in PACKAGECONFIG13:15
JaMaread meta-qt5 wiki and qtbase.inc13:15
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC13:22
LocutusOfBorg1Hi, does anybody know how to make my mouse work in yocto?13:22
LocutusOfBorg1[  1027.105] (WW) Warning, couldn't open module evdev13:22
LocutusOfBorg1[  1027.105] (II) UnloadModule: "evdev"13:23
LocutusOfBorg1[  1027.105] (II) Unloading evdev13:23
LocutusOfBorg1[  1027.105] (EE) Failed to load module "evdev" (module does not exist, 0)13:23
LocutusOfBorg1[  1027.105] (EE) No input driver matching `evdev'13:23
LocutusOfBorg1the architecture is armhf13:23
TRoGd0RI see there is a line like this in PACKAGECONFIG[icu] = "-icu,-no-icu,icu" and there is a comment about how qtwebkit needs icu but I am not seeing how I should do anything different than what I am doing.  Sorry for my n00bishness13:23
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto13:23
*** rcw <rcw!~rwoolley@> has joined #yocto13:25
*** coldnew <coldnew!> has joined #yocto13:25
ndecTRoGd0R: you need PACKAGECONFIG_append = " icu" in your .bbappen13:25
JaMaLocutusOfBorg1: install xf86-input-evdev13:25
TRoGd0ROK cool let me try that, thanks!13:26
-YoctoAutoBuilder- build #176 of nightly-fsl-arm-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at
LocutusOfBorg1thanks jackmitchell13:34
LocutusOfBorg1thanks JaMa13:34
*** rcw <rcw!~rwoolley@> has quit IRC13:43
*** dmoseley <dmoseley!> has joined #yocto13:44
*** blitz00 <blitz00!~stefans@> has joined #yocto13:49
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has joined #yocto13:49
*** tasslehoff <tasslehoff!> has quit IRC13:53
*** rcw <rcw!~rwoolley@> has joined #yocto14:06
*** vikko_ <vikko_!d4d9cc29@gateway/web/freenode/ip.> has quit IRC14:20
*** dmiller_ <dmiller_!> has joined #yocto14:20
*** T0mW <T0mW!> has joined #yocto14:21
TheLostI’m preparing Yocto build for a custom AM335x Texas Instruments board, what do I have to do with mux.h and pinmux.h from the PinMux utility?14:26
TheLostI changed mux.h in kernel’s arch/arm/mach-omap/14:26
TheLostBut i don’t understand how/where to include the pinmux.h14:26
TheLostany suggestion?14:26
*** wotte <wotte!~textual@> has joined #yocto14:31
*** tmpsantos <tmpsantos!tmpsantos@nat/intel/x-objqnqxmfhxkjhys> has quit IRC14:31
motzer_bluelightning: thanks good information =)14:32
*** motzer_ <motzer_!574f4685@gateway/web/freenode/ip.> has left #yocto14:32
*** munch <munch!> has joined #yocto14:33
TRoGd0RI updated my qtbase_5.2.1.bbappend and removed icu from DEPENDS and added it to PACKAGECONFIG_append.  I am still getting the same error, here is the build output, any other ideas?
*** wotte <wotte!~textual@> has quit IRC14:34
*** wotte <wotte!~textual@> has joined #yocto14:35
*** rcw <rcw!~rwoolley@> has quit IRC14:37
*** motzer <motzer!574f4685@gateway/web/freenode/ip.> has quit IRC14:41
*** sjolley <sjolley!~sjolley@> has quit IRC14:45
ant_workzeddii: so linux-yocto-dev is at 3.16-rc614:47
kroonTRoGd0R, make sure you have PACKAGECONFIG[accessibility] enabled14:49
*** WarheadsSE <WarheadsSE!~WarheadsS@> has joined #yocto14:50
zeddiiant_work. wow. I pushed that about 5 mins ago!14:50
WarheadsSEHey all. Having trouble locating the problem: kernel modules aren't getting stripped. (Dora)14:51
zeddiiI'm testing yaffs2 now. I didn't have it in my first build cycles, I spent a lot of time fighting with lttng.14:51
* zeddii finishes up his pull request14:51
*** Doug_ <Doug_!c0373624@gateway/web/freenode/ip.> has joined #yocto14:53
TRoGd0Rkroon: How do I do that?14:53
*** g1zer0 <g1zer0!> has quit IRC14:54
kroonTRoGd0R, PACKAGECONFIG_append = "accessibility" in the .bbappend. Or you can do PACKAGECONFIG_append_pn-qtbase = "accessibility" in your distro.conf14:55
*** alimon <alimon!> has joined #yocto14:55
kroon_append = " accessibility", with the prepended blank space, just to be sure..14:56
TRoGd0RCool I just updated to this PACKAGECONFIG_append = " icu accessibility"14:58
TRoGd0Rshould that work?14:58
*** Crofton <Crofton!> has joined #yocto14:59
ant_workzeddii: some patches have been hit by /drivers/video -> drivers/video/fbdev14:59
ndecTRoGd0R: yes14:59
TRoGd0Rok it's building now14:59
kroonTRoGd0R, icu is in there by default, but otherwise yes14:59
kroonoh, its not15:01
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto15:02
lpapphello, is Phil Blundell lurking here ?15:02
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has quit IRC15:03
lpapp -> I wonder why the sticky bit was deemed useful in busybox a bit more than four years ago?15:03
lpapp(isn't it a kind core security hole?)15:04
*** wotte <wotte!~textual@> has quit IRC15:06
*** ant_work <ant_work!> has quit IRC15:08
*** kroon <kroon!> has quit IRC15:09
*** rcw <rcw!~rwoolley@> has joined #yocto15:16
*** wotte <wotte!~textual@> has joined #yocto15:20
JaMaRP: I'm sorry to see that the NEEDINFO task about multi-machines builds fall again on you, but on the other hand I'm glad that you'll bring other view on this (so that official Yocto documentation doesn't just copy how I do multi-machine build)15:23
*** elmi82 <elmi82!> has quit IRC15:25
*** dmoseley <dmoseley!> has quit IRC15:26
*** staylor <staylor!> has joined #yocto15:28
*** roric <roric!~roric@> has quit IRC15:30
*** wotte <wotte!~textual@> has quit IRC15:38
RPJaMa: Its a case of "someone" needing to put info together and you/I appear to be the only people who can :/15:38
*** wotte <wotte!~textual@> has joined #yocto15:43
*** Crofton <Crofton!> has quit IRC15:54
*** wotte <wotte!~textual@> has quit IRC15:56
*** sjolley <sjolley!sjolley@nat/intel/x-whdjyusqijcbwbfc> has joined #yocto15:56
*** kevin_t1 <kevin_t1!~Thunderbi@> has quit IRC15:58
-YoctoAutoBuilder- build #176 of nightly-world is complete: Failure [failed BuildImages] Build details are at
*** kevin_t <kevin_t!~Thunderbi@> has joined #yocto16:02
*** sjolley <sjolley!sjolley@nat/intel/x-whdjyusqijcbwbfc> has quit IRC16:10
*** Nitin <Nitin!~nakamble@> has joined #yocto16:16
*** wotte <wotte!~textual@> has joined #yocto16:17
*** Crofton <Crofton!> has joined #yocto16:22
*** [Sno] <[Sno]!~Sno]> has quit IRC16:26
*** mckoan is now known as mckoan|away16:35
*** Crofton <Crofton!> has quit IRC16:35
*** Crofton <Crofton!> has joined #yocto16:35
*** kevin_t <kevin_t!~Thunderbi@> has quit IRC16:38
*** kevin_t <kevin_t!~Thunderbi@> has joined #yocto16:39
*** dmoseley <dmoseley!> has joined #yocto16:40
*** wotte <wotte!~textual@> has quit IRC16:46
*** lpapp <lpapp!~lpapp@kde/lpapp> has left #yocto16:47
*** sjolley <sjolley!sjolley@nat/intel/x-cogmhnxoklwytkgi> has joined #yocto16:47
*** j6V6t <j6V6t!> has joined #yocto16:53
*** j6V6t <j6V6t!> has left #yocto16:54
volker-can someone check if their /build/downloads/ folder also contains a file called "*.done"16:56
volker-(ls /build/downloads/\*.done16:56
kergothnot here16:57
bluelightningnor here16:57
volker-strange, all my downloadfolders have it16:57
volker-maybe because I use SRC_URI = "file://*" a couple of times16:58
volker-and rsync seems to have problems with it when trying to move the download folders to the download mirror17:00
*** sjolley <sjolley!sjolley@nat/intel/x-cogmhnxoklwytkgi> has quit IRC17:01
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC17:03
*** sjolley <sjolley!~sjolley@> has joined #yocto17:03
*** staylor <staylor!> has quit IRC17:05
*** Doug_ <Doug_!c0373624@gateway/web/freenode/ip.> has quit IRC17:08
*** phantoxe <phantoxe!> has quit IRC17:08
*** eballetbo <eballetbo!> has quit IRC17:19
*** sameo <sameo!samuel@nat/intel/x-eehubvyzdyqazbin> has quit IRC17:20
*** Sput <Sput!~sputnick@quassel/developer/sput> has quit IRC17:23
*** alimon <alimon!> has quit IRC17:24
*** alimon <alimon!> has joined #yocto17:25
*** Sput <Sput!~sputnick@quassel/developer/sput> has joined #yocto17:26
*** belen <belen!Adium@nat/intel/x-naayadgboaektxqi> has quit IRC17:27
*** kroon <kroon!> has joined #yocto17:38
*** sjolley <sjolley!~sjolley@> has quit IRC17:41
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto17:51
lpappis there a way on the generated target image after flashing to figure out whether a binary is stripped? Busybox does not seem to have the "file" command available.17:51
*** diego_r <diego_r!> has quit IRC17:52
rburtonuse binutils to determine if the binary has debug sections?17:53
rburtonor look at the size17:53
rburtonor install file17:53
maxtothemaxtrack down the binary on your build system and look at it there17:53
nerdboyshould be a function of config settings/packaging in the build...17:53
lpappinstall file is not an option without development environment17:53
lpappsize does not tell me much17:53
nerdboyare you seeing something unexpected?17:53
lpappnot sure what binutils means in this context.17:53
nerdboynm or readelf maybe?17:54
nerdboyer, scanelf?17:54
*** [Sno] <[Sno]!~Sno]> has joined #yocto17:55
lpappthose are not available, at least on the core-image-minimal17:56
maxtothemaxlpapp, you will not be able to do this from within the image you create17:56
nerdboyno access to package feed?17:57
maxtothemaxyou need to look at the binaries on the machine you used to create the image17:57
lpappok, thanks (sad).17:57
maxtothemaxdoes that make sense?17:57
lpappwell, sorta. I will file a feature request against busybox to create a file applet ;-)17:57
nerdboyor manually copy the binutils package and install it...17:57
maxtothemaxhow did you get this core-image-minimal anyway? did you build it yourself or download it from somewhere17:58
*** sjolley <sjolley!sjolley@nat/intel/x-rbgienzatcqgoudx> has joined #yocto17:59
*** joranb <joranb!407ea468@gateway/web/freenode/ip.> has joined #yocto18:00
joranbI dont understand how to make a simple gui program in yoctoproject.  I have looked at lots of docs and it seems heavily focused on the architecture of a program.18:01
joranbbut I havent been able to find any resources that completly detail creating a custom application18:02
maxtothemaxdo you have an existing GUI program and you want to make a recipe for it so you can put it on images?18:02
maxtothemaxor are you trying to make a GUI front end for yocto?18:02
joranb(really Im interested in a simple charting engine (that streams data in) (from a usb connector))18:02
joranbno Im trying to create basically a hello world type application just to learn about it18:03
*** sjolley <sjolley!sjolley@nat/intel/x-rbgienzatcqgoudx> has quit IRC18:03
maxtothemaxso yocto is not really a way to create new programs, it's a way to put lots of existing programs together18:04
joranbIm really familliar with python , fairly proficient with c/c++ , marginally proficient with Java ... but I just dont really understand how to make a simple yoctoproject gui18:04
joranbby programs you mean "recipes"?18:05
joranbor actual programs? that the recipes tell to execute?18:05
maxtothemaxyeah, actual programs18:05
lpappmaxtothemax: I am just the user of the image. I honestly think busybox ougtha have the "file" applet, anyhow.18:06
joranbso Ive found plenty of tutorials that show writing a simple "helloworld.cpp" and then executing it (since its essntially a stripped down linux from what I can tell)18:06
maxtothemaxlpapp, I doubt they'll put one in, but what you can do is boot up your image, copy the file you're interested in onto a flash drive or do a network copy or something, and then look at it on a more full-featured Linux OS18:07
*** TRoGd0R <TRoGd0R!> has left #yocto18:07
lpappmaxtothemax: I doubt they would not put one in, especially configurably.18:07
maxtothemaxlpapp, or if you have a copy of your image on a Linux machine, you can mount it with loopback and look at the files that way18:08
maxtothemaxjoranb, yocto is designed to create a complete Linux OS with a custom loadout of preinstalled programs on it18:09
maxtothemaxjoranb, you know how some routers have Linux operating systems on them?18:09
maxtothemaxa lot of those operating systems were generated using Yocto18:09
maxtothemaxand when a firmware update for that router comes out, the replacement operating system was also generated with yocto18:10
maxtothemaxthat's sort of what it's for18:10
joranbok ... so gumstix pepper board is what Im developing for ... I would likely just put my program execution into the ~/.bashrc or something18:11
maxtothemaxjoranb, now we're talking :)18:11
maxtothemaxhere's what I would suggest18:11
maxtothemaxinstall a yocto image on your gumstix18:11
joranbbut I dont understand what graphics libraries I can use (ie wx,qt,etc)18:12
joranbuh huh I can manage that much Im sure ;P18:12
maxtothemaxthen develop your program as you normally would, using your PC for testing of your program18:12
maxtothemaxfinally, write a yocto recipe for your program18:13
maxtothemaxand generate a new yocto image that includes your program18:13
maxtothemaxas for graphics libraries18:13
maxtothemaxI know we have recipes for GTK18:13
maxtothemaxwe might also have recipes for WX and QT18:13
joranbthat makes sense then :)18:13
joranbok I think I get it now ... maybe ...18:14
joranbI guess ill try this weekend and see how far I get18:14
maxtothemaxoe-core is all the recipes that are included with yocto:
joranbI'll likely be back with more specific questions this weekend18:14
joranbahh that helps alot I think18:14
maxtothemaxbut there are lot's more18:14
maxtothemaxlook in metal-oe, it's a huge library of extra recipes:
maxtothemaxyou can add the meta-oe layer to your bblayers.conf, and you'll be able to use whatever of those extra recipes you want18:15
joranbI will definately do that18:15
joranbIt makes more sense now18:15
joranbthat you explained some stuff18:15
joranbI was just more confused by than anything by the getting started guides18:16
maxtothemaxyocto is kind of unique, it took me a couple of days before I understood what it was and what it was for18:16
joranbI think I get it now ... my program is just to stream values from a usb tty and plot them (animated) and show the latest value at the top ... and thats all its supposed to do (really thats all the whole device is supposed to do)18:18
joranbwhich is really simple ... but the yocto ecosystem is the hardest part ...18:18
maxtothemaxand if you want to generate a little mini-OS that will start up your program at boot time and do nothing else, yocto is perfect18:18
*** sjolley <sjolley!sjolley@nat/intel/x-zupnsgyqgzvhjyrp> has joined #yocto18:19
joranbthats exactly what I want to do ... I have done it in android on touchrevolution , but I was interested to try out yocto and gumstix18:19
maxtothemaxassuming you have a PC with Linux on it, you should develop your program on that and then make a yocto recipe for it to get it on your gumstix18:19
joranbgot It ... I think18:19
joranbI will make a super simple ui this weekend and let you know ... or come back with more specific how do i type questions :P18:20
kergothmaxtothemax: it kind of depends on what your goals are. yocto is actually better for maintaining your image for your device long term. if all you're doing is something extremely light, e.g. board bringup or just one thing to run on the target, buildroot is faster and lighter. but yocto makes it easy to maintain your image and packages for the long term, and to maintain a linux distribution for embedded18:20
*** wotte <wotte!~textual@> has joined #yocto18:21
joranbThanks alot for the help ... I think I understand better what yocto is now :)18:22
joranb@kergoth never heard of buildroot ,  just googled it ... I'll have to look into it further18:23
*** challinan <challinan!> has quit IRC18:23
joranbhow hard is it to build an image for gumstix with it?18:24
kergoththere's no guarantee it supports gumstix out of the box at all. nearly every device has its own kernel and patches and configuration. any tool targeting embedded devices needs explicit support for whatever it is, generally18:25
joranbmeh ok ... well I know I can get a gumstix layer for yocto definately (so I guess I'll stick with that for now... maybe when I have a better handle on these builds I'll revisit buildroot)18:29
joranbthanks though18:29
joranbI'll file that bookmark away for later examination18:29
*** challinan <challinan!> has joined #yocto18:31
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC18:31
*** sjolley <sjolley!sjolley@nat/intel/x-zupnsgyqgzvhjyrp> has quit IRC18:33
*** joranb <joranb!407ea468@gateway/web/freenode/ip.> has quit IRC18:38
*** sjolley <sjolley!sjolley@nat/intel/x-qcyyecccugtgsthl> has joined #yocto18:41
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC18:43
*** florian_kc <florian_kc!~fuchs@Maemo/community/contributor/florian> has joined #yocto18:43
kergothrburton: did you ever look back at the automatic .debug for FILES_${PN}-dbg bits that you hacked together?18:44
WarheadsSEAnyone have thoughts on why my kernel modules are not being stripped?18:46
*** sjolley <sjolley!sjolley@nat/intel/x-qcyyecccugtgsthl> has quit IRC18:47
kergothah, there's the contrib branch18:48
kroonWarheadsSE, none of my kernel modules in FC20 are stripped18:50
kroonWarheadsSE, are kernel modules allowed to be ?18:50
kergoththey can be stripped, but it has to be done more carefully than the strip of regular binaries18:51
kergothafaik it should be done automatically int he build process, not sure why yours wouldn't be18:52
kroonby "not stripped", I mean at least that what "file" says :)18:53
kergothyou can't strip all symbols, they're needed to load the module. but iirc debug info and whatnot can be18:53
*** e8johan <e8johan!> has joined #yocto18:54
rburtonkergoth: sadly not18:56
kergothwould love to see that branch get merged :) definitely nicer than hardcoding the list, given it already knows about the paths19:00
*** Crofton <Crofton!> has quit IRC19:00
rburtonkergoth: feel free to finish it ;)19:00
*** e8johan <e8johan!> has quit IRC19:00
*** e8johan <e8johan!~quassel@> has joined #yocto19:04
*** dvhart <dvhart!dvhart@nat/intel/x-twheshvgfbjrgush> has joined #yocto19:05
*** else58 <else58!> has quit IRC19:08
*** Crofton <Crofton!> has joined #yocto19:11
fray_'er.. Linux rant of the day.. but it may affect us:19:12
fray_basically he says gcc-4.9.0 is broken when compiling the kernel.. :P19:12
fray_yup.. pretty much19:20
*** e8johan <e8johan!~quassel@> has quit IRC19:21
*** sjolley <sjolley!sjolley@nat/intel/x-rqjhypckjjzmkzxn> has joined #yocto19:32
* zeddii is already watching it, as are a lot of us. it'll get worked out :P19:35
* zeddii finishes pushing 3.16 support and gcc 4.9 .. right in the death zone ;)19:35
*** challinan_ <challinan_!> has joined #yocto19:41
*** challinan <challinan!> has quit IRC19:42
*** sjolley <sjolley!sjolley@nat/intel/x-rqjhypckjjzmkzxn> has quit IRC19:47
*** ant_home <ant_home!> has joined #yocto19:48
*** henriknj <henriknj!> has quit IRC19:49
WarheadsSEkroon: kergoth yeah19:55
*** dvhart <dvhart!dvhart@nat/intel/x-twheshvgfbjrgush> has quit IRC19:58
*** Crofton <Crofton!> has quit IRC20:03
*** mkeeter <mkeeter!~mkeeter@> has joined #yocto20:04
*** mkeeter <mkeeter!~mkeeter@> has quit IRC20:05
*** dvhart <dvhart!~dvhart@> has joined #yocto20:07
mranostayhi kergoth20:09
*** LCyrin <LCyrin!~LCyrin@2607:fb90:40c:21d6:e19f:71cb:88a:def7> has joined #yocto20:12
*** manuel_ <manuel_!> has joined #yocto20:15
*** phantom is now known as phantoxeD20:19
*** roric <roric!> has joined #yocto20:28
*** challinan_ <challinan_!> has quit IRC20:35
*** roric <roric!> has quit IRC20:36
*** challinan <challinan!> has joined #yocto20:36
*** wotte <wotte!~textual@> has quit IRC20:42
*** Crofton <Crofton!> has joined #yocto20:52
*** Crofton <Crofton!> has quit IRC20:57
*** Crofton <Crofton!> has joined #yocto20:58
*** manuel_ <manuel_!> has quit IRC20:58
*** wotte <wotte!~textual@> has joined #yocto21:02
*** LCyrin_ <LCyrin_!~lynn@> has joined #yocto21:14
*** LCyrin <LCyrin!~LCyrin@2607:fb90:40c:21d6:e19f:71cb:88a:def7> has quit IRC21:15
*** sjolley <sjolley!~sjolley@> has joined #yocto21:15
*** LCyrin_ is now known as lcyrin21:15
*** wotte <wotte!~textual@> has quit IRC21:26
*** sameo <sameo!samuel@nat/intel/x-uaeapfocipwwwtqq> has joined #yocto21:31
-YoctoAutoBuilder- build #181 of nightly-fsl-ppc-lsb is complete: Failure [failed BuildImages] Build details are at
-YoctoAutoBuilder- build #181 of nightly-x86-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at
-YoctoAutoBuilder- build #180 of nightly-x86-64-lsb is complete: Failure [failed BuildImages BuildImages_1] Build details are at
-YoctoAutoBuilder- build #179 of minnow-lsb is complete: Failure [failed BuildImages] Build details are at
*** ant_home <ant_home!> has quit IRC21:45
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto21:48
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC21:51
*** rcw <rcw!~rwoolley@> has quit IRC21:55
*** roric <roric!> has joined #yocto22:00
*** bfederau <bfederau!> has quit IRC22:01
*** bfederau <bfederau!> has joined #yocto22:01
*** Nitin <Nitin!~nakamble@> has quit IRC22:02
*** challinan <challinan!> has quit IRC22:06
*** challinan <challinan!> has joined #yocto22:09
*** sameo <sameo!samuel@nat/intel/x-uaeapfocipwwwtqq> has quit IRC22:14
sgw_halstead: pidge: Around?22:21
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto22:30
*** jkridner <jkridner!> has joined #yocto22:49
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto22:49
*** Nitin <Nitin!nakamble@nat/intel/x-yrslutxoulijquvw> has joined #yocto22:57
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC23:00
*** Crofton <Crofton!> has quit IRC23:09
*** alimon <alimon!> has quit IRC23:23
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC23:31
*** roric <roric!> has quit IRC23:44
*** munch <munch!> has quit IRC23:45
*** manuel_ <manuel_!> has joined #yocto23:46
mranostayhi manuel_23:54
*** nerdboy <nerdboy!> has joined #yocto23:58

Generated by 2.11.0 by Marius Gedminas - find it at!