Thursday, 2013-12-12

SmittySo, I'm quite familiar with cross compiling for embedded, and frankly, I don't see any difference between that and compiling native for non-embedded.  I still use gnu cc, g++, ld, ar, etc, and of course have to specify the architecture, or specific CPU in some cases.  although I'm not constructing an entire OS.00:00
SmittySo, Yocto is providing a framework to facilitate not only the cross-compiling, but also the construction of the file system, the boot image, etc.  Is that right ?00:03
*** _tid <_tid!> has joined #yocto00:03
*** davest <davest!~Adium@> has joined #yocto00:03
b1gtunaHello everyone, has any of you figured out how to auto-connect a network interface on boot on Dora/Dylan?00:04
kergothi'm assuming 'auto eth0' in interfaces isn't doing it :)00:06
*** zeddii_home <zeddii_home!> has quit IRC00:06
*** zeddii_home <zeddii_home!> has joined #yocto00:06
b1gtunakergoth: that only automatically brings up when I do ifup -a (vs ifup wlan0)00:07
kergoth'auto' is intended to bringup on boot also00:07
kergothpossible the hardware isn't ready at that point in teh boot process, though00:07
b1gtunakergoth: reallly? hmm I see so that's where it's broken00:07
b1gtunakergoth: that is highly possible00:07
SmittyMy immediate question would be, Why would auto-connecting a network interface behave any different on Dora/Dylan than any other standard linux build ?00:08
kergothyou'd think it'd automatically come up when it becomes available though, via the udev bits00:08
b1gtunakergoth: so I don't need a separte systemd service to do this?00:08
kergothas hotplug used to00:08
kergothah, not sure exactly how ifupdown integrates with systemd, or if it does at all00:08
kergothactually i think you can either use connman, or you could use systemd's built in interface stuff00:08
kergothe.g. systemctl enable dhcpcd@eth0 or what have you00:09
b1gtunakergoth: hmmm00:09
kergothafraid i'm not sure off the top of my head00:09
kergothSmitty: it isn't in general. but as with desktop distros, the variations in configuration between distros matter00:09
b1gtunakergoth: so the 'auto' command only works when I have systemd correctly configured, right?00:09
kergothi'd guess so, it wouldn't surprise me if the ifiupdown startup script just ran ifup -a00:10
SmittyThanks kergoth, you have been helpful in clearing some of the mud from my eyes.00:10
b1gtunakergoth: good stuff, thanks for the pointers. I am gonna go fix my systemd scripts now00:10
*** Smitty <Smitty!55b54be1@gateway/web/freenode/ip.> has quit IRC00:10
kergothgood luck :)00:10
b1gtunakergoth: thanks =D00:10
kergothof course wlan config gets complicated, e.g. wpa-supplicant configuration..00:11
kergothnot that thats particular hard, i just meant another piece to check the systemd integration of00:11
b1gtunakergoth: ya there are a number of components that i must align00:11
kergothof course, if it uses ifupdown, can use the wpa-supplicant ifupdown integration and let ifup handle it, in theory..00:12
* kergoth shrugs, as you say, lots of pieces00:12
b1gtunakergoth: wait, of it's either systemd service + wpa_supplicat OR ifupdown + wpa_supplicant? Not systemd service + ifupdown + wpa_Supplicant?00:13
kergothwell, a systemd service could run ifup, and then you'd adjust interfaces appropriately, or it coul dhandle the wpa-supplicant/dhcp client bits itself presumably, never messed with that myself00:14
kergothi'd guess it'd be less complicated to do the ifup route, but then you need tom ake sure it runs at the right time00:14
kergothwhereas systemd services which are bound to an interface will automatically run when teh interface shows up00:14
kergothe.g. the @ one i mentioned before00:15
b1gtunakergoth: gotchat00:15
*** ScriptRipper <ScriptRipper!~ScriptRip@opensuse/member/MartinMohring> has quit IRC00:15
*** Jefro <Jefro!> has joined #yocto00:17
-YoctoAutoBuilder- build #46 of nightly-intel-gpl is complete: Failure [failed Building Images] Build details are at
*** ScriptRipper <ScriptRipper!~ScriptRip@opensuse/member/MartinMohring> has joined #yocto00:29
*** jamestunnicliffe <jamestunnicliffe!~quassel@linaro/jamestunnicliffe> has quit IRC00:30
*** ant_home <ant_home!> has quit IRC00:34
*** munch <munch!> has quit IRC00:41
-YoctoAutoBuilder- build #44 of build-appliance is complete: Success [build successful] Build details are at
*** davest <davest!~Adium@> has quit IRC00:50
-YoctoAutoBuilder- build #44 of nightly-fsl-arm-lsb is complete: Failure [failed Building Images Building Images_1 Building Images_2 Publishing Artifacts] Build details are at
*** seebs <seebs!> has quit IRC01:14
*** seebs <seebs!> has joined #yocto01:17
*** hollisb <hollisb!> has quit IRC01:20
*** mulhern <mulhern!> has joined #yocto01:23
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto01:26
*** [simar|on] <[simar|on]!> has quit IRC01:36
*** joeythesaint <joeythesaint!> has quit IRC01:45
*** bingbu <bingbu!~mars@> has joined #yocto01:46
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has quit IRC01:46
-YoctoAutoBuilder- build #44 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
*** _tid <_tid!> has quit IRC01:50
*** davest <davest!Adium@nat/intel/x-bldrxvuccqgsatng> has joined #yocto01:59
*** _tid <_tid!> has joined #yocto02:03
*** davest <davest!Adium@nat/intel/x-bldrxvuccqgsatng> has quit IRC02:06
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC02:15
*** Jefro <Jefro!> has quit IRC02:28
*** dv_ <dv_!> has quit IRC02:43
*** dv_ <dv_!> has joined #yocto02:45
*** synthesize <synthesize!> has joined #yocto02:45
*** erbo <erbo!> has quit IRC02:47
*** erbo <erbo!> has joined #yocto02:55
synthesizeI'm looking for 'advanced' u-boot documentation with regards to strategies in handling upgrades - it seems like a common solution is to just reflash u-boot in order to fix bugs. This happens fairly normally under situations where your CPLD/FPGA has a change in behavior and needs to have a different initialization.03:01
*** silviof1 <silviof1!~silviof@unaffiliated/silviof> has joined #yocto03:01
synthesizeI've used hush scripts for this in the past, but I'm thinking about trying to rig up a 'patch' system so that there are compiled u-boot programs that get added to a repo in flash with some sorting rules for what overides what.03:02
synthesizeJust wondering if someone has documented this or if I should as I work through it.03:02
-YoctoAutoBuilder- build #45 of nightly-x86-64 is complete: Failure [failed Building Toolchain Images Building Toolchain Images_1 Publishing Artifacts] Build details are at
*** silviof <silviof!> has quit IRC03:03
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC03:04
*** khem <khem!> has joined #yocto03:10
*** khem <khem!> has quit IRC03:15
*** khem <khem!~Thunderbi@> has joined #yocto03:15
*** cristianiorga <cristianiorga!~cristiani@> has quit IRC03:20
*** cristianiorga <cristianiorga!~cristiani@> has joined #yocto03:21
*** khem <khem!~Thunderbi@> has quit IRC03:22
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto03:24
*** khem <khem!> has joined #yocto03:29
*** khem <khem!> has quit IRC03:31
*** khem <khem!> has joined #yocto03:32
-YoctoAutoBuilder- build #44 of nightly-x86 is complete: Failure [failed Building Toolchain Images Building Toolchain Images_1 Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #44 of nightly-ppc is complete: Failure [failed Building Toolchain Images Building Toolchain Images_1 Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #46 of nightly-mips is complete: Failure [failed Building Toolchain Images Building Toolchain Images_1 Publishing Artifacts] Build details are at
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC03:58
-YoctoAutoBuilder- build #44 of nightly-fsl-ppc is complete: Failure [failed Building Toolchain Images Building Toolchain Images_1 Publishing Artifacts] Build details are at
*** alex_kag <alex_kag!~alex_kag@> has joined #yocto04:02
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto04:11
*** alex_kag <alex_kag!~alex_kag@> has quit IRC04:15
*** Squix <Squix!> has joined #yocto04:16
*** Squix <Squix!> has quit IRC04:18
*** Squix <Squix!> has joined #yocto04:19
*** khem <khem!> has quit IRC04:35
*** Squix <Squix!> has quit IRC04:41
*** Squix <Squix!> has joined #yocto04:41
*** khem <khem!~Thunderbi@> has joined #yocto04:46
*** Jefro <Jefro!> has joined #yocto04:48
*** Squix <Squix!> has quit IRC04:52
*** Squix <Squix!> has joined #yocto04:53
*** Jefro <Jefro!> has quit IRC05:00
*** chrobi_ <chrobi_!> has quit IRC05:02
*** Squix <Squix!> has quit IRC05:03
*** Squix <Squix!> has joined #yocto05:03
*** Jefro <Jefro!> has joined #yocto05:15
*** khem <khem!~Thunderbi@> has quit IRC05:17
*** khem <khem!~Thunderbi@> has joined #yocto05:18
*** Squix <Squix!> has quit IRC05:19
*** Squix <Squix!> has joined #yocto05:20
*** sunfunbaby <sunfunbaby!> has joined #yocto05:20
*** khem <khem!~Thunderbi@> has quit IRC05:23
*** synthesize <synthesize!> has left #yocto05:24
*** khem <khem!~Thunderbi@> has joined #yocto05:24
*** khem <khem!~Thunderbi@> has joined #yocto05:25
*** khem <khem!~Thunderbi@> has quit IRC05:26
*** trollixx <trollixx!> has quit IRC05:26
*** khem <khem!~Thunderbi@> has joined #yocto05:27
*** e8johan <e8johan!~quassel@> has joined #yocto05:28
*** Squix <Squix!> has quit IRC05:31
*** Squix <Squix!> has joined #yocto05:31
*** trollixx <trollixx!> has joined #yocto05:39
*** Squix <Squix!> has quit IRC05:41
*** Squix <Squix!> has joined #yocto05:42
*** trollixx <trollixx!> has quit IRC05:47
*** alex_kag <alex_kag!~alex_kag@> has joined #yocto05:51
*** Squix <Squix!> has quit IRC05:52
*** Squix <Squix!> has joined #yocto05:52
*** khem <khem!~Thunderbi@> has quit IRC05:55
*** khem <khem!~Thunderbi@> has joined #yocto05:56
*** Squix <Squix!> has quit IRC05:57
*** Squix <Squix!> has joined #yocto05:58
*** Jefro <Jefro!> has quit IRC06:02
*** SorenHolm <SorenHolm!> has joined #yocto06:03
*** roric <roric!> has joined #yocto06:09
*** SorenHolm <SorenHolm!> has quit IRC06:09
*** Squix <Squix!> has quit IRC06:20
*** Squix <Squix!> has joined #yocto06:20
*** agust <agust!> has joined #yocto06:22
*** linu <linu!~linu@> has joined #yocto06:24
linuhi i try to load g_multi gadget module in my at91sam9g35 board it shows me the following error,and i have used poky with meta-atmel, please see can you help me06:26
*** SorenHolm <SorenHolm!> has joined #yocto06:32
*** roric <roric!> has quit IRC06:38
*** SorenHolm <SorenHolm!> has quit IRC06:41
*** khem <khem!~Thunderbi@> has quit IRC06:45
*** Squix <Squix!> has quit IRC06:47
*** linu <linu!~linu@> has quit IRC06:47
*** Squix <Squix!> has joined #yocto06:47
*** Squix <Squix!> has quit IRC07:03
*** Squix <Squix!> has joined #yocto07:04
*** Squix <Squix!> has quit IRC07:08
*** GusBricker <GusBricker!> has quit IRC07:09
*** Squix <Squix!> has joined #yocto07:09
*** g1zer0 <g1zer0!> has joined #yocto07:15
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC07:30
*** sameo <sameo!~samuel@> has quit IRC07:30
*** kbart <kbart!~KBart@> has joined #yocto07:32
*** ak77 <ak77!c12e4b04@gateway/web/freenode/ip.> has joined #yocto07:33
ak77i want to upgrade SD card with new image but on a system running from that SD card. tried with simple umount, dd, reboot, but had many errors.07:34
*** SorenHolm <SorenHolm!> has joined #yocto07:35
tobiash_ak77: I do that with a second partition containing a minimal sysroot07:36
tobiash_ak77: you can switch to the second partition with systemctl switch-root and flash the first partition from there07:36
ak77i'm not using systemd (yet).07:38
ak77but yes. second partition. hmm.07:38
*** roric <roric!~roric@> has joined #yocto07:39
tobiash_I also do an emergency remount ro before flashing07:40
*** B4gder <B4gder!> has joined #yocto07:41
tobiash_(I wasn't able to unmount the original root somehow)07:41
*** e8johan <e8johan!~quassel@> has quit IRC07:43
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto07:44
*** panda84kde <panda84kde!> has joined #yocto07:44
*** tasslehoff <tasslehoff!~tasslehof@> has joined #yocto07:48
*** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has joined #yocto07:52
*** evanp_ <evanp_!~evan@> has joined #yocto07:55
*** boz_v1 <boz_v1!> has quit IRC07:55
*** boz_v1 <boz_v1!> has joined #yocto07:55
*** michael_e_brown <michael_e_brown!~michaeleb@> has quit IRC07:56
*** evanp <evanp!~evan@> has quit IRC07:56
*** michael_e_brown <michael_e_brown!~michaeleb@> has joined #yocto07:57
*** n01 <n01!> has joined #yocto08:02
*** e8johan <e8johan!> has joined #yocto08:09
*** eballetbo <eballetbo!> has joined #yocto08:12
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC08:16
*** florian_kc is now known as florian08:24
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto08:28
*** mihai <mihai!~mihai@> has quit IRC08:29
*** elmi82 <elmi82!> has joined #yocto08:34
*** W1N9Zr0 <W1N9Zr0!> has quit IRC08:34
*** sameo <sameo!~samuel@> has joined #yocto08:35
*** rainerschuster <rainerschuster!> has joined #yocto08:36
*** zeddii_home <zeddii_home!> has quit IRC08:52
*** GusBricker <GusBricker!> has joined #yocto08:58
*** maharvey <maharvey!maharvey@nat/intel/x-hdnfidpdvoltxbbj> has joined #yocto09:00
*** maharvey <maharvey!maharvey@nat/intel/x-hdnfidpdvoltxbbj> has left #yocto09:10
*** rainerschuster <rainerschuster!> has left #yocto09:28
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto09:36
*** mihai <mihai!~mihai@> has joined #yocto09:44
bluelightningmorning all09:50
*** belen <belen!Adium@nat/intel/x-ahtfxtkjpxomovik> has joined #yocto09:51
LetoThe2ndhowdy bluelightning09:58
bluelightninghi LetoThe2nd09:59
*** belen <belen!Adium@nat/intel/x-ahtfxtkjpxomovik> has quit IRC10:03
*** ScriptRipper <ScriptRipper!~ScriptRip@opensuse/member/MartinMohring> has quit IRC10:06
*** mckoan|away is now known as mckoan10:07
mckoangood morning10:07
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC10:10
*** dany <dany!> has quit IRC10:12
*** dany <dany!> has joined #yocto10:12
*** dany <dany!> has quit IRC10:17
*** dany <dany!> has joined #yocto10:17
*** ScriptRipper <ScriptRipper!~ScriptRip@opensuse/member/MartinMohring> has joined #yocto10:20
*** jackmitc1 <jackmitc1!> has joined #yocto10:25
*** jackmitc1 <jackmitc1!> has quit IRC10:30
*** GusBricker <GusBricker!> has quit IRC10:47
ak77bluelightning: morning!10:48
*** bingbu <bingbu!~mars@> has quit IRC10:48
ak77still on the quest of searching why my recipe with CC -lbluetooth wants bluez4 package although I use bluez5, it tries to satisfy bluez4 (>= 4.101) *10:49
bluelightninghi ak7710:53
*** JimBaxter <JimBaxter!> has joined #yocto10:54
ak77dependency got into my package's build/tmp/work/ARCH/${PN}/${PV}-${PR}/packages-split/${PN}.shlibdeps10:55
bluelightningak77: it must be linking against the wrong library then10:55
bluelightningak77: I'd suggest looking at the compile logs and what's in the sysroot10:56
*** ScriptRipper <ScriptRipper!~ScriptRip@opensuse/member/MartinMohring> has quit IRC10:56
ak77bluelightning: the sysroot has only bluez5 libs, "bitbake mypackage" build allright10:58
*** _tid <_tid!> has quit IRC10:58
ak77bluelightning: it fails during do_rootfs, when it's installing ipks10:58
bluelightningak77: right, I got that10:59
bluelightningak77: anything of interest in log.do_package?11:01
ak77bluelightning: calculation of shlib requirements concludes with: DEBUG: brcm-patchram-plus-usb: Dependency requires package bluez411:03
*** belen1 <belen1!Adium@nat/intel/x-fcvxalpvyqqyxgxq> has joined #yocto11:04
bluelightningak77: that says that bluez4 must have been built11:07
*** ScriptRipper <ScriptRipper!~ScriptRip@opensuse/member/MartinMohring> has joined #yocto11:09
bluelightningak77: try: grep tmp/sstate-control/manifest-*11:10
*** zeddii <zeddii!~ddez@> has quit IRC11:13
*** _tid <_tid!> has joined #yocto11:13
*** mulhern <mulhern!> has joined #yocto11:15
ak77bluelightning: indeed. there are two, (one for bluez4 and one for bluez5) and then there is (bluez4) and
bluelightningak77: ok... so assuming you did clean it before as I suggested, something is still depending upon it11:17
bluelightningak77: to find out what that is, you can do bitbake -g <whatever you normally build> and then grep the .dot files produced for bluez411:17
*** zeddii <zeddii!~ddez@> has joined #yocto11:18
*** n01 <n01!> has quit IRC11:18
ak77bluelightning: khm.. now after bitbake bluez4 -c cleansstate, manifest show only bluez5. now i'll try to bitbake mypackage to see if it brings it back11:19
bluelightningak77: right, clean/cleansstate would remove the sysroot parts and hence the manifests for them11:19
*** n01 <n01!> has joined #yocto11:20
*** W1N9Zr0 <W1N9Zr0!> has joined #yocto11:25
*** Leo___ <Leo___!> has joined #yocto11:28
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has joined #yocto11:28
*** belen1 <belen1!Adium@nat/intel/x-fcvxalpvyqqyxgxq> has quit IRC11:30
Leo___Anybody that can gives me a tip why bit bake is failing on the last do_rootfs task when trying to build fsl-image-gui? everything seems to have compiled but I got an error "package architecture (armel) does not match system (i386)" and 1.| The following packages have unmet dependencies:11:31
Leo___2.|  packagegroup-core-x11-base : Depends: packagegroup-core-x11-utils but it is not going to be installed"11:31
*** belen1 <belen1!~Adium@> has joined #yocto11:31
Leo___full error log here:
ak77bluelightning: i also did cleanall on my package. now it doesn't compile. can't find includes (bluetooth/bluetooth.h)11:32
bluelightningak77: if bluez4 and bluez5 are deploying the same files, you may need to clean and build bluez5 again11:33
Marex_Hi guys, I have another stupid question. Where can I find documentation for the difference between '+=' and '_append' operator please ?11:34
Marex_I just recently used VAR_mymachine += ' package ' , which broke my build, while VAR_append_mymachine = ' package ' did not.11:35
ak77bluelightning: thank you. that was solved by clean/build of bluez5,11:35
bluelightningMarex_: the bitbake manual11:36
RPMarex_: look at the bitbake manual. The difference is when the addition is applied. one is immediate, the other deferred11:36
*** _tid <_tid!> has quit IRC11:36
bluelightningright, what he said :)11:36
bluelightninghi Marex_ btw :)11:36
Marex_ this is what I was looking for !11:36
Marex_wow, thank you !11:36
RPLeo___: that looks like the debian package backend, you might have more success with opkg11:37
Marex_bluelightning: hey :)11:39
ak77bluelightning: yes, cleaning of all three involved packages (bluez4, bluez5, mypackage) and rebuilding did the trick. thank you.11:40
Marex_RP: so if I use _append , it's deffered ?11:40
bluelightningak77: right, but I'm still curious as to how you got into this situation - if something does depend on bluez4 directly in your build, you'll likely hit the same problem later on11:40
bluelightningMarex_: right, the other difference is that += adds a space when appending, whereas _append does not11:41
RPMarex_: ye11:41
ak77bluelightning: i tried to compile alsa, maybe it picked it up... but this is 'negative surprise', how can system pick up something just because it's there. to be sure one would have to delete everything.11:42
bluelightningak77: well, ideally we'd flag up this conflict and fail the build immediately11:43
bluelightningak77: I'm not sure what mechanism we'd use to do that though11:43
Marex_bluelightning: I got that "far" (but I do appreciate the help!), I am now trying to wrap my head around this "deferred" appending though11:46
bluelightningMarex_: with += the value is appended immediately when the line is parsed11:47
bluelightningMarex_: with _append, it is put into a separate area and gets appended each time the value of the variable is expanded (usually at some much later time)11:48
*** _tid <_tid!> has joined #yocto11:48
Marex_bluelightning: so if I use this with DEPENDS (DEPENDS_mymachine += vs. DEPENDS_append_mymachine = ), what happens there please ?11:49
Marex_bluelightning: I am starting it catch up ... maybe ;-/11:49
*** GusBricker <GusBricker!> has joined #yocto11:49
bluelightningMarex_: that is a good question; basically you should not mix overrides and += because the two operations will happen at different times, and because of the override you'll usually end up stomping on the value instead of appending to it11:49
Marex_bluelightning: so the rule of the thumb here is to use _append with DEPENDS, right ?11:50
bluelightningMarex_: use _append in conjunction with overrides11:51
*** wdenk1 <wdenk1!> has joined #yocto11:51
bluelightningMarex_: such as _mymachine11:51
bluelightningMarex_: it would be DEPENDS_append_mymachine = " somevalue"11:51
bluelightningMarex_: another note, if you're effectively making the recipe machine-specific by doing this, you'll also want to do PACKAGE_ARCH = "${MACHINE_ARCH}" for the recipe so that multi-machine builds continue to work properly11:52
bluelightningMarex_: (assuming it's not already machine-specific, that is)11:53
*** sameo <sameo!~samuel@> has quit IRC11:54
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto11:54
lpapprburton: I am not sure what you mean by linux is fetched from git, and that can help me.11:54
lpappI cannot find a .git folder after the fetch.11:54
rburtonlpapp: the yocto-kernel recipe is built from a git clone11:54
Marex_lpapp: see your download dir and there'll be something like git2/ , in there, you'll find the directory with the git repo11:55
lpappMarex_: I do not.11:55
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC11:55
Marex_lpapp: there won't be any .git directory anywhere, it's doing bare clone11:55
Marex_bluelightning: gotcha, thank you !11:55
lpappwell, that is not helpful for patch recreation.11:55
lpappalso, we do not have git2 since that would be an embedded git inside a git which is apparently calling for troubles with Yocto.11:56
lpapprburton: well, I thought git diff could be helpful, but apparently there is no such a thing here for my build dir changes.11:58
lpappso I still need to go back to the raw diff?11:59
Marex_bluelightning: so if I use _append with overrides, like _mymachine, the append will happen only after the override is processed, right ?12:01
Marex_bluelightning: if I use += , the contents of the variable might be dropped once the override is processed ?12:01
bluelightningMarex_: with += the plain, non-overridden value would be dropped when the override applies, yes12:02
*** rainerschuster <rainerschuster!> has joined #yocto12:02
bluelightningMarex_: which is usually not desirable12:02
bluelightningMarex_: if you really do mean that to happen (which is sometimes the case) you'd just do MYVAR_mymachine = rather than += and fully express the value12:03
lpappMarex_: _append will be added at the end of the parsing, so it is guaranteed to be there. += is an immediate assignment. so if AA += "BB" is followed later by AA = "CC", then it would be lost12:03
*** rainerschuster <rainerschuster!> has quit IRC12:06
Marex_bluelightning: ah, got it now, thank you very much!12:07
bluelightningMarex_: np12:08
Marex_bluelightning: I owe you a beverage of your preference, remind me in dusseldorf :)12:10
bluelightningMarex_: :)12:15
Crofton|workwe need a beer fund12:15
Marex_Crofton|work: make a fundraiser campain :)12:17
Crofton|workthis is on the todo list12:17
Marex_is that the kind of todo list that looks like an infinite roll of toilet paper ?12:18
*** Squix <Squix!> has quit IRC12:21
*** GusBricker <GusBricker!> has quit IRC12:22
*** joeythesaint <joeythesaint!~jjm@> has joined #yocto12:57
*** Zaif <Zaif!> has joined #yocto12:59
*** Leo___ <Leo___!> has quit IRC13:23
*** sameo <sameo!~samuel@> has joined #yocto13:27
*** davest <davest!~Adium@> has joined #yocto13:37
*** fpaut_ is now known as fpaut13:37
*** dany <dany!> has quit IRC13:40
*** dany <dany!> has joined #yocto13:44
vicenteolivertMaybe this is a silly question... How can I know what version of gcc Yocto is using? And more important..., how can I change it?13:47
bluelightningvicenteolivert: this will tell you: bitbake -s | grep gcc13:48
vicenteolivertbluelightning: that's the gcc used to compile my target? (the gcc of the toolchain)13:50
*** fpaut is now known as fpaut_13:51
*** belen1 <belen1!~Adium@> has quit IRC13:51
*** davest <davest!~Adium@> has quit IRC13:51
bluelightningvicenteolivert: gcc-cross is, yes13:53
*** belen <belen!Adium@nat/intel/x-muhixwvqxeljmojp> has joined #yocto13:53
*** belen1 <belen1!~Adium@> has joined #yocto13:56
*** alex_kag <alex_kag!~alex_kag@> has quit IRC13:57
*** belen <belen!Adium@nat/intel/x-muhixwvqxeljmojp> has quit IRC13:58
*** groleo <groleo!groleo@nat/intel/x-usfnkndgvcznctiz> has joined #yocto14:00
*** belen1 <belen1!~Adium@> has quit IRC14:02
*** challinan <challinan!> has quit IRC14:05
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto14:09
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC14:09
*** rainerschuster <rainerschuster!> has joined #yocto14:15
*** tasslehoff <tasslehoff!~tasslehof@> has quit IRC14:17
*** Jay7 <Jay7!> has quit IRC14:24
*** challinan <challinan!> has joined #yocto14:25
*** Jay7 <Jay7!> has joined #yocto14:25
*** groleo <groleo!groleo@nat/intel/x-usfnkndgvcznctiz> has quit IRC14:26
*** sroy <sroy!~sroy@2607:fad8:4:6:3e97:eff:feb5:1e2b> has joined #yocto14:34
*** mihai <mihai!~mihai@> has quit IRC14:34
ak77I have a function in ROOTFS_POSTPROCESS_COMMAND in a image-making recipe. what variable containes path to host sysroot (where are native tools get installed). (${D} doesnt point to right directory)14:53
ak77in that function, I need to access some files i placed in /usr/share/xy when installing my native tool.14:54
*** reallife <reallife!> has joined #yocto14:54
ndecak77: STAGING_DIR_NATIVE i believe is what you need.14:57
ndecor its BINDIR or INCDIR variant14:57
ndecand btw, $D is never the sysroot, but an intermediate folder in the recipe WORKDIR, used before files get installed/populated in the sysroot14:58
*** Squix <Squix!> has joined #yocto14:58
*** khem <khem!> has joined #yocto15:04
*** alex_kag <alex_kag!~alex_kag@> has joined #yocto15:05
*** belen <belen!Adium@nat/intel/x-yewoncdzgynrwnbn> has joined #yocto15:08
ak77ndec: thankyou15:09
*** SorenHolm <SorenHolm!> has quit IRC15:10
*** ak77 <ak77!c12e4b04@gateway/web/freenode/ip.> has quit IRC15:14
*** rainerschuster <rainerschuster!> has left #yocto15:32
*** kscherer_ <kscherer_!~kscherer@> has joined #yocto15:35
*** munch <munch!> has joined #yocto15:37
*** sunfunbaby <sunfunbaby!> has quit IRC15:39
*** _tid <_tid!> has quit IRC15:40
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC15:43
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has quit IRC15:46
*** dlern <dlern!~dlerner@> has quit IRC15:46
*** khem <khem!> has quit IRC15:51
*** Jefro <Jefro!> has joined #yocto15:58
*** ak77 <ak77!c12e4b04@gateway/web/freenode/ip.> has joined #yocto16:06
*** davest <davest!~Adium@> has joined #yocto16:11
*** lpapp <lpapp!~lpapp@kde/lpapp> has left #yocto16:12
*** dlern <dlern!~dlerner@> has joined #yocto16:13
*** hollisb <hollisb!> has joined #yocto16:13
*** dlern <dlern!~dlerner@> has left #yocto16:14
*** dlern <dlern!~dlerner@> has joined #yocto16:15
*** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has quit IRC16:20
*** fpaut_ is now known as fpaut16:22
*** davest <davest!~Adium@> has quit IRC16:23
*** fpaut is now known as fpaut_16:27
*** elmi82 <elmi82!> has quit IRC16:28
vicenteolivertCan anyone help me setting up the sourcery toolchain please? I have downloaded the "meta-sourcery" layer and put it on the poky dir. Then, I have added that layer to my bblayers.conf file, just before the meta layer. Then I downloaded the sourcery codebench tarball and extracted it (that created the ~/mips-2013.05 directory). Then I have added EXTERNAL_TOOLCHAIN = "/home/myuser/mips-2013.05" to local.conf16:28
kergothsounds about right. what's the issue?16:29
vicenteolivertIt fails with:16:30
vicenteolivert /usr/include/gnu/stubs.h:7:27: error: gnu/stubs-32.h: No such file or directory16:30
kergothif it's including /usr/include headers, that sounds like you'er failing in a native recipe, not a target one, so it isn't even failing in a recipe that uses the external toolchain16:31
kergothwhat exactly is failing? which recipe?16:31
*** mckoan is now known as mckoan|away16:31
bluelightningvicenteolivert: maybe try NO32LIBS = "1" in local.conf ?16:32
vicenteolivertbluelightning: will that affect to my target system? I'm building a MIPS32 target system.16:33
bluelightningvicenteolivert: no, that's just for the native (build host) part16:33
bluelightningin fact it's only looked at by the pseudo recipe16:33
vicenteolivertOk, added and running the "bitbake core-image-minimal" again.16:34
*** davest <davest!~Adium@> has joined #yocto16:34
vicenteolivertNo..., more errors :-(16:34
bluelightningvicenteolivert: the same error or something else?16:35
kergothyou need to be more specific, if you have an error, post it16:35
bluelightningand use pastebin for the errors ;)16:35
bluelightningif > 2 lines16:35
vicenteolivertYes, sorry, the error has occured right now. I'm looking at it :-P16:35
vicenteolivertIt's not the same recipe. It has failed installing the external toolchain. I'll paste it.16:36
vicenteolivertbluelightning, kergoth:
vicenteolivertThe directory is trying to find it doesn't exists.16:39
*** dlern1 <dlern1!~dlerner@> has joined #yocto16:41
*** dlern <dlern!~dlerner@> has quit IRC16:41
*** dlern1 <dlern1!~dlerner@> has quit IRC16:47
*** eballetbo <eballetbo!> has quit IRC16:48
*** pidge <pidge!~eflanagan@> has joined #yocto16:52
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC16:54
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto16:54
*** slips <slips!~slips@> has quit IRC16:55
vicenteolivertbluelightning, kergoth: any clues?17:01
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto17:02
kergothHmm, odd, never seen that one. which toolchain is this?17:03
vicenteolivertkergoth: Sourcery Codebench.17:03
*** bluelightning_ <bluelightning_!~paul@> has joined #yocto17:03
*** bluelightning_ <bluelightning_!~paul@> has quit IRC17:03
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto17:03
vicenteolivertI'm following the instructions:
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC17:04
*** bluelightning_ is now known as bluelightning17:04
*** belen <belen!Adium@nat/intel/x-yewoncdzgynrwnbn> has quit IRC17:04
*** dvhart <dvhart!~dvhart@> has joined #yocto17:05
*** belen <belen!~Adium@> has joined #yocto17:05
*** belen2 <belen2!Adium@nat/intel/x-ylrfphjpfvhijskz> has joined #yocto17:05
*** belen3 <belen3!~Adium@> has joined #yocto17:07
kergothvicenteolivert: obviously, it's codebench17:07
kergothwhat *exact* version? pro or lite?17:08
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC17:08
kergothi hae to support like 32 combinations of arch and versions with that layer17:08
vicenteolivertkergoth: lite.17:08
kergothi can't test them all17:08
vicenteolivertkergoth: mips-2013.11-36-mips-linux-gnu-i686-pc-linux-gnu.tar.bz217:08
kergoththank you, that'ss what i needed17:08
vicenteolivertkergoth: do you want the link so I can save you time?17:08
kergothI'll pull it down and try to repro17:08
*** belen <belen!~Adium@> has quit IRC17:09
*** JaMa <JaMa!> has quit IRC17:09
vicenteolivertkergoth: thank you very much for your time and help :-)17:10
kergothexcellent, thanks17:10
*** belen3 <belen3!~Adium@> has left #yocto17:10
*** belen3 <belen3!~Adium@> has joined #yocto17:10
*** belen2 <belen2!Adium@nat/intel/x-ylrfphjpfvhijskz> has quit IRC17:10
kergothThe lite ones usually aren't a priority for us, but we do try to ensure they stay working with yocto17:10
vicenteolivertkergoth: aha.17:11
vicenteolivertkergoth: I will be off work in a few minutes, so please, don't be upset if you talk me and I don't reply. That's because I'm not here.17:12
*** zenlinux_ <zenlinux_!> has joined #yocto17:19
vicenteolivertThe reason I'm trying to use this external toolchain is because I need to build a target with micromips support (rootfs compiled with -mmicromips CFLAG). If I try to do that using the Yocto toolchain it fails because it's gcc doesn't recognize that option. I don't know why, because as fas as I know, that option was introduced in Mar 2013, so gcc-4.8.2 should have it.17:23
LetoThe2ndhowdy! how to make fortran available as a dependency?17:24
*** dlern <dlern!~dlerner@> has joined #yocto17:26
*** Squix <Squix!> has quit IRC17:29
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has joined #yocto17:29
LetoThe2nda simple DEPENDS doesn't seem to do the trick17:30
bluelightningvicenteolivert: where were you setting the CFLAGS though?17:31
*** n01 <n01!> has quit IRC17:32
vicenteolivertbluelightning: in my local.conf, TARGET_CFLAGS_append = " -mmicromips"17:32
bluelightningvicenteolivert: ok17:32
vicenteolivertI have to go. See you tomorrow and have a nice day :-)17:37
kergothvicenteolivert: hmm, actually hit an entirely different failure than you did, i got past the toolchain install, but failed in libffi17:44
kergothactually, i think meta-mentor might have that fix, maybe i should move it or push to oe-core17:44
*** seebs <seebs!> has quit IRC17:46
*** SorenHolm <SorenHolm!> has joined #yocto17:48
LetoThe2ndany hints about needing fortran as a dependency?17:49
*** seebs <seebs!> has joined #yocto17:49
*** roric <roric!~roric@> has quit IRC17:54
*** SorenHolm <SorenHolm!> has quit IRC17:54
*** zenlinux_ <zenlinux_!> has quit IRC17:57
*** zenlinux_ <zenlinux_!> has joined #yocto17:57
* mr_science 's ears perk up at the mention of Fortran...17:57
mr_sciencehmm, not enough log today...17:58
mr_scienceLetoThe2nd: can you catch me up?17:58
mr_sciencedamn, i got a standup in 1 minute...17:59
LetoThe2ndmr_science: i want to make up a recipe for R, for which the docs say it needs fortran18:00
*** dvhart <dvhart!~dvhart@> has quit IRC18:00
*** alex_kag <alex_kag!~alex_kag@> has quit IRC18:10
*** belen3 <belen3!~Adium@> has quit IRC18:14
*** bluelightning_ <bluelightning_!~paul@> has joined #yocto18:15
*** bluelightning_ <bluelightning_!~paul@> has quit IRC18:15
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto18:15
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC18:16
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC18:21
mr_scienceLetoThe2nd: i did some R hacking, er, packaging on Gentoo a while back18:21
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto18:21
mr_sciencei don't have access to my yocto build right now, but initially it would depend on the toolchain config18:22
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC18:22
mr_scienceie, --languages=foo18:22
mr_scienceno reason not to build gfortran, since you pretty much get it for free18:22
*** alex_kag <alex_kag!~alex_kag@> has joined #yocto18:23
mr_scienceif it's not already being built that way, you could try a bbappend to add --languages=c,c++,fortan or whatever18:23
mr_sciencebut that's really my ass talking without actually looking at it...18:24
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC18:26
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto18:26
LetoThe2ndmr_science: no worries, the input is much appreciated18:26
mr_sciencei have a drs appt this afternoon so i could probably take a look when i get back18:28
mr_scienceis there an existing bug, or?18:28
LetoThe2ndyou mean the fortran thing?18:33
mr_scienceyeah, if you want a test build/bbappend that should be doable18:35
mr_scienceshould be able to at least build a toolchain with fortran18:36
mr_sciencedo you have any recipes to test yet?18:37
LetoThe2ndno, nothing at all. just at the very beginning18:37
mr_scienceso there's essentially no R stuff at all yet?18:39
mr_sciencein anything meta-* anyway...18:39
LetoThe2ndnothing that i'm aware of18:42
*** jackmitchell1 <jackmitchell1!> has joined #yocto18:43
kergothi think richard looked into / improved the fortran support recently, it's ringing a bell18:43
kergothe.g. [OE-core] [PATCH] gcc: Allow fortran to build successfully in 4.818:44
kergothsearch oe-core list archives for fortran18:44
*** roric <roric!> has joined #yocto18:44
kergothIIRC there's a variable for what gets passed to --languages= that you can change18:45
mr_sciencesounds good18:45
kergothLANGUAGES maybe? something along those lines18:45
kergothcheck the gcc recipes :)18:45
LetoThe2ndjust pulled, will now look at it18:45
mr_scienceLetoThe2nd: if you can, let me know if you make any progress today18:47
mr_sciencestephen.arnold42 at the gmail will work...18:47
LetoThe2ndmr_science: well you are araound here, not?18:48
mr_sciencethere's also the github issue tracker that nobody has used yet18:48
mr_scienceyeah, i will be a bit later18:48
mr_scienceLetoThe2nd: you can be the first:
mr_sciencethis should be more interesting than your average packaging task...18:57
* LetoThe2nd has just kicked off the rebuild to see whats going on.18:58
-YoctoAutoBuilder- build #46 of nightly-x86-64-lsb is complete: Failure [failed Building Images Building Images_1 Publishing Artifacts] Build details are at
LetoThe2ndwell i found
LetoThe2ndbut does this mean to do nothing at all because a toolchain rebuild will geive me fortran? or shall i depend on libgfortran now?19:05
kergothyou still need to ensure fortran is enabled in gcc languages, no?19:07
kergoththat commit just ensures the fortran lib is packaged as well19:07
LetoThe2ndah ok19:08
* mr_science still thinking about how to integrate that one...19:09
kergothLANGUAGES ?= "c,c++${FORTRAN}${JAVA}"19:09
kergothlooks like you just need to set FORTRAN=",f77"19:09
kergothfrom a quick look at the gcc recipes, asi pointed out earlier19:10
kergoththe var is even named what i thought it was :P19:10
LetoThe2ndkergoth: :)19:13
*** SorenHolm <SorenHolm!> has joined #yocto19:15
kergothah, looks like sets FORTRAN = "" specifically19:16
kergothso you'd actually want to set LANGUAGES = "c,c++,f77"19:16
*** maharvey <maharvey!~maharvey@> has joined #yocto19:16
LetoThe2ndyes. a bbappend should do, right?19:17
kergothor local.conf, LANGUAGES is set with ?=19:18
*** maharvey <maharvey!~maharvey@> has quit IRC19:18
kergoth?= is set only if unset, so the config metadata would take precedence if set19:18
kergothobviously a bbappend is better for long term maintenance19:18
kergothdepends on your goals19:18
LetoThe2ndgoal == learning, tinkering19:19
*** n01 <n01!> has joined #yocto19:21
* kergoth nods19:22
kergothlocal.conf for a temporary change to see if it works is what i'd do :)19:22
mr_scienceif you set it to --enable-languages=c,c++,fortran you should get both f77 and newer19:25
kergothah, nice19:26
kergothgood call19:26
kergothi think richard removed the f77 bits from the metadata, so that'd be much better :)19:26
mr_sciencemeaning it should actually work...  ;)19:27
kergothindeed :)19:29
mr_sciencei'd wager most people don't mess with fortran19:29
kergothi'm kind of surprised richard put time into making sure it worked, he must have been bored19:29
-YoctoAutoBuilder- build #46 of minnow-lsb is complete: Failure [failed Building Images] Build details are at
mr_sciencemaybe he was science geek at some point in the past?19:30
* mr_science might have one of the only fortran projects on github19:30
mr_sciencealmost certainly the only windfield model...19:30
mr_sciencei'm sure *that* would get lots of action if i packaged it for yocto...19:31
kergothone of the many languages i never learned19:32
mr_scienceit's pretty cool, with real publications and everything19:33
*** sroy <sroy!~sroy@2607:fad8:4:6:3e97:eff:feb5:1e2b> has quit IRC19:33
mr_science  <=  it's operational in several orgs19:33
*** chrobi <chrobi!> has joined #yocto19:36
LetoThe2ndi currently more thinking about use cases of statistics/R in embedded controls19:40
kergothsounds quite interesting19:40
LetoThe2ndthats why i'm looking into it19:41
*** jackmitchell1 <jackmitchell1!> has quit IRC19:41
*** SorenHolm <SorenHolm!> has quit IRC19:42
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto19:46
mr_scienceR is nice tool19:46
mr_sciencewhich i don't get to play with much any more...19:47
*** zenlinux_ <zenlinux_!> has quit IRC19:48
*** zenlinux_ <zenlinux_!> has joined #yocto19:48
LetoThe2ndthere are so many nice tools and so little time19:48
*** SorenHolm <SorenHolm!> has joined #yocto19:51
-YoctoAutoBuilder- build #46 of nightly-qa-systemd is complete: Success [build successful] Build details are at
kergothi really want to spend more time with Go19:52
mr_scienceon the development/V&V side there are some really nice/little-used tools19:52
mr_scienceactual formal verification stuff, using model checking, SAT solvers, etc19:53
mr_scienceand some of the cleanest-looking opensource c++ code i've seen19:54
mr_sciencetake a gander at this source =>
mr_sciencei wish more people would give a crap about their (public) code...19:55
* mr_science goes back to his build branch migration19:56
*** ccube <ccube!> has quit IRC20:06
*** ccube <ccube!> has joined #yocto20:08
mr_sciencepulled-pork sandwiches today...20:10
*** maharvey <maharvey!maharvey@nat/intel/x-prbacipmzckzdcid> has joined #yocto20:13
*** zenlinux_ <zenlinux_!> has quit IRC20:20
*** zenlinux_ <zenlinux_!> has joined #yocto20:20
*** zeddii_home <zeddii_home!> has joined #yocto20:24
*** sameo <sameo!~samuel@> has quit IRC20:28
*** wdenk2 <wdenk2!> has joined #yocto20:32
*** wdenk1 <wdenk1!> has quit IRC20:32
*** maharvey <maharvey!maharvey@nat/intel/x-prbacipmzckzdcid> has quit IRC20:37
*** dany <dany!> has quit IRC20:39
*** dany <dany!> has joined #yocto20:39
*** jdvdt_ <jdvdt_!> has joined #yocto20:42
*** roric <roric!> has quit IRC20:43
-YoctoAutoBuilder- build #45 of build-appliance is complete: Failure [failed Building Images] Build details are at
*** jdvdt <jdvdt!> has left #yocto20:50
*** JimBaxter <JimBaxter!> has quit IRC20:54
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC21:03
*** maharvey <maharvey!maharvey@nat/intel/x-fdfvelpgqcltihsx> has joined #yocto21:03
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has quit IRC21:05
*** roric <roric!> has joined #yocto21:06
*** jdvdt <jdvdt!> has joined #yocto21:14
-YoctoAutoBuilder- build #45 of nightly-fsl-ppc is complete: Success [build successful] Build details are at
*** joeythesaint <joeythesaint!~jjm@> has quit IRC21:22
*** maharvey <maharvey!maharvey@nat/intel/x-fdfvelpgqcltihsx> has quit IRC21:22
*** maharvey <maharvey!~maharvey@> has joined #yocto21:24
-YoctoAutoBuilder- build #45 of nightly-x86-lsb is complete: Failure [failed Building Images_1] Build details are at
-YoctoAutoBuilder- build #45 of nightly-arm-lsb is complete: Failure [failed Building Images_1] Build details are at
-YoctoAutoBuilder- build #45 of nightly-mips-lsb is complete: Failure [failed Building Images_1] Build details are at
*** davest <davest!~Adium@> has quit IRC21:56
*** maharvey <maharvey!~maharvey@> has quit IRC21:56
*** davest <davest!~Adium@> has joined #yocto21:58
*** zenlinux_ <zenlinux_!> has quit IRC21:59
*** zenlinux_ <zenlinux_!> has joined #yocto21:59
*** sameo <sameo!~samuel@> has joined #yocto22:01
*** GusBricker <GusBricker!> has joined #yocto22:01
*** maharvey <maharvey!~maharvey@> has joined #yocto22:04
*** SorenHolm <SorenHolm!> has quit IRC22:17
*** panda84kde <panda84kde!> has quit IRC22:21
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto22:23
*** dlern <dlern!~dlerner@> has quit IRC22:29
*** davest <davest!~Adium@> has quit IRC22:35
*** zenlinux_ <zenlinux_!> has quit IRC22:37
*** zenlinux_ <zenlinux_!> has joined #yocto22:37
kergothI have to say, I kind of hate the bits where libx11 refuses to be buildable without x11 in distro features. it's a useful sanity check, but building it doesn't mean I'm linking much against it, or that it'll end up in my images..22:47
RPkergoth: I can't say I'm that keen either fwiw but equally there wasn't any opposition to the patches :/22:49
kergothit's certainly been around for a while now. it's not always a problem, but is occasionally annoying/limiting22:51
* kergoth mulls over such things as an opt-in/opt-out sanity check rather than a requirement22:51
-YoctoAutoBuilder- build #46 of nightly-ppc-lsb is complete: Failure [failed Building Images_1] Build details are at
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC22:58
*** bfederau <bfederau!> has quit IRC23:01
*** bfederau <bfederau!> has joined #yocto23:01
*** agust <agust!> has quit IRC23:03
*** gagi <gagi!> has quit IRC23:04
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto23:04
*** gagi <gagi!> has joined #yocto23:04
*** Jefro <Jefro!> has quit IRC23:05
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC23:07
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto23:08
*** zenlinux_ <zenlinux_!> has quit IRC23:10
*** zenlinux_ <zenlinux_!> has joined #yocto23:10
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC23:10
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto23:11
*** jzhang <jzhang!~jzhang@> has left #yocto23:15
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC23:16
*** n01 <n01!> has quit IRC23:16
*** [simar|on] <[simar|on]!> has joined #yocto23:18
*** pidge1 <pidge1!pidge@nat/intel/x-tbjetpcfwifweojt> has joined #yocto23:20
*** pidge1 is now known as pidge_laptop23:20
*** jzhang <jzhang!~jzhang@> has joined #yocto23:21
RPkergoth: you could probably knock out the check with a suitable override from local.conf I guess :)23:26
*** pidge_laptop <pidge_laptop!pidge@nat/intel/x-tbjetpcfwifweojt> has quit IRC23:29
*** Guest21451 <Guest21451!~tinti@pdpc/supporter/student/tinti> has joined #yocto23:31
*** zaif_ <zaif_!~Zaif@> has joined #yocto23:34
-YoctoAutoBuilder- build #50 of buildtools is complete: Failure [failed Building Images Building Images_1 Publishing Artifacts] Build details are at
*** jzhang <jzhang!~jzhang@> has quit IRC23:39
*** pidge1 <pidge1!pidge@nat/intel/x-hrzyjqxkzzzsedxj> has joined #yocto23:40
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC23:42
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto23:42
*** seebs <seebs!> has quit IRC23:43
*** Squix <Squix!> has joined #yocto23:49
*** pidge1 <pidge1!pidge@nat/intel/x-hrzyjqxkzzzsedxj> has quit IRC23:51
*** seebs <seebs!> has joined #yocto23:53
*** hollisb <hollisb!> has quit IRC23:55
*** zenlinux_ <zenlinux_!> has quit IRC23:57
*** JaMa <JaMa!> has joined #yocto23:59

Generated by 2.11.0 by Marius Gedminas - find it at!