Thursday, 2013-07-04

*** blloyd <blloyd!> has quit IRC00:06
*** Squix <Squix!> has quit IRC00:07
*** Squix <Squix!> has joined #yocto00:08
*** ka6sox-away is now known as ka6sox00:09
*** blloyd <blloyd!> has joined #yocto00:21
*** cetola <cetola!4a5ca5c1@gateway/web/freenode/ip.> has left #yocto00:25
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto00:32
*** alexhairyman <alexhairyman!> has joined #yocto00:51
*** Umeaboy <Umeaboy!> has joined #yocto00:52
UmeaboyDoes Yocto run on Little Endian-devices?00:53
*** _julian_ <_julian_!> has joined #yocto00:56
UmeaboyI have a TV that I want to make some more changes to other than just using a wrapping-script. I have bootloader-access.00:57
Crofton|workit should00:57
UmeaboyCPU-name is Titania.00:58
*** _julian <_julian!> has quit IRC00:59
UmeaboyYes, I know it's a long-shot, but I'm intreeegued to test something else that makes the TV better........00:59
UmeaboyFor instance........... in the original EEPROM it's quite difficult to add new drivers.00:59
*** mulhern <mulhern!> has joined #yocto01:00
UmeaboyI'm talking about adding the driver for my external USB sound-card so that I can listen to my movies (at night) through my headset/phones.01:01
UmeaboyCrofton|work: Where do I start?01:01
UmeaboyI know I have to do some reading, but reading is not the strongest part of me. I like to follow guides instead.01:02
*** davest <davest!Adium@nat/intel/x-ekznrheqmazarfqd> has quit IRC01:04
*** blloyd <blloyd!> has quit IRC01:05
*** nitink <nitink!nitink@nat/intel/x-rajhofdogsbpsram> has quit IRC01:09
*** nitink <nitink!~nitink@> has joined #yocto01:22
*** nitink <nitink!~nitink@> has quit IRC01:28
*** nitink1 <nitink1!~nitink@> has joined #yocto01:28
*** nitink1 <nitink1!~nitink@> has quit IRC01:32
*** mranostay is now known as mranostay_gone01:39
*** scot_ <scot_!> has quit IRC01:49
*** mulhern <mulhern!> has quit IRC02:00
*** Umeaboy <Umeaboy!> has quit IRC02:08
*** trollixx <trollixx!> has quit IRC02:37
*** trollixx <trollixx!> has joined #yocto02:37
*** trollixx <trollixx!> has joined #yocto02:38
*** silviof2 <silviof2!> has joined #yocto02:54
*** silviof1 <silviof1!> has quit IRC02:56
*** seebs <seebs!> has quit IRC03:14
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC03:24
*** seebs <seebs!> has joined #yocto03:37
*** SidH_ <SidH_!~SidH_@> has joined #yocto04:09
*** alexhairyman <alexhairyman!> has quit IRC04:30
*** andyross <andyross!> has quit IRC04:36
*** andyross <andyross!> has joined #yocto04:37
*** crazy_imp <crazy_imp!> has quit IRC04:39
*** SidH_ <SidH_!~SidH_@> has quit IRC04:40
*** crazy_imp <crazy_imp!> has joined #yocto04:41
*** ka6sox is now known as ka6sox-away04:57
*** agust <agust!> has joined #yocto04:59
*** zecke <zecke!> has joined #yocto05:15
*** nitink <nitink!~nitink@> has joined #yocto05:22
*** tasslehoff <tasslehoff!~tasslehof@> has joined #yocto05:32
*** mitz_ <mitz_!> has quit IRC05:42
*** andyross <andyross!> has quit IRC05:47
*** bilboed <bilboed!~bilboed@> has quit IRC05:57
*** icanicant <icanicant!~klawson@> has quit IRC05:57
*** bilboed <bilboed!~bilboed@> has joined #yocto05:58
*** icanicant <icanicant!~klawson@> has joined #yocto05:58
*** zecke <zecke!> has quit IRC05:59
*** melonipoika <melonipoika!> has joined #yocto06:02
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC06:03
*** mitz_ <mitz_!> has joined #yocto06:05
*** silviof2 is now known as silviof06:07
*** gmacario <gmacario!> has joined #yocto06:14
*** zeeblex <zeeblex!apalalax@nat/intel/x-rrrvkydxutpjrloh> has joined #yocto06:16
*** jonatan <jonatan!> has joined #yocto06:20
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto06:20
*** mihai <mihai!~mihai@> has joined #yocto06:27
*** mihai <mihai!~mihai@> has joined #yocto06:28
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC06:37
*** JaMa <JaMa!> has joined #yocto06:44
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto06:50
*** eballetbo <eballetbo!> has joined #yocto06:59
*** bluelightning <bluelightning!> has joined #yocto07:03
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto07:03
*** ivali <ivali!~droid@unaffiliated/ivali> has joined #yocto07:13
*** TuTizz <TuTizz!~TuTizz@> has joined #yocto07:16
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has joined #yocto07:16
*** ka6sox-away is now known as ka6sox07:21
*** zecke <zecke!~ich@> has joined #yocto07:29
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:34
*** abelloni <abelloni!> has joined #yocto07:42
*** lpapp <lpapp!> has joined #yocto07:45
lpappHi. Yocto does not support arch host yet?
*** sameo <sameo!~samuel@> has joined #yocto07:47
bluelightningmorning all07:53
bluelightninglpapp: not officially, no... if you want to use it you're welcome to do so, and it may well work fine, but we can't guarantee there won't be issues07:53
lpappbluelightning: I guess I can ask for help in here if there are issues?07:54
bluelightninglpapp: sure07:55
lpappbluelightning: yocto needs python 2? Arch has been shipping python 3 since its appearance.07:58
*** ant_work <ant_work!> has joined #yocto07:58
bluelightninglpapp: that is correct08:03
bluelightninglpapp: we've made some moves towards python 3 support but with a codebase such as ours it is difficult to be compatible with both08:04
lpappbluelightning: oh, it also needs the old texinfo4?08:05
*** zenlinux <zenlinux!> has quit IRC08:05
bluelightninglpapp: I thought we patched in support for texinfo 5 in a bunch of different places08:06
*** TuTizz <TuTizz!~TuTizz@unaffiliated/tutizz> has left #yocto08:06
lpappbluelightning: ok, I just saw a thread about it in March this year.08:07
lpappit may have changed after that.08:07
lpappalso, my company uses an old yocto version.08:08
bluelightningah, right... in which case you may have issues with that08:08
bluelightningI'd suggest using a distro that is more conservative than arch in that case08:08
lpappmaybe I can install something in a chroot environment just for this.08:09
lpappbut it would be still be nice to get archlinux working with the latest so that when my company switches to a new version, I can drop the chroot environment.08:10
*** seebs <seebs!> has quit IRC08:14
*** seebs <seebs!> has joined #yocto08:15
*** fenrig <fenrig!55eac3e5@gateway/web/freenode/ip.> has joined #yocto08:16
fenrigHi :)08:16
*** zenlinux <zenlinux!> has joined #yocto08:18
fenrigI'm trying to generate a decent yocto distro for my BeagleBone Black using yocto :) I'm using git repo " "08:18
fenrigNow I've got the beaglebone booted :) using MLO and u-boot.img and uImage08:18
fenrigI don't have a Device tree generated file :/08:18
fenrigso I'm stuck at the last u-boot procedure08:19
fenrigat the moment I'm reading about u-boot, but that won't fix my issue08:19
fenrigcould someone give me some pointers on how to look for the root cause of the problem, any help will be appreciated ;)08:20
*** slaine <slaine!~slaine@> has joined #yocto08:22
*** mckoan|away is now known as mckoan08:22
mckoangood morning08:22
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC08:25
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto08:25
fenrigmckoan: good morning :)08:28
*** synthnassizer <synthnassizer!~quassel@> has joined #yocto08:28
*** florin <florin!~florin@> has joined #yocto08:42
*** florin is now known as Guest59208:43
Guest592hi everybody08:43
Guest592does yocto provide any support for conditionally adding a patch to some package when a certain package is  going to be built for an image?08:44
fenrigI'm trying to generate a decent yocto distro for my BeagleBone Black using yocto :) I'm using git repo " ". Now I've got the beaglebone booted :) using MLO and u-boot.img and uImage BUT I don't have a Device tree generated file :/. so I'm stuck at the last u-boot procedure could someone give me some pointers on how to look for the root cause of the problem, any help will be appreciat08:44
-YoctoAutoBuilder- build #34 of minnow-lsb is complete: Failure [failed Building Images] Build details are at
Guest592let's say I want to applay a patch to package X only when package Y is going to be compiled as part of my image08:45
fenrigGuest592: you can use shell commands (bash) with if's :)08:45
Guest592to check against what? just look-up my image recipe and parse that?08:45
fenriguhm I'll look into that for you, but I'm also just a noob so don't expect fancy solutions (if I can even offer solutions)08:46
Guest592I'd expect yocto to have something fancy for this kind of problem08:46
bluelightningGuest592: you can't do that directly I'm afraid08:52
bluelightningGuest592: the only option would be to build two versions of the piece of software08:52
bluelightningi.e. two recipes08:52
Guest592so X would have 2 recipes for it08:53
Guest592and I should keep myimage recipe always updated with the needed X recipe?08:53
bluelightningGuest592: i'd suggest two separate image recipes as well08:54
Guest592I had hoped this would not be the case :)08:54
Guest592seems like a pretty nice feature to have into yocto though08:54
bluelightningyou're effectively talking about making compilation-level changes based upon the structure of the image08:55
Guest592I know at least one build system that can handle that :)08:55
bluelightningsince the image construction happens a lot later in the build process, that would be very difficult08:55
-YoctoAutoBuilder- build #207 of nightly-mips-lsb is complete: Failure [failed Building Images Building Images_1] Build details are at
Guest592I'd have thought that right at the beginning of the build, the needed packages should be known by the build system08:56
ant_workGuest592: adding a patch conditionally is possible, the point is the condition to check08:58
Guest592condition is if the image beeing built contains a certain package08:59
fenrigyes but I think the execution shell, when building the packages (fetch - configure - compile - install - populate - ...) does not have access to that data, though the executing python script of OE should have access to this09:00
bluelightningone of the issues is that the final image construction is controlled by the package manager (RPM + smart when the RPM backend is selected)09:00
-YoctoAutoBuilder- build #48 of minnow is complete: Failure [failed Building Images Publishing Artifacts] Build details are at
ant_workthat won't work, you'd need to check against some variable09:00
bluelightningbitbake has an idea of what is needed to construct the image (via RDEPENDS) but different package managers can have different ideas about actual runtime dependencies, so it doesn't know exactly09:00
-YoctoAutoBuilder- build #198 of nightly-x86-lsb is complete: Failure [failed Building Images Building Images_1] Build details are at
ant_workGuest592: finally you risk to build two different recipes under the same name...09:01
ant_workone patched, the other unpatched09:02
fenrigso now about device tree :D09:04
bluelightningthe other issue with doing something like this is what would happen if you built two images, one that had the conditional package and one that didn't?09:05
fenrigI'm trying to generate a beaglebone build, and I have troubles with device tree. As in that I can't find a generated (valid) device tree :)09:05
ant_workfenrig: pls try on #beagle, iirc "of" was discussed yesterday09:05
-YoctoAutoBuilder- build #208 of nightly-intel-gpl is complete: Failure [failed Building Images Building Images_1] Build details are at
-YoctoAutoBuilder- build #192 of nightly-x86-64 is complete: Failure [failed Building Images Running Sanity Tests Building Images_1 Building Images_2 Publishing Artifacts] Build details are at
Guest592ant_work, seems like there should be something more to that than having to maintain 2 image recipes for this kind of situation09:06
fenrigIant_work: Okay but I'm building it with yocto, so isn't it closely related to yocto itself?09:06
-YoctoAutoBuilder- build #196 of build-appliance is complete: Failure [failed Building Images Building Images_1 Publishing Artifacts] Build details are at
*** ivali <ivali!~droid@unaffiliated/ivali> has quit IRC09:08
-YoctoAutoBuilder- build #198 of nightly-arm-lsb is complete: Failure [failed Building Images Building Images_1] Build details are at
*** soldoKyn <soldoKyn!> has joined #yocto09:10
-YoctoAutoBuilder- build #189 of nightly-x86-64-lsb is complete: Failure [failed Building Images] Build details are at
*** ka6sox is now known as ka6sox-away09:13
soldoKynhi to all! I need to clean my yocto environment from heavy data...basically i need to clean sstate-cache, tmp and downloads directory. there's a bitbake option to do this or I have to clean that directories with a rude rm -rf? thanks!09:16
*** lpapp <lpapp!> has quit IRC09:16
rburtonsoldoKyn: rm -rf09:17
rburtoniirc, there is a tool to clean sstate of old files09:17
-YoctoAutoBuilder- build #193 of nightly-arm is complete: Failure [failed Building Images Running Sanity Tests Building Images_1 Building Images_2 Building Images_3 Publishing Artifacts] Build details are at
*** belen <belen!~Adium@> has joined #yocto09:18
-YoctoAutoBuilder- build #195 of nightly-ppc is complete: Failure [failed Building Images Running Sanity Tests Building Images_1 Building Images_2 Building Images_3 Publishing Artifacts] Build details are at
soldoKynrburton: ok, I think i'll do an rm -rf! thanks!09:21
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC09:22
*** Net147 <Net147!> has joined #yocto09:22
*** melonipoika_ <melonipoika_!> has joined #yocto09:25
*** Squt <Squt!~sputnick@quassel/developer/sput> has joined #yocto09:25
*** mckoan_ <mckoan_!~marco@unaffiliated/mckoan> has joined #yocto09:27
*** nitink1 <nitink1!~nitink@> has joined #yocto09:28
*** OlivierG` <OlivierG`!> has joined #yocto09:30
*** rburton_ <rburton_!> has joined #yocto09:31
*** melonipoika <melonipoika!> has quit IRC09:32
*** nitink <nitink!~nitink@> has quit IRC09:32
*** OlivierG_ <OlivierG_!> has quit IRC09:32
*** fray <fray!> has quit IRC09:32
*** Sput <Sput!~sputnick@quassel/developer/sput> has quit IRC09:32
*** rburton <rburton!> has quit IRC09:32
*** mckoan <mckoan!~marco@unaffiliated/mckoan> has quit IRC09:32
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC09:34
-YoctoAutoBuilder- build #195 of nightly-non-gpl3 is complete: Success [build successful] Build details are at
*** OlivierG` <OlivierG`!> has left #yocto09:34
-YoctoAutoBuilder- build #197 of nightly-x86 is complete: Failure [failed Building Images Running Sanity Tests Building Images_1 Building Images_2 Building Images_3 Publishing Artifacts] Build details are at
fenrigin my beaglebone.conf09:48
fenrigI found that09:48
fenrigMACHINE_ESSENTIAL_EXTRA_RDEPENDS = "kernel-devicetree-overlays"09:48
fenrignow I don't get a resulting device tree tar09:48
fenrigso I don't understand why it isn't generated :/09:49
ant_workfenrig: is the dtc package built?09:49
*** ivali <ivali!~droid@unaffiliated/ivali> has joined #yocto09:51
fenrigant_work: excuse me but I'm still a beginner, how can I verify that a package is being build? By looking at the deploy folder?09:51
ant_workno, in workdir09:51
fenrigin the work directory I found a dtc source :o09:52
ant_workit should be a -native package, built under x8609:52
fenrigand I did one build only, so I think I can assume it's being built09:52
ant_workI'm sorry09:53
ant_workI can't help you too much being I stopped working with beagle* before devicetree09:54
ant_workafais the infrastructure is there09:54
fenrigant_work: it's not your fault, I just don't understand yocto (openembedded) that good. It's still a complex jungle for me :o09:54
*** ivali <ivali!~droid@unaffiliated/ivali> has quit IRC10:00
*** soldoKyn <soldoKyn!> has quit IRC10:11
-YoctoAutoBuilder- build #193 of nightly-multilib is complete: Failure [failed Building Images_2 Running Sanity Tests_2 Building Images_3 Running Sanity Tests_3 Building Images_4] Build details are at
fenriguhm how do layer.conf work?10:13
fenrigwhen does OE read this file :o10:13
fenrigand what is {layerdir}10:14
*** belen <belen!~Adium@> has quit IRC10:19
*** jbaxter <jbaxter!> has joined #yocto10:20
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto10:37
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto10:39
*** joeythesaint <joeythesaint!~jjm@> has joined #yocto10:46
ndecfenrig: from bitbake usermanual: BitBake will first search the current working directory for an optional "conf/bblayers.conf" configuration file. This file is expected to contain a BBLAY\10:47
ndecERS variable which is a space delimited list of 'layer' directories. For each directory in this list, a "conf/layer.conf" file will be searched for and parsed with the LAYERDI\10:47
ndecR variable being set to the directory where the layer was found. The idea is these files will setup BBPATH and other variables correctly for a given build directory automatica\10:47
ndeclly for the user.10:47
ndecargh.. sorry about that ;-)10:47
*** walters <walters!> has quit IRC10:48
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC10:50
*** belen <belen!~Adium@> has joined #yocto10:51
-YoctoAutoBuilder- build #195 of nightly-mips is complete: Failure [failed Building Images Running Sanity Tests Building Images_1] Build details are at
jackmitchellrburton_: are you saying that xuser is general user which it's only function is that it's not root?11:15
jackmitchellbecause I am struggling to understand, why connman needs to depend on it11:15
rburton_jackmitchell: to be honest you don't want to know11:15
jackmitchellis it because connman wants a non root user to switch to?11:15
*** belen <belen!~Adium@> has quit IRC11:15
jackmitchellI'm just confused, to why I need xuser when I don't have X11 in my image11:16
rburton_it's because the shell can run as non-root but the upstream connman DBus ACLs don't work because generally we don't have anything that says "user is at the console"11:16
jackmitchelland I aussume it's because I have connman in my image11:16
rburton_i suspect dbus will moan if the ACLs talk about a user that doesn't exist11:16
rburton_to fix this we need to make the at-console stuff work in dbus for us11:17
jackmitchellok, I kind of get it11:17
rburton_the easy solution is "mandate systemd" :)11:17
jackmitchellwell, I use systemd in my image11:17
*** mihai <mihai!~mihai@> has quit IRC11:17
jackmitchellbut I think I agree it shouldn't be called xuser, it's particularly consfusing11:17
rburton_this is something that's been bugging me since i started on yocto11:17
*** mihai <mihai!~mihai@> has joined #yocto11:18
rburton_jackmitchell: does your stuff all run as root, or do you have another "normal" user?11:19
jackmitchellI only have root and (since recently) xuser11:19
rburton_i wonder if dbus can ACL on a user's groups, so we can stop hard-coding that username11:20
jackmitchellso yes, everything currently runs as root11:20
-YoctoAutoBuilder- build #161 of nightly is complete: Failure [failed Building Images Building Images_9 Building Images_10] Build details are at
rburton_ hm, yes, it can do groups.11:21
*** fray <fray!> has joined #yocto11:21
fenrigant_work: How can i check if it's build?11:24
ant_workfenrig: 1) you have to check for artifacts in deploydir 2) check under tmpdir/work 3) check the produced ipk/rpm 4) re-bitbake the recipe and see 0 tasks executed11:28
fenrigant_work: I've found a binary of dtc and sources in the work directory, however I did not find a rpm (yocto distro) but that is because the target does not run device tree compiler11:29
ant_worksure, it's dtc-native11:30
*** belen <belen!~Adium@> has joined #yocto11:30
*** blitz00 <blitz00!~stefans@> has joined #yocto11:45
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has joined #yocto11:45
*** scot_ <scot_!> has joined #yocto11:45
*** zecke <zecke!~ich@> has quit IRC11:47
*** eren <eren!~eren@unaffiliated/eren> has quit IRC11:48
*** ScriptRipper <ScriptRipper!~ScriptRip@opensuse/member/MartinMohring> has quit IRC12:26
*** OlivierG <OlivierG!> has joined #yocto12:40
*** ScriptRipper1 <ScriptRipper1!> has joined #yocto12:42
*** belen <belen!~Adium@> has quit IRC12:44
*** OlivierG <OlivierG!> has quit IRC12:51
*** walters <walters!> has joined #yocto12:52
fenrigSo I think I found (not sure yet) why .dtb for beaglebone is not generated :)12:54
fenrigthe machine conf was missing " KERNEL_DEVICETREE = ... "12:55
fenrignow I don't know for sure what to fill in " ... "12:55
fenrigat the moment I'm using " KERNEL_DEVICETREE = "arch/${ARCH}/boot/dts/am335x-bone.dts" "12:55
fenrigbut for some reason it fails12:56
fenrig| ERROR: Function failed: do_devicetree_image12:56
fenrighow do I go about fixing this (can't find the exact reason why)12:56
*** mulhern <mulhern!> has joined #yocto12:57
ant_workfenrig: this is in the archives
ant_worktry KERNEL_DEVICETREE = "${S}/arch/12:59
ant_work(inelegant and strange, though)12:59
fenrigant_work: I'm testing your solution12:59
ant_workbut I think I know why you're struggling12:59
ant_workI fear for the black bone you'd need Angstrom and its customizations13:00
ant_workYocto is tested on beagleboard afaik, then you need extra layers13:00
fenrigant_work: the generated build does work, i stole a dtb file from the archlinux arm os :)13:02
bluelightningsurely meta-beagleboard should be all that's needed13:02
fenrigant_work: and now it boots, unfortenately I get the same error with your ${S} fix13:03
fenrigbut I noticed something I missed last time13:03
fenrigtemp/run.do_devicetree_image.3545: package_stagefile_shell: not found13:03
*** belen <belen!~Adium@> has joined #yocto13:03
fenrigbluelightning: I'm using it, but it generates a 3.8 linux kernel (with devicetree) but I'm missing the devicetree dtb's :) so uboot can't finish it's boot process13:04
fenrigwould you guys like to see the full error response?13:05
fenrigI think the warning can be safely ignored (allthough it bothers me that it shows up at all)13:09
*** tasslehoff <tasslehoff!~tasslehof@> has quit IRC13:10
*** andyross <andyross!> has joined #yocto13:11
*** e8johan_ <e8johan_!> has quit IRC13:11
fenrigthe error is quite odd13:19
fenrigand I can't seem to find anything about it on the internet13:19
*** andyross <andyross!> has quit IRC13:19
ant_workbluelightning: maybe a stale ?13:19
fenrigwhich is also very odd :o13:19
ant_workyes, package_stagefile_shell it's from the old times iirc13:20
ant_workfenrig: see
ant_workKERNEL_DEVICETREE_ is already set13:23
ant_workjust for fun, remove the you have in meta-oe13:23
Net147are we staying with kernel 3.8 for the next release even though its EOL?13:26
bluelightningNet147: zeddii_home_ would be the best person to answer that but if it follows our usual pattern we'd be using 3.10 for this release13:27
Net147zeddii_home_: ^13:28
*** zecke <zecke!> has joined #yocto13:30
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto13:31
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC13:32
ant_workfenrig: have you already commented that line?13:34
fenrigant_work: normally KERNEL_DEVICETREE wasn't present by default, I added it so I could have the dtb file for u-boot13:39
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC13:48
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has quit IRC13:50
ant_workfenrig: the way Poky/Yocto does it is  /linux-dtb.inc13:52
*** bluelightning1 <bluelightning1!~paul@> has joined #yocto13:52
*** madman-alex <madman-alex!~luccisa@nat/cisco/x-curpayqaacapkqzn> has quit IRC13:53
*** belen2 <belen2!Adium@nat/intel/x-dellqwlmllzfjphq> has joined #yocto13:53
*** belen <belen!~Adium@> has quit IRC13:53
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC13:56
*** Net147 <Net147!> has quit IRC13:57
*** ant_work <ant_work!> has quit IRC14:03
*** mckoan_ is now known as mckoan|away14:08
*** pev <pev!~pev@> has joined #yocto14:08
pevHeya, would anyone be willing to help me with a newbie idiot question?14:09
pev(build related)14:09
*** ka6sox-away is now known as ka6sox14:15
*** Squt is now known as Sput14:17
rburton_pev: ask, don't ask to ask14:18
pevoh, ok...!14:19
pevSo I've just started getting to grips with yocto. I've got a BSP thats come from someone else and I'm playing with rebuilding uboot via "bitbake -v -f -c compile u-boot-pev". This works fine. However I'm trying to read up on what the 'correct' way is to modify and update patches for it14:20
pevSo, there's a patch file : meta-my-board/recipes-bsp/u-boot/u-boot-pev/local-changes.patch14:21
pevbut I don't know the accepted / convenient way to modify the source / update the patch is...14:22
*** Guest592 <Guest592!~florin@> has quit IRC14:22
rburton_one way is to use the devshell function14:22
pevI guess I'm missing something really obvious but cant seem to see anything obvious in the documentation14:22
rburton_bitbake -c devshell u-boot-pev14:22
rburton_that drops you into the source directory, where you can edit and compile directly14:22
rburton_actually generating the patch is Your Problem, so you can use quilt or git14:23
pevso does that update the patch auto-magically?14:23
pevIs there a quick a-b-c walkthrough of that somewhere out there?14:23
rburton_hm, not sure14:23
rburton_if not this should be in the manual14:23
*** ScriptRipper1 <ScriptRipper1!> has quit IRC14:23
rburton_have you looked through the docs on
pevI'm broadly familiar with quilt through devloping around openwrt14:24
rburton_so in the devshell, do the quilt stuff to edit a file and generate the patch14:24
pevbut to be honest I've set up all my sources in SVN as I'm more familiar with it than GIT and havent got time to learn at the mo...14:24
rburton_then copy it out of the work dir into the layer14:24
pevSo you think I should generate iterative patches rather than re-generating the existing patch?14:25
rburton_depends on the problem14:25
rburton_if you're fixing a patch, re-generating makes sense14:25
pevat the moment fixing but adding features next so both realy14:26
fenrigOkay I found the problem: in do_devictree_image of of meta-beagleboard/common-bsp/recipes-kernel  "package_stagefile_shell()" is not found, so I've copied it from of "meta/recipes-kernel"14:26
mulhernSnort is soo close to starting as a daemon process. But it fails just as it forks because fork can't allocate enough memory. There is a fix: set the number in /proc/sys/vm/overcommit_memory to 1. Then you can set it back to 0 once the daemon is successfully started. Is there some standard way to handle this problem? Or should I just try to make it explicit in the snort initialization script?14:27
*** sameo <sameo!~samuel@> has quit IRC14:28
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto14:34
mulhernpev: Actually, I edit in the workdir but compile from the poky/build dir when making patches. bitbake -e is nice because it tells you the values of all the environment variables that you have set, shows how they were expanded, etc. bitbake -c listtasks will tell you all the tasks available for a particular recipe.14:36
rburton_mulhern: devshell gives you a terminal with all those set for you14:37
pevmulhern : what do you do to recreate the patch in your world? Manually?14:37
*** ScriptRipper1 <ScriptRipper1!> has joined #yocto14:37
mulhernrburton: Yep, I know, more or less the same thing.14:38
*** tor <tor!> has joined #yocto14:38
mulhernpev: My one experience with regenerating an existing patch was awkward. Right now I'm really only generating new patches. I think quilt can help you with the regeneration stuff as well, but I started using quilt two weeks ago…and that was after the regeneration experience.14:40
pevOk, I'd settle for your procedure for generating new for now :-D Is it as low tech as duplicating a clean un-built dir and then manually diffing to your modified dir? I know it works but feels very clunky!14:41
rburton_using quilt in the work directory is easy enough14:42
rburton_the patches are generated in the wrong place, but you can mv them to where your recipe is easy enough14:42
pevI take it you have to manually take care of patch sequencing via patch file name prefixes?14:43
rburton_bitbake's SRC_URI is sorted in order of application14:43
pevrburton_: Is that the same as what I'm reading here :
rburton_pev: yes14:44
pevOk, so it's explicit via SRC_URI and not wildcarded?14:44
rburton_wildcards have gotchas14:45
rburton_so its best to be explicit14:45
rburton_i wonder if its possible to setup quilt "properly" when unpacking, so quilt refresh actually updates the patches in the layer14:46
rburton_pev: those docs are old, is the latest copy14:48
pevrburton_: thanks14:49
*** jonatan <jonatan!> has quit IRC14:54
kergothrburton_: pretty sure quilt refresh unlinks and recreates patches, rather than following links, so they'd have to be hardlinked, which would limit the paths to not crossing filesystem boundaries, or you'd have to alter quilt to write them in place, i think, anyway14:58
* kergoth shrugs14:58
rburton_kergoth: awww, the hardlink limitation would stop it working for me at least, so i don't care anymore :)14:59
kergothrburton_: the patch resolver stuff will automatically update the layer files if the quilt series changes after fixing it in the patch resolver shell, iirc, but that was never very pretty14:59
kergothI could see an argument for a quilt refresh argument which makes it modify in-place.. hmm15:00
rburton_it would be nice if the patcher automatically did a git init and effectively did a git am of each patch15:00
kergoththat could be interesting, indeed15:01
kergothone time i had a experimental class that turned workdir into a git repo and tagged the tasks :)15:01
kergothwas interesting to examine that log15:01
rburton_yes i bet15:01
Croftonkergoth, shouldn't you be drinking beer and shooting fireworks?15:06
kergothrburton_: actually, there's already a git-apply based patch applier, doubt it'd take much to extend that.. hmm15:07
kergothheh, i hate arizona on the 4th, we never want to go watch fireworks in the evening because it's way too damn hot to be sitting outside :)15:08
Croftonand I figure they are worried about catching everything on fire15:08
Croftonhere, we are hoping it stops raining long enough for them15:08
*** acidfu <acidfu!~nib@> has joined #yocto15:08
*** acidfu <acidfu!~nib@unaffiliated/acidmen> has joined #yocto15:08
kergothHmm, somewhere around here I have a rewritten patch.bbclass which avoids the classes, resolver stuff, and had a partial implementation of series file support, so you could do file://foo.series or file://series rather than listing each file15:09
kergothCrofton: heh, gotta love mother nature15:09
Croftonthere was a lot of localized flooding yesterday15:10
Croftonmore possible today15:10
*** alexhairyman <alexhairyman!> has joined #yocto15:13
*** tinti_ <tinti_!~tinti@pdpc/supporter/student/tinti> has joined #yocto15:17
* rburton_ wonders what to talk about at ELCE15:23
*** steve___ <steve___!c18ddb24@gateway/web/freenode/ip.> has joined #yocto15:31
*** steve___ is now known as Guest9573415:31
*** Guest95734 <Guest95734!c18ddb24@gateway/web/freenode/ip.> has quit IRC15:35
*** fenrig <fenrig!55eac3e5@gateway/web/freenode/ip.> has quit IRC15:36
*** gmacario <gmacario!> has quit IRC15:39
*** nitink <nitink!~nitink@> has joined #yocto15:40
*** nitink1 <nitink1!~nitink@> has quit IRC15:40
*** hbragge <hbragge!> has left #yocto15:41
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto15:42
*** jackmitchell <jackmitchell!> has quit IRC15:45
*** gcoville <gcoville!> has quit IRC15:46
*** nitink <nitink!~nitink@> has quit IRC16:01
*** zenlinux_ <zenlinux_!> has joined #yocto16:03
*** eballetbo <eballetbo!> has quit IRC16:03
*** ScriptRipper1 <ScriptRipper1!> has quit IRC16:04
*** Squix <Squix!> has quit IRC16:09
*** synthnassizer <synthnassizer!~quassel@> has quit IRC16:14
*** belen <belen!~Adium@> has joined #yocto16:14
*** belen2 <belen2!Adium@nat/intel/x-dellqwlmllzfjphq> has quit IRC16:15
*** ScriptRipper <ScriptRipper!~ScriptRip@opensuse/member/MartinMohring> has joined #yocto16:17
*** eren <eren!~eren@unaffiliated/eren> has quit IRC16:19
*** nitink <nitink!nitink@nat/intel/x-nqgekrftsuoiabsa> has joined #yocto16:33
*** zenlinux_ <zenlinux_!> has quit IRC16:54
*** zeeblex <zeeblex!apalalax@nat/intel/x-rrrvkydxutpjrloh> has left #yocto16:56
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has quit IRC17:00
*** mihai <mihai!~mihai@> has quit IRC17:02
*** swex_ <swex_!~swex@> has quit IRC17:07
*** swex_ <swex_!~swex@> has joined #yocto17:08
*** adam____ <adam____!> has quit IRC17:14
*** mulhern <mulhern!> has quit IRC17:17
*** adam___ <adam___!> has joined #yocto17:22
*** slaine <slaine!~slaine@> has quit IRC17:23
*** zecke <zecke!> has quit IRC17:23
*** zecke <zecke!> has joined #yocto17:24
*** alexhairyman <alexhairyman!> has quit IRC17:25
*** belen <belen!~Adium@> has quit IRC17:25
*** joshc <joshc!> has quit IRC17:36
*** joshc <joshc!~joshc@rhlug/joshc> has joined #yocto17:36
*** winfriedd <winfriedd!> has joined #yocto17:36
*** nitink <nitink!nitink@nat/intel/x-nqgekrftsuoiabsa> has quit IRC17:48
*** mulhern <mulhern!> has joined #yocto17:53
*** nitink <nitink!~nitink@> has joined #yocto18:03
-YoctoAutoBuilder- build #209 of nightly-intel-gpl is complete: Success [build successful] Build details are at
*** nitink <nitink!~nitink@> has quit IRC18:10
*** adam___ <adam___!> has quit IRC18:11
*** adam___ <adam___!> has joined #yocto18:14
*** mulhern <mulhern!> has quit IRC18:29
*** bluelightning1 <bluelightning1!~paul@> has quit IRC18:45
*** zenlinux <zenlinux!> has quit IRC18:49
*** zenlinux <zenlinux!> has joined #yocto18:51
*** scot_ <scot_!> has quit IRC18:58
*** scot_ <scot_!> has joined #yocto18:59
*** zecke <zecke!> has quit IRC18:59
Daemon404seebs, there is a typo in your book. i am disappointed.19:05
seebsI think I know of a couple which I've reported to APress, but I don't think sales are fast enough that additional printings are super likely.19:06
Daemon404page 158 under Almquist Shell19:06
Daemon404there's an extra paren19:06
Daemon404and this concludes The Daily Pedant19:07
seebsWell, that's not so much a typo as the inevitable punishment for your moral failings, see.19:07
Daemon404seems plausible.19:07
*** kergoth <kergoth!> has quit IRC19:11
*** kergoth <kergoth!> has joined #yocto19:11
*** yocti <yocti!> has joined #yocto19:40
*** francois99 <francois99!> has quit IRC19:41
*** halstead <halstead!> has quit IRC19:41
*** smartin <smartin!> has quit IRC19:41
*** Crofton <Crofton!> has quit IRC19:41
*** Rootert <Rootert!> has quit IRC19:41
*** addu <addu!> has quit IRC19:41
*** smartin <smartin!> has joined #yocto19:41
*** jjardon_ is now known as jjardon19:41
*** Rootert <Rootert!> has joined #yocto19:41
*** addu <addu!> has joined #yocto19:41
*** rburton_ <rburton_!> has quit IRC19:47
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC19:47
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto19:47
*** rburton <rburton!> has joined #yocto19:48
*** ant_home <ant_home!> has joined #yocto19:51
*** jmdelos_ <jmdelos_!> has joined #yocto19:53
*** seebs <seebs!> has quit IRC19:56
*** seebs <seebs!> has joined #yocto19:56
*** jmpdelos <jmpdelos!> has quit IRC19:57
*** davest <davest!~Adium@> has joined #yocto20:01
*** joey_saint <joey_saint!~jjm@> has quit IRC20:01
*** bluelightning <bluelightning!> has joined #yocto20:07
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto20:07
*** andyross <andyross!> has joined #yocto20:10
*** andyross <andyross!> has quit IRC20:25
*** jbaxter <jbaxter!> has quit IRC20:29
*** MWelchUK <MWelchUK!> has joined #yocto20:29
MWelchUKHi Guys. Is there a way to add autotool site config options to a recipe?20:30
*** tor <tor!> has quit IRC20:33
*** ausxxh_ <ausxxh_!~xxiao@> has joined #yocto20:55
*** davest <davest!~Adium@> has quit IRC20:56
*** MWelchUK <MWelchUK!> has quit IRC20:57
*** MWelchUK <MWelchUK!> has joined #yocto21:00
*** davest <davest!Adium@nat/intel/x-sngviydcusghfyel> has joined #yocto21:01
*** seebs <seebs!> has quit IRC21:02
*** seebs <seebs!> has joined #yocto21:03
*** zenlinux_ is now known as zenlinux21:09
-YoctoAutoBuilder- build #197 of build-appliance is complete: Success [build successful] Build details are at
*** abelloni <abelloni!> has quit IRC21:11
*** davest <davest!Adium@nat/intel/x-sngviydcusghfyel> has quit IRC21:12
*** davest <davest!~Adium@> has joined #yocto21:19
*** smartin_ <smartin_!> has joined #yocto21:25
*** blloyd <blloyd!~blloyd@> has joined #yocto21:32
*** sameo <sameo!~samuel@> has joined #yocto21:39
bluelightningMWelchUK: sure - you can use CACHED_CONFIGUREVARS or meta/site/*21:44
*** honschu <honschu!> has joined #yocto21:45
*** honschu <honschu!~honschu@shackspace/j4fun> has joined #yocto21:45
*** honschu_ <honschu_!~honschu@shackspace/j4fun> has quit IRC21:48
*** davest <davest!~Adium@> has quit IRC21:50
*** smartin_ <smartin_!> has quit IRC21:53
*** davest <davest!Adium@nat/intel/x-iswjflahflfgppno> has joined #yocto22:05
*** Umeaboy <Umeaboy!> has joined #yocto22:20
*** davest <davest!Adium@nat/intel/x-iswjflahflfgppno> has quit IRC22:38
*** winfriedd <winfriedd!> has quit IRC22:39
*** pev <pev!~pev@> has quit IRC23:36
*** Umeaboy <Umeaboy!> has quit IRC23:44

Generated by 2.11.0 by Marius Gedminas - find it at!