Wednesday, 2013-09-04

abellonithe end result is that you have more chances of overlapping interesting talks00:00
mranostayabelloni: yeah00:03
mranostayat least my talk is the first day00:03
mranostayand not the first of the day00:04
*** munch <munch!> has quit IRC00:05
mranostayabelloni: yeah i see a few overlaps00:06
mranostaypanto or Tartarus... hard choice00:06
*** thaytan <thaytan!> has quit IRC00:08
*** thaytan <thaytan!> has joined #yocto00:08
*** cfo215 <cfo215!> has quit IRC00:08
*** _julian_ <_julian_!> has quit IRC00:10
*** _julian <_julian!> has joined #yocto00:11
*** davest <davest!Adium@nat/intel/x-wutugomfwvbqxulr> has quit IRC00:19
*** mulhern <mulhern!> has quit IRC00:25
*** RagBal <RagBal!> has joined #yocto00:33
*** Rootert <Rootert!> has joined #yocto00:33
*** mulhern <mulhern!> has joined #yocto00:43
*** scot_ <scot_!~scot@> has quit IRC00:49
*** OSNinja <OSNinja!> has quit IRC00:52
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has quit IRC00:53
*** mulhern <mulhern!> has quit IRC01:00
*** mulhern <mulhern!> has joined #yocto01:09
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto01:16
halsteadsgw_, All the builders except 02 are ready. You could start a MUT now.01:23
*** smartin <smartin!> has joined #yocto01:24
*** smartin_ <smartin_!> has quit IRC01:25
*** Crofton|work <Crofton|work!> has quit IRC01:26
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto01:26
*** mulhern <mulhern!> has quit IRC01:27
*** Crofton|work <Crofton|work!> has joined #yocto01:31
*** smartin_ <smartin_!> has joined #yocto01:32
*** smartin <smartin!> has quit IRC01:35
*** Net147 <Net147!> has joined #yocto01:42
*** Net147 <Net147!> has quit IRC01:54
*** _Lucretia__ <_Lucretia__!~munkee@> has quit IRC02:00
*** silviof1 <silviof1!~silviof@unaffiliated/silviof> has joined #yocto02:01
*** silviof <silviof!~silviof@unaffiliated/silviof> has quit IRC02:03
*** mitz <mitz!> has quit IRC02:21
*** mitz <mitz!> has joined #yocto02:23
*** uvan <uvan!~uvan@> has joined #yocto02:24
*** _Lucretia_ <_Lucretia_!~munkee@pdpc/supporter/active/lucretia> has joined #yocto02:29
uvanhi all, i try to create a new images and got error: Error: locale-base-en-us not found in the base feeds (genericarmv8 aarch64 noarch any all)02:32
uvancould anyone tell me how to include locale in this case?02:33
*** JaMa <JaMa!> has quit IRC03:08
*** JaMa <JaMa!> has joined #yocto03:10
*** thaytan <thaytan!> has quit IRC03:31
*** andyross <andyross!> has joined #yocto03:46
*** thaytan <thaytan!> has joined #yocto03:47
*** honschu_ <honschu_!~honschu@shackspace/j4fun> has quit IRC03:59
*** roxell <roxell!~roxell@linaro/roxell> has quit IRC03:59
*** roxell <roxell!> has joined #yocto03:59
*** roxell <roxell!~roxell@linaro/roxell> has joined #yocto03:59
*** honschu <honschu!~honschu@shackspace/j4fun> has joined #yocto04:00
*** [simar|school] <[simar|school]!> has joined #yocto04:00
*** pev <pev!~pev@> has quit IRC04:05
*** Net147 <Net147!> has joined #yocto04:19
*** e8johan <e8johan!> has joined #yocto04:22
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has quit IRC04:44
*** _alex_kag_ <_alex_kag_!~alex_kag@> has joined #yocto04:49
*** amarsman <amarsman!> has joined #yocto04:57
*** silviof1 is now known as silviof04:59
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC05:05
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto05:06
*** andyross <andyross!> has quit IRC05:10
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC05:11
*** mihai <mihai!~mihai@> has quit IRC05:15
*** [simar|school] <[simar|school]!> has quit IRC05:30
lpappwhat is the codename for the next poky version?05:41
*** shoragan <shoragan!~jlu@debian/developer/shoragan> has quit IRC05:42
*** shoragan <shoragan!~jlu@2001:6f8:1178:2:219:99ff:fe56:8d7> has joined #yocto05:43
*** shoragan <shoragan!~jlu@debian/developer/shoragan> has joined #yocto05:43
*** kbart <kbart!~KBart@> has joined #yocto05:57
AlexGpidge: ping05:59
*** behanw_ <behanw_!> has quit IRC06:09
mranostayAlexG: little late here :)06:10
AlexGmranostay: ok06:13
*** behanw_ <behanw_!> has joined #yocto06:20
mranostayhi behanw_ !06:23
*** elmi82 <elmi82!> has joined #yocto06:29
mranostayAlexG: had a question?06:29
*** zecke <zecke!> has joined #yocto06:30
lpappAlexG: just ask06:37
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has joined #yocto06:38
*** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has joined #yocto06:43
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto06:52
*** W1N9Zr0 <W1N9Zr0!> has quit IRC06:55
*** W1N9Zr0 <W1N9Zr0!> has joined #yocto06:55
*** eballetbo <eballetbo!> has joined #yocto06:57
*** jwessel <jwessel!~jwessel@> has quit IRC06:57
*** jwessel <jwessel!~jwessel@> has joined #yocto06:58
*** mihai <mihai!~mihai@> has joined #yocto07:00
seebs <-- apparently, they have a sense of humor07:02
*** zeeblex <zeeblex!~apalalax@> has joined #yocto07:03
*** pirut <pirut!~Pirut@> has quit IRC07:04
*** pirut <pirut!~Pirut@> has joined #yocto07:06
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has joined #yocto07:11
*** zz_ka6sox is now known as ka6sox07:14
*** smartin <smartin!> has joined #yocto07:15
*** smartin_ <smartin_!> has quit IRC07:16
*** ant_work <ant_work!> has joined #yocto07:17
*** rburton <rburton!> has quit IRC07:18
*** dany <dany!> has quit IRC07:19
*** dany <dany!> has joined #yocto07:21
*** slaine <slaine!~slaine@> has joined #yocto07:21
*** rburton <rburton!> has joined #yocto07:21
*** [1]uvan <[1]uvan!~uvan@> has joined #yocto07:23
*** RP <RP!> has quit IRC07:25
*** RP <RP!> has joined #yocto07:25
*** uvan <uvan!~uvan@> has quit IRC07:25
*** [1]uvan is now known as uvan07:26
*** roric <roric!> has quit IRC07:26
*** roric <roric!> has joined #yocto07:26
zibriseebs: is it yocto compatible? ;)07:27
lpappseebs: sweet07:28
*** slaine <slaine!~slaine@> has quit IRC07:30
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC07:34
*** rogerzhou <rogerzhou!~rogerzhou@> has joined #yocto07:44
*** eren <eren!~eren@unaffiliated/eren> has quit IRC07:47
*** mshakeel <mshakeel!~mshakeel@> has quit IRC07:52
*** sameo <sameo!samuel@nat/intel/x-hsqshcgoblnssvzx> has joined #yocto07:53
*** mckoan|away is now known as mckoan07:55
mckoangood morning07:55
*** slaine <slaine!~slaine@> has joined #yocto07:55
*** mshakeel <mshakeel!~mshakeel@> has joined #yocto07:55
*** bluelightning <bluelightning!~paul@> has joined #yocto08:06
*** bluelightning <bluelightning!~paul@> has quit IRC08:06
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto08:06
rburtonlpapp: "dora"08:09
lpapprburton: thanks.08:09
rburtonit was announced in the tech call minutes last tuesday, sent to yocto@08:09
*** nrossi <nrossi!~nrossi@> has joined #yocto08:10
rburtonthose minutes are always worth a read08:10
bluelightningmorning all08:10
lpappbluelightning: hi08:10
*** mbelisko <mbelisko!> has joined #yocto08:11
lpappit is a(n unwrittne) rule to always start with 'd'?08:11
rburtonthat's just the pattern of the current naming scheme08:12
lpappso yes. :)08:12
*** padge_ <padge_!> has joined #yocto08:12
rburtonpoints if you can identify the naming schemes08:14
B4gderwell, now with so many names it gets easier to google for them08:14
rburtoni suspect the final addition makes it a lot easier to google08:15
rburtonpreviously you had to have a hunch and guide google with other keywords08:15
lpappby the way, that is lacking the dora cells at the top.08:16
lpappCode name and poky version.08:16
rburtonso it was08:16
rburtonunwritten rule: if you identify the current scheme, don't announce it publically.08:17
_alex_kag_hello! can anybody say about mfw_isink? (imx6)  fakesink take a lot of processor time, is it possiple to get frame from isink?08:17
lpappis there a channel for opkg questions?08:18
lpappor we can reach the maintainer only via email?08:18
*** JimBaxter <JimBaxter!> has joined #yocto08:25
*** lpapp <lpapp!~lpapp@kde/lpapp> has quit IRC08:27
*** honschu_ <honschu_!~honschu@shackspace/j4fun> has joined #yocto08:32
*** Net147 <Net147!> has quit IRC08:32
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has joined #yocto08:32
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto08:33
*** honschu <honschu!~honschu@shackspace/j4fun> has quit IRC08:33
erenmorning all08:34
bluelightninghi eren08:35
erenporky would be a good name canditate for a build bot08:38
erenguys at axis named it so, which was interesting. I don't know if it was a typo or not08:40
*** Anusko <Anusko!~anusko@> has quit IRC08:42
*** Anusko <Anusko!~anusko@> has joined #yocto08:43
zibrieren: it wasn't :)08:47
zibria manager accidentaly said "porky" in a meeting, and the name stuck for our migration project :)08:48
zibrieren: sorry about the mails btw08:48
B4gderhey, don't ruin a good story with facts! B)08:48
rburtonzibri: i like that story08:49
*** belen <belen!~Adium@> has joined #yocto08:50
erenzibri: ah, don't worry, mails are not problem :)08:50
erenzibri: if it is not confidential, what are you using currently for building images?08:50
zibrieren: hum, i didn't write our image bbclass, but it's ported from our old system. not exactly sure what you want to know :)09:02
*** swex__ <swex__!~swex@> has quit IRC09:02
*** swex <swex!~swex@> has joined #yocto09:02
erenzibri: ah, someone just wrote it then09:03
erenI always wonder why embdded system companies do not usually think of switching to OE09:04
erenhere we have a company producing software for routers, they sell quite well but their image is, pardon me, crap09:04
ereni have to reboot the machine once in a week09:05
erenI learned that they are using some hackery for building images for their boards. I asked why they are not switching to more elegant solutions, they said "it works"09:05
*** elbc_ <elbc_!2e12602e@gateway/web/freenode/ip.> has joined #yocto09:06
*** mitz <mitz!> has quit IRC09:16
*** mitz <mitz!> has joined #yocto09:17
elbc_hi all !09:19
elbc_I come to you because I would like to build a poky image I've already build before, this image contains wayland and X11 but I would like to re-build it without X11, does someone know how is that possible ?09:19
elbc_thank you09:19
rburtonelbc_: remove x11 from your DISTRO_FEATURES09:21
rburtonthen you'll be free of any traces of X1109:21
rburton(with x11 distro feature enabled dbus will depend on libx11, which is why you can still get pieces of X on a wayland image)09:22
elbc_I'm a beginner with yocto but actually i didn't found any trace of X11 in my conf file09:22
elbc_thank you for your ansmwer by the way09:22
bluelightningeren: well, there's definitely some ramp-up time... it's after that that people see the value of the system09:23
erenbluelightning: yeah, learning curve is a bit high but after that it's ok09:24
erenat least, it is maintainable09:24
elbc_when the image is built, libX11 is present because I think some features need it. As I said there is no trace of "X11" in my DISTRO_FEATURES, but maybe there is a command to disable or not allow libX1109:25
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto09:26
rburtonelbc_: your distro features must have x11, as otherwise libx11 will refuse to build09:26
rburtonelbc_: (the default has x11)09:26
elbc_ok I'll take a look again. thank you !09:27
rburtonif you're using poky from git master, you can use the lovely new _remove operator to edit DISTRO_FEATURES09:29
rburtonotherwise you'll need to set it09:29
BCMMif i don't like one line of a recipe's do_install(), for example, is the correct course of action to replace the entire do_install() in my bbappend?09:30
rburtonBCMM: yes09:31
BCMMcan i ask some advice about submitted changes upstream? i've made a few modifications to the mpd recipe which might be of general interest09:32
elbc_ok I'll try to use it ! thanks a lot for your help09:32
rburtonBCMM: each layer has a readme with any rules, like where to send the patches.09:32
BCMMrburton: for meta-multimedia, it's a mailing list, it's just that somebody posted a patch that does some of the same things as what i did at pretty much exactly the same time, but his has a bug09:33
BCMMand i'm rather unsure of the etiquette - should i post a patch to be applied after his patch, or a working version of his patch, or what?09:33
rburtonBCMM: if that broken patch hasn't been applied, reply on the list and send a revised version09:34
BCMMan, in general, are people interested in patches that optionally remove features?09:34
BCMMrburton: thanks09:34
rburtonBCMM: optionally trimming stuff out is fine, best practise is to use PACKAGECONFIG if it works for that package09:34
BCMMrburton: that's what i've done, thanks09:35
BCMMjust wanted to make sure i wasn't totally misunderstanding stuff before posting09:35
BCMMnow i just have to work out how to make git generate patches for me, cause that's the rules for that layer...09:35
BCMM(for some reason, pulseaudio was compulsory in mpd)09:35
rburtonif you configure git's email sending, you can use git send-email09:35
BCMMand dbus in wpa_supplicant09:35
BCMMrburton: i've also never modified somebody else's git repo before09:36
BCMMi've used a local one, and pulled other ones (obviously)09:36
BCMMdo i just edit the recipe in the layer, and then git-send-email works out what i've done?09:37
rburtonit sends the commits as patches09:37
rburtonso you review your branch and ensure that you've logical changes with clear commit messages09:37
rburtoni.e. no "add foo", "fix typo", "argh another typo" commits09:37
BCMMah right, so i make a git branch, commit changes to it, then have git generate the patches from that?09:38
BCMMthanks, i'll go and read git docs and make a brance09:39
erenBCMM: that documentation would help:
rburtonmy personal workflow is a "feature" branch per logical set of changes, then i daily rebase all my branches and get to see what's been merged and what is outstanding09:39
BCMMrburton: what do you mean by "rebase" in this context?09:39
BCMMeren: thanks!09:39
*** awafaa <awafaa!uid716@gateway/web/> has quit IRC09:39
erenah, rebasing, I haven't done that either09:39
rburtonBCMM: git-rebase09:40
erenI usually create a branch for changes, generate patches from that branch09:40
erenthen I remove that branch09:40
erenif the patches have been applied, of course09:40
rburtoneren: my "mergeotron" script does a git fetch, rebase's all branches against origin/master, and tells me if any branches are now the same as master (i.e. have been merged), so my other script can prune them from local and remote repos09:41
BCMMso... rebase is for if your branch could basically be considered a relatively small set of patches to the master, and rebase basically applies said patches to the latest master?09:41
rburtonBCMM: basically09:41
rburtonif you google for git workflow you'll find plenty of example workflows09:42
BCMMso in terms of actually making my images, i could have a branch of meta-multimedia in my bblayers.conf, and make changes i want to send upstream to that branch, and changes that only make sense for my project in bbappends in a seperate layer?09:42
rburtonBCMM: that's pretty sensible for the long-term09:44
BCMMrburton: well, it's a pretty small project. thus far, i upstreamable changes for wpa_supplicant and mpd09:45
BCMMbut i want to do things "cleanly" where i can09:45
rburtonBCMM: good, make it easier for everyone :)09:46
*** boz_v1 <boz_v1!> has quit IRC09:48
*** Anusko <Anusko!~anusko@> has quit IRC09:49
*** Anusko <Anusko!~anusko@> has joined #yocto09:50
*** boz_v1 <boz_v1!> has joined #yocto09:50
elbc_rburton: reading again what you have written, to be sure to understand, are you saying there is no way to disable libx11 (I want to build an image using wayland/weston)10:07
elbc_thanks again10:07
rburtonelbc_: removing x11 from your DISTRO_FEATURES will mean you have absolutely zero X in your builds10:08
elbc_yes that'ts what I want10:08
*** awafaa <awafaa!uid716@gateway/web/> has joined #yocto10:08
rburtonelbc_: and if anything doesn't respect that choice and tries to build something, libx11 checks the DISTRO_FEATURES and will refuse to build10:08
elbc_rburton: ok, so there is no way to build an image entirely based on wayland ?10:09
rburtonsure there is, just remove x11 from distro features10:10
rburtoni'm saying that the system will do exactly what you want10:10
rburtonremove x11 from distro features and you'll have no x11 in your distro10:10
elbc_rburton: ok thank you very much for your patience and your help10:11
elbc_DISTRO_FEATURES_remove = "x11 x11-common xorg-xserver" ?10:11
rburtonelbc_: are you using poky from git master?10:12
rburtoncool, in that case close10:12
rburtonDISTRO_FEATURES != packages10:12
rburtonso just "x11"10:12
elbc_ok ! thanks !10:13
*** mihai <mihai!~mihai@> has quit IRC10:14
*** OlivierG is now known as OlivierG_10:15
*** mihai <mihai!~mihai@> has joined #yocto10:18
*** uvan <uvan!~uvan@> has quit IRC10:23
*** ant_work <ant_work!> has quit IRC10:24
BCMMwhere can i find a list of vars for paths? i mean, like ${bindir}10:33
bluelightningBCMM: best reference for those is meta/conf/bitbake.conf, where their default values are defined10:36
BCMMbluelightning: thanks10:36
*** mankku <mankku!> has quit IRC10:42
*** boz_v1 <boz_v1!> has quit IRC10:42
*** Krz <Krz!c0c6972b@gateway/web/freenode/ip.> has joined #yocto11:02
*** mulhern <mulhern!> has joined #yocto11:05
KrzHi guys, in machine/my.conf originally used: SERIAL_CONSOLE = "" SERIAL_CONSOLES = "115200;ttyS0 115200;ttyS1"11:05
Krznow switching to only one COM port11:05
Krzis the logic as simple as assigning it to SERIAL_CONSOLE and leaving SERIAL_CONSOLES = "" ?11:06
*** joeythesaint <joeythesaint!> has joined #yocto11:09
*** walters <walters!> has joined #yocto11:11
bluelightningKrz: for dylan, yes; note that the two variables use different syntaxes though11:19
Krzso I'm gonna do exactly: SERIAL_CONSOLE = "115200 ttyS1" SERIAL_CONSOLES = ""11:19
Krzfor dylan11:19
*** walters <walters!> has quit IRC11:20
bluelightningKrz: right, that would be correct assuming ttyS1 is the device you wish to enable11:20
Krzbluelightning: thanks very much!11:20
*** rogerzhou <rogerzhou!~rogerzhou@> has quit IRC11:36
Crofton|workbluelightning, it sounds like cf0... made a working sdk after installing F1911:38
Crofton|workwe may have some problem with Ubuntu something11:38
*** jkridner <jkridner!> has joined #yocto11:44
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto11:44
elbc_rburton: hello again ! I've tried this : DISTRO_FEATURES != "x11" and I had the following error : ParseError: ParseError at /yocto/poky/thinkpad/conf/local.conf:251: unparsed line: 'DISTRO_FEATURES != "x11"'12:12
elbc_do you know why ?12:12
rburtonoh , i meant that the DISTRO_FEATURES line isn;t a set of packages12:12
rburtonso DISTRO_FEATURES_remove = "x11"12:12
elbc_ok thanks I will try this12:13
elbc_rburton: beginner question : if it builds correctly, how can I check easily that this line has worked ?12:14
rburtonelbc_: the work directory for the image will let you browse the rootfs that's been created, and see a list of files12:15
elbc_ok thanks I'll check this list !12:16
bluelightningCrofton|work: FWIW I run ubuntu here, though I haven't made a habit of using the Qt toolchain on this machine12:24
bluelightningCrofton|work: but noted, thanks12:25
Crofton|workdo you use any sdk's?12:25
*** Anusko <Anusko!~anusko@> has quit IRC12:25
*** Anusko <Anusko!~anusko@> has joined #yocto12:26
*** scot_ <scot_!~scot@> has joined #yocto12:26
bluelightningCrofton|work: I use buildtools-tarball every day on my build machine which is basically an SDK; I've installed the meta-toolchain SDKs a number of times recently to check basic functionality12:31
Crofton|workI''l try and get some details about the issue12:32
Crofton|workI'm an ubuntu avoider so not much help :)12:32
*** panda84kde <panda84kde!> has joined #yocto12:32
*** cfo215 <cfo215!> has joined #yocto12:33
*** mankku <mankku!> has joined #yocto12:34
*** mulhern <mulhern!> has quit IRC12:35
*** mulhern <mulhern!> has joined #yocto12:38
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC12:46
*** amarsman <amarsman!> has quit IRC12:49
KrzI need to add one entry to inittab. I think there is some magic API to do that in Yocto way, anybody aware?12:52
bluelightningKrz: I don't think there's any magic for that, I think you'd just bbappend sysvinit-inittab (see meta/recipes-core/sysvinit/
Krzbluelightning: was looking at this recipe right now. Yeah, it seems I have to do bbappend for that. Does do_install_append in my bbappend sound good?12:55
bluelightningKrz: that would work yes12:55
Krzbluelightning: nice, cheers12:56
*** padge_ <padge_!> has quit IRC13:04
*** elmir <elmir!> has joined #yocto13:07
*** Daemon404 <Daemon404!~who_knows@pdpc/supporter/student/Daemon404> has quit IRC13:07
*** Daemon404 <Daemon404!> has joined #yocto13:08
*** zecke <zecke!> has quit IRC13:11
*** cfo215 <cfo215!> has quit IRC13:13
*** zecke <zecke!> has joined #yocto13:13
*** walters <walters!walters@nat/redhat/x-mrzjxurqimnlaqma> has joined #yocto13:17
*** behanw_ is now known as behanw13:35
behanwmranostay, How's it going?13:35
Krzwhat's the codename for 1.5 release?13:45
rburtonKrz: dora13:46
Krzwow, that sounds non-english13:46
*** Krz is now known as Guest9692913:50
*** davest <davest!~Adium@> has joined #yocto13:52
bluelightningKrz: well, technically "dylan" is a welsh name so that's also non-English ;)13:53
*** shoragan <shoragan!~jlu@debian/developer/shoragan> has quit IRC13:53
*** jkridner <jkridner!> has joined #yocto13:53
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto13:53
*** shoragan <shoragan!~jlu@2001:6f8:1178:2:219:99ff:fe56:8d7> has joined #yocto13:54
*** shoragan <shoragan!~jlu@debian/developer/shoragan> has joined #yocto13:54
*** mbelisko <mbelisko!> has quit IRC14:02
*** Daemon404 <Daemon404!> has quit IRC14:03
*** Daemon404 <Daemon404!~who_knows@pdpc/supporter/student/Daemon404> has joined #yocto14:03
*** B4gder <B4gder!> has quit IRC14:04
*** quatre <quatre!c0926547@gateway/web/freenode/ip.> has joined #yocto14:06
*** silviof <silviof!~silviof@unaffiliated/silviof> has quit IRC14:07
*** _alex_kag_ <_alex_kag_!~alex_kag@> has quit IRC14:09
*** Zagor <Zagor!~bjst@rockbox/developer/Zagor> has quit IRC14:10
quatreI've a question about the package_rpm. There is a recipe I am using that is a pre-compiled program with a few libraries. The rpm for the pre-compiled program mentions that it provides all of the libraries it contains. I want to avoid that. Is there a way to prevent this, such that the rpm will only provide the package name, and not any of the libraries it contains?14:10
*** silviof <silviof!~silviof@unaffiliated/silviof> has joined #yocto14:12
Garibaldi|workquatre: adjust the recipe to not include them?14:15
Garibaldi|workvia a .bbappend14:16
*** fp <fp!~Chaudhary@> has joined #yocto14:16
*** darknighte_znc is now known as darknighte14:16
rburtonGaribaldi|work: the depends are added when building the rpm itself14:16
rburtonquatre: not sure how you can avoid those...14:17
Garibaldi|workrburton: I thought that's what he wanted ... to have an external depend rather than the rpm including the lib14:17
*** fp <fp!~Chaudhary@> has quit IRC14:19
*** ka6sox is now known as zz_ka6sox14:19
quatreHere is the concrete example: I am using a recipe to bring in the oracle java jre. It has several libraries already compiled, including a jpeg library. I move the program and its libraries out of the standard path to avoid conflicts. There are two images being built, one that pulls in the jre, and one that pulls in libjpeg from another recipe.14:20
quatreThe way it works now, both images happen to pull in the jre. the first pulls it in because it provides the jre. the second pulls it in because it find that it provides libjpeg, but does not see the other rpm file first14:20
*** mckoan is now known as mckoan|away14:21
quatreI would like the jre rpm to only provide the name of the jre recipe, so that it is not unintentionally pulled in to the other image14:21
elbc_rburton:  Hi again, I think X11 has been removed correctly, my question is : is there a way to have no trace of libx11 (because it is still present) if I want some packages like pulseaudio and gtk3 ?14:21
quatreI tried setting 'EXCLUDE_FROM_SHLIBS = "1"', as in, but it did not do as I expected14:22
rburtonquatre: in that case you'll be pleased to know that (iirc) there's a patch on the list to not generate those deps if the libs are not in the default search paths14:22
rburtonelbc_: gtk3 and pulse will compile fine without x1114:22
quatrethat is great news. Do you happen to know where I can find that patch so I may try it out?14:23
mranostaywin 214:23
elbc_rburton: ok, so if after build I see traces of libx11 , i can affirm it is not a problem, can you confirm ? thanks14:24
rburtonquatre: might be relevant14:24
rburtonelbc_: if you've correctly removed the x11 distro feature you won't see any libx11.  as i've said, libx11 checks for the x11 distro feature and will only build if x11 is enabled.14:24
*** hollisb <hollisb!~hollisb@> has joined #yocto14:25
*** arky <arky!~arky@> has joined #yocto14:25
elbc_rburton: ok, I'll check, I've just put the DISTRO_FEATURES_remove = "x11". thanks again14:26
RPJaMa: Did you update your shlibs patches from the ones you posted?14:33
RPJaMa: I'm seeing a few small bugs in the ones I took from the list :/14:33
*** kbart <kbart!~KBart@> has quit IRC14:36
*** mulhern <mulhern!> has quit IRC14:41
*** dany <dany!> has quit IRC14:42
elbc_is the eglibc error : ERROR: Function failed: do_compile (log file is located at /yocto/poky/thinkpad/tmp/work/x86_64-poky-linux/eglibc/2.18-r0/temp/log.do_compile.3428 a known issue ?14:46
rburtonprobably not14:47
rburtonpastebin the log please14:47
elbc_here is the end of the log :14:51
elbc_ln -s /home/elebideau/yocto/poky/thinkpad/tmp/work/x86_64-poky-linux/eglibc/2.18-r0/build-x86_64-poky-linux/elf/ /home/elebideau/yocto/poky/thinkpad/tmp/sysroots/x86_64-linux/usr/libexec/x86_64-poky-linux.gcc-cross-initial/gcc/x86_64-poky-linux/4.8.1/ld:/home/elebideau/yocto/poky/thinkpad/tmp/work/x86_64-poky-linux/eglibc/2.18-r0/build-x86_64-poky-linux/ syntax error collect2: error: ld returned 1 e14:51
elbc_it didn't work14:52
rburtonpastebin the full log please :)14:52
*** dany <dany!> has joined #yocto14:53
*** sameo <sameo!samuel@nat/intel/x-hsqshcgoblnssvzx> has quit IRC14:58
*** gjohnson <gjohnson!4542f923@gateway/web/freenode/ip.> has joined #yocto15:00
*** andyross <andyross!> has joined #yocto15:03
elbc_rburton: try to do a pastebin on but have some problems, trying to do as fast as i can15:06
*** zeeblex <zeeblex!~apalalax@> has quit IRC15:07
*** eren <eren!~eren@unaffiliated/eren> has quit IRC15:09
*** arky <arky!~arky@> has quit IRC15:10
*** munch <munch!> has joined #yocto15:10
*** mulhern <mulhern!> has joined #yocto15:11
*** belen <belen!~Adium@> has quit IRC15:12
gjohnson Hello all, is there a way to create a native package based on the output of a target build?  This question is in reference to building qt.  I want to build qt for my arm target but I would like to then add the generated qmake to my host sysroot.15:13
elbc_rburton: log is too long cannot create a pastebin15:13
elbc_rburton: is there an other way to send you the log ?15:15
kergothtry a different pastebin, i'd say. there are plenty fo pastebin sites, i can't imagine they all have the same limitations15:17,, others15:17
elbc_kergoth: thanks I'll try15:17
kergothalternatively, if you have dropbox, share it that way, that's always an easy way to share a fiel15:17
kergothor mediafire or rapidshare or..15:17
kergothalways lots of options for such things15:17
*** arky <arky!~arky@> has joined #yocto15:23
elbc_rburton: I'll try to build all packages excepts eglibc and i'll post you the log of the build of eglibc after that if it is ok for you. thanks for your time15:31
rburtonelbc_: eglibc is pretty important...15:32
quatrerburton: still at a bit of a loss. I tried the patch, but the rpm will still list the offending libraries as being provided. I also see that by setting 'EXCLUDE_FROM_SHLIBS = "1"' in a recipe the entire step that the patch tries to help with can be skipped. Even doing that, when I query the generated rpm file:15:35
quatre$ rpm -qp $rpm_file_here --provides | grep libjpeg15:36
quatreso, the package_do_shlibs step is not the one causing the issue in my case.15:36
*** zz_ka6sox is now known as ka6sox15:39
*** zenlinux_ <zenlinux_!> has joined #yocto15:40
*** blitz00 <blitz00!~stefans@unaffiliated/blitz00> has quit IRC15:41
elbc_rburton: yes I know but that was for have just the log (short) I need15:44
*** elmi82 <elmi82!> has quit IRC15:44
elbc_rburton:  here is the log !
quatreHm, it seems that including 'SKIP_FILEDEPS = "1"' into the recipe instead appears to work.15:47
rburtonelbc_: that's... odd.  silly question but the disk isn't full?15:48
elbc_rburton: not at all15:48
RPquatre: This is an rpm feature enabled at the rpm level15:49
RPquatre: you probably need to move the files you don't want to a different directory or something15:50
RPquatre: or split the package into two15:50
elbc_rburton: I've to go thanks a lot for your help again, maybe see you tomorrow15:51
quatreall the files in the jre package I believe I need. The files in the jre package are installed to a location that is non-standard to avoid other programs from accidently loading with the jre's libraries.15:51
quatrethe issue is that I am using one workspace to build two images15:51
*** Jefro <Jefro!> has joined #yocto15:57
*** eballetbo <eballetbo!> has quit IRC16:03
*** mulhern <mulhern!> has quit IRC16:03
*** belen <belen!Adium@nat/intel/x-zfzikgpzpjjtxbjj> has joined #yocto16:05
*** mulhern <mulhern!> has joined #yocto16:05
JaMaRP: I'll compare them with my local copy a bit later and let you know, current version is HEAD~4 here
JaManow off to get some food16:10
*** darknighte is now known as darknighte_znc16:11
Guest96929there is a gdb recipe in poky16:14
Guest96929but I didn't find gdb-server16:14
Guest96929how do I build gdb-server?16:14
fraygdb-server usually comes out of the gdb recipe16:18
fraythe 'gdbserver' package (produced from the gdb recipe) is what you likely want16:19
*** mihai <mihai!~mihai@> has quit IRC16:20
*** mitz <mitz!> has quit IRC16:23
Daemon404so it's been a while since i last checked16:23
Daemon404er.. shit wrong channel16:23
Daemon404carry on.16:23
Guest96929ERROR: Nothing PROVIDES 'gdbserver'16:24
Guest96929im using poky dylan 9.0.116:24
kergothhe just told you the recipe is gdb, not gdbserver16:24
*** mitz <mitz!> has joined #yocto16:25
Guest96929sorry, my bad16:25
Guest96929so I just build gdb and will have server and client, right?16:25
frayyou build gdb, and tell your image recipe to install the 'gdbserver' package16:27
Guest96929fray: thanks!16:27
*** mr_science <mr_science!> has joined #yocto16:33
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has joined #yocto16:33
*** _alex_kag_ <_alex_kag_!~alex_kag@> has joined #yocto16:35
*** ka6sox is now known as zz_ka6sox16:42
*** OSNinja <OSNinja!> has joined #yocto16:44
*** amarsman <amarsman!> has joined #yocto16:50
*** quatre <quatre!c0926547@gateway/web/freenode/ip.> has quit IRC16:55
*** seebs <seebs!> has quit IRC16:55
RPJaMa: ok, I have some fixes then16:55
*** seebs <seebs!> has joined #yocto16:58
*** slaine <slaine!~slaine@> has quit IRC16:59
RPJaMa: specifically17:00
RPJaMa: I'm now worrying this will cause autogenerated shlibs dependencies for be removed from things though. We probably need to have some kind of RPATH handling to make this all work properly :/17:01
* RP is out of time right now but will try and write up a full repsonse/summary17:01
JaMalooks good, my version in jansa/test branch has one more change:17:06
JaMa-    def read_shlib_providers:17:06
JaMa+    def read_shlib_providers():17:06
*** arky <arky!~arky@> has quit IRC17:09
*** Anusko <Anusko!~anusko@> has quit IRC17:21
*** Anusko <Anusko!~anusko@> has joined #yocto17:22
*** belen <belen!Adium@nat/intel/x-zfzikgpzpjjtxbjj> has quit IRC17:23
*** belen <belen!~Adium@> has joined #yocto17:24
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto17:25
*** zenlinux_ <zenlinux_!> has quit IRC17:29
*** panda84kde <panda84kde!> has quit IRC17:30
*** mihai <mihai!~mihai@> has joined #yocto17:35
*** mulhern <mulhern!> has quit IRC17:36
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has quit IRC17:50
*** zecke <zecke!> has quit IRC17:52
*** tinti <tinti!~tinti@pdpc/supporter/student/tinti> has joined #yocto18:04
*** belen <belen!~Adium@> has quit IRC18:13
seebsSo, I've got this one nagging loose end with the pseudo bug pabigot found, which is: How did this ever appear to work?18:14
bluelightningI hate when that happens :(18:15
seebsAnswer: Back in October of 2011, fray renamed the undocumented/internal PSEUDO_RELOADED hack to PSEUDO_UNLOAD.18:15
seebsIn passing, he added a helpful check in the pseudo client: if PSEUDO_UNLOAD is in the environment, pseudo *also* disables itself.18:15
seebsSo in any case where you tried to do something like "PSEUDO_UNLOAD=1 <cmd>", the command would run as though it didn't have pseudo in its environment, even if it was actually loaded.18:16
seebsOf course, that doesn't entirely resolve the mystery.18:16
seebsBecause I still don't know why, on the machines not exhibiting this behavior, we don't get any diagnostics about being unable to load
seebsAh. Hah.18:19
seebspseudo dash -c "PSEUDO_UNLOAD=1 id" => trips t18:19
seebsthe test I had for this18:19
seebspseudo bash -c "PSEUDO_UNLOAD=1 id" => does not18:19
frayall of the testing done at the time used /usr/bin/env18:20
seebsAnd the reason we rarely-if-ever saw it inside WR is that our old build system did not have enough hooks to protect individual apps from bashisms, so we have a habit of changing /bin/sh to point to bash on systems that have to build the old product.18:20
seebsAnd if you had a program which cleaned up its environment, then called something else, and you ran it with PSEUDO_UNLOAD=1 but without the bug fix and you were using dash, it could end up with LD_PRELOAD set and LD_LIBRARY_PATH not set, or something similar.18:21
*** Jefro <Jefro!> has quit IRC18:22
seebsOh, like, say, if it tried to change LD_LIBRARY_PATH. I bet I could now make something that triggers this, but in any event, I am now content to assert that this really IS the fundamental problem, and that there are real reasons for it to appear only sporadically.18:22
bluelightningso is pabigot's fix the correct one then?18:23
bluelightning(for the confused)18:24
seebsWell, "the" correct one might be a bit strong, but I stand by my "this looks good, let's use that until I have time to spend staring at this and thinking more about edge cases".18:24
*** Jefro <Jefro!> has joined #yocto18:24
bluelightningok, fair enough18:24
rburtonseebs: i mysteriously got the problem again today and confirm that his patch fixed it18:26
seebsrburton, what's /bin/sh on your machine?18:27
seebsHuh. Well, then I'm still a little confused. But I think I'm willing to accept that.18:28
rburtonsame here :)18:28
seebsFWIW, a quick check for the behavior:18:29
seebspseudo bash -c "PSEUDO_UNLOAD=1 env" | grep LD_PRE18:29
*** Guest96929 <Guest96929!c0c6972b@gateway/web/freenode/ip.> has quit IRC18:30
seebsAnd then you can try with other shells, and observe the behavior changing.18:30
seebsThinking more about this, I note a fundamental flaw in pseudo's environment setup, which is that the UNLOAD behavior just tries to remove LD_PRELOAD. So I think I am going to change this so that, if UNLOAD is set, we don't do the environment setup, we just remove LD_PRELOAD. As-is, pseudo will clutter an environment with various PSEUDO_FOO values even if it's being unloaded.18:41
*** tor <tor!> has joined #yocto18:46
*** florian <florian!~fuchs@Maemo/community/contributor/florian> has quit IRC18:54
*** smartin_ <smartin_!> has joined #yocto18:54
*** JimBaxter <JimBaxter!> has quit IRC18:57
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC18:59
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has quit IRC19:12
*** c00kiemon5ter <c00kiemon5ter!~c00kiemon@foss-aueb/coder/c00kiemon5ter> has joined #yocto19:20
*** smartin__ <smartin__!> has joined #yocto19:29
*** smartin <smartin!> has quit IRC19:30
*** drasko <drasko!> has joined #yocto19:36
draskohi all. My external kernel module includes local .h files. How to tell Yocto to find these files19:37
draskoI tried EXTRA_CFLAGS=-I$(PWD), does not work19:37
*** mario-goulart <mario-goulart!> has quit IRC19:39
*** mario-goulart <mario-goulart!> has joined #yocto19:43
mr_sciencehow about CFLAGS_append = foo19:45
*** brm <brm!da653619@gateway/web/freenode/ip.> has joined #yocto19:57
*** tor <tor!> has quit IRC20:09
sgw_JaMa: still around?  Wanted to ask you about bug #479520:09
yoctiBug normal, Medium, 1.5, saul.wold, NEEDINFO , PSEUDO_LOCALSTATEDIR _sometimes_ points to WORKDIR with wrong TARGET_OS20:09
brmHi Guys, Anyone know how to do Yocto app development on Windoze?20:10
JaMasgw_: yes, I've seen NEEDINFO in the morning but haven't had time to reproduce it and add more details20:13
JaMasgw_: fwiw it's not fatal in any way (at least I don't think so) so it's OK to move it to 1.620:13
sgw_JaMa: got it was one of those, that I had hanging around and thought I would look at it.  I am guessing it's oe-core not poky based and maybe qemuarm for the machine?20:18
*** _alex_kag_ <_alex_kag_!~alex_kag@> has quit IRC20:20
*** mulhern <mulhern!> has joined #yocto20:23
sakomanIs there a way to have an image recipe DEPEND on another image build?  A client would like to include the tarball of a small recovery image in the main image build.20:32
sakomanDoing the obvious approach, adding a DEPENDS in the image recipe, doesn't trigger a build of the recovery image20:33
ndecsakoman: i have done something similar.20:34
sgw_sakoman: I think that's doable, since we do it form initramfs I think20:34
ndeci have 2 images. 1 being 'included' in the other one.20:35
ndecto make a chroot in my case, but it's similar.20:35
sgw_sakoman: you might need to create a depends on the image:do_rootfs, take a look at imiage-live.bbclass and INITRD_IMAGE20:36
ndecsakoman: in the 'top level' image, i do this:20:36
ndec do_rootfs[depends] += "my-other-image:do_rootfs"20:36
sgw_ndec got it also20:37
ndecyep ;-)20:37
*** brm <brm!da653619@gateway/web/freenode/ip.> has quit IRC20:37
ndecthen in your top level image, you can assume that your other image is in  ${DEPLOY_DIR_IMAGE}/20:37
*** amarsman <amarsman!> has quit IRC20:43
*** smartin_ <smartin_!> has quit IRC20:45
*** W1N9Zr0 <W1N9Zr0!> has quit IRC20:45
*** mihai <mihai!~mihai@> has quit IRC20:47
sakomanndec: thanks, I'll try that20:52
JaMasgw_: yes different DISTRO and I've seen it with multiple different MACHINEs20:54
*** W1N9Zr0 <W1N9Zr0!> has joined #yocto20:56
sgw_jama, ok I am building an oe-core/qemuarm, I know you said the reproduce was hard, you do know that the pseudo directory is added back in again to deal with setscene20:59
JaMayes, but than I've built the same target twice once completely from sstate-cache and once from scratch and the names of pseudo dirs weren't consistenly all incorrect or correct21:04
kergothheh, bitbake still has a bug where it doesn't re-create the mirror tarballs when the repositories are updated21:05
kergothugh, i don't think BB_SRCREV_POLICY = "cache" is working properly anymore21:09
* kergoth digs21:09
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto21:26
*** andyross <andyross!> has quit IRC21:41
otaviosgw_: how that u-boot seems ok on beagle; I sent a upgrade patch for it21:42
otaviosgw_: *now that ...21:42
otaviobluelightning: sent an e-mail with a possible backport for dylan21:46
*** OSNinja <OSNinja!> has quit IRC21:49
sgw_otavio: yes, I saw that thanks.21:51
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC21:52
sgw_tomz2: thoughts on moving lttng to git recipes instead of tarballs? (re otavio email from this morning)21:52
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto21:52
tomz2sgw_: sounds like a good idea to me21:53
tomz2tomz2: of course it means going through the whole potential renaming issue again, maybe..21:54
gjohnsonHow do I add extra files so that they get populated in the sysroot?22:00
*** walters <walters!walters@nat/redhat/x-mrzjxurqimnlaqma> has quit IRC22:01
bluelightninggjohnson: install them within your recipe's do_install into the appropriate path under ${D} and they will be staged into the sysroot automatically22:02
-YoctoAutoBuilder- build #281 of nightly-non-gpl3 is complete: Failure [failed Building Images] Build details are at
otaviokergoth: ouch; if you fix the cache policy please cc me in the patch so I can test it22:03
*** gjohnson <gjohnson!4542f923@gateway/web/freenode/ip.> has quit IRC22:05
*** Garibaldi|work <Garibaldi|work!~andydalt@nat/cisco/x-bpiisfepgwfuilco> has quit IRC22:05
-YoctoAutoBuilder- build #92 of buildtools is complete: Failure [failed Building Images Publishing Layer Tarballs Publishing Artifacts] Build details are at
BCMMi don't quite understand the README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY  in my /tmp/deploy/images dir - do i have to do something special in order to remove old images?22:07
BCMMit seems to collect an extra image for every build i run22:07
otavioBCMM: the kernel file, in case you remove it and kernel does not change, it won't be re-deployed.22:07
-YoctoAutoBuilder- build #293 of nightly-intel-gpl is complete: Failure [failed Building Images Building Images_1] Build details are at
otavioBCMM: same for bootloaders22:08
*** sameo <sameo!~samuel@> has joined #yocto22:08
sgw_BCMM: if you know that you are doing you can remove images, problem has been people will remove the kernel or other files and then can not rebuild, what otavio said ;-)22:08
otavioBCMM: so you must to be careful22:08
BCMMbut you can always recover by -c clean'ing the appropriate recipe?22:08
otaviosgw_: ;-)22:08
otavioBCMM: well, but it takes time and in case you use package feeds it is not wanted22:09
otavioBCMM: you can -b deploy -f22:09
BCMMi don;t know aht "package feeds" means...22:09
-YoctoAutoBuilder- build #136 of minnow is complete: Failure [failed Building Images Publishing Layer Tarballs Publishing Layer Tarballs_1 Publishing Layer Tarballs_2 Publishing Layer Tarballs_3 Publishing Artifacts] Build details are at
otavioBCMM: I think it'll do the trick22:09
otavioBCMM: look at Yocto docs about package feeds22:10
kergothotavio: not sure exactly what's going on, but i do know we're having trouble shipping with SRCREV=AUTOREV, which was a problem we'd already worked around in the past by pre-supplying the BB_URI_HEADREVS map.. will come up with more detail and open a bug if necessary tomorrow22:10
* sgw_ the YoctoAutoBuilder is going to make a lot of noise shortly, bad build on my part!22:10
otaviosgw_: you bad!22:10
otaviosgw_: please if possible add my u-boot in mut for testing as well22:10
otaviosgw_: did you see the distro_features_check additions?22:11
-YoctoAutoBuilder- build #292 of nightly-mips-lsb is complete: Failure [failed Building Images Building Images_1 Publishing Layer Tarballs Publishing Layer Tarballs_1 Publishing Artifacts] Build details are at
* otavio went off; bbl22:12
-YoctoAutoBuilder- build #121 of minnow-lsb is complete: Failure [failed Building Images Publishing Layer Tarballs Publishing Layer Tarballs_1 Publishing Layer Tarballs_2 Publishing Layer Tarballs_3 Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #248 of nightly-fsl-ppc-lsb is complete: Failure [failed Building Images Publishing Layer Tarballs Publishing Layer Tarballs_1 Publishing Layer Tarballs_2 Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #278 of nightly-world is complete: Failure [failed Building Images Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #278 of nightly-x86-64-lsb is complete: Failure [failed Building Images Building Images_1 Publishing Layer Tarballs Publishing Layer Tarballs_1 Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #284 of poky-tiny is complete: Failure [failed Building Images Publishing Layer Tarballs Publishing Layer Tarballs_1 Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #282 of build-appliance is complete: Failure [failed Building Images Building Images_1 Publishing Layer Tarballs Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #257 of nightly-oecore is complete: Failure [failed Building Images Running Sanity Tests Building Toolchain Images Building Toolchain Images_1] Build details are at
-YoctoAutoBuilder- build #284 of nightly-x86-lsb is complete: Failure [failed Building Images Building Images_1 Publishing Layer Tarballs Publishing Layer Tarballs_1 Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #276 of nightly-x86-64 is complete: Failure [failed Building Images Running Sanity Tests Building Images_1 Building Toolchain Images Building Toolchain Images_1 Publishing Layer Tarballs Publishing Layer Tarballs_1 Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #54 of eclipse-plugin-kepler is complete: Failure [failed Publishing Layer Tarballs Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #290 of nightly-x32 is complete: Failure [failed Publishing Layer Tarballs Publishing Layer Tarballs_1 Building Images Running Sanity Tests Running Sanity Tests_1] Build details are at
-YoctoAutoBuilder- build #279 of nightly-ppc is complete: Failure [failed Building Images Running Sanity Tests Building Images_1 Building Toolchain Images Building Toolchain Images_1 Publishing Layer Tarballs Publishing Layer Tarballs_1 Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #277 of nightly-arm is complete: Failure [failed Building Images Running Sanity Tests Building Images_1 Building Toolchain Images Building Toolchain Images_1 Publishing Layer Tarballs Publishing Layer Tarballs_1 Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #282 of nightly-x86 is complete: Failure [failed Building Images Running Sanity Tests Building Images_1 Building Toolchain Images Building Toolchain Images_1 Publishing Layer Tarballs Publishing Layer Tarballs_1 Publishing Artifacts] Build details are at
-YoctoAutoBuilder- build #282 of nightly-mips is complete: Exception [exception Building Images] Build details are at
-YoctoAutoBuilder- build #257 of nightly-fsl-arm is complete: Exception [exception Building Images] Build details are at
-YoctoAutoBuilder- build #53 of eclipse-plugin-juno is complete: Exception [exception interrupted] Build details are at
-YoctoAutoBuilder- build #279 of nightly-multilib is complete: Exception [exception Building Images] Build details are at
-YoctoAutoBuilder- build #251 of nightly-fsl-ppc is complete: Exception [exception Building Images] Build details are at
-YoctoAutoBuilder- build #137 of minnow is complete: Exception [exception interrupted] Build details are at
-YoctoAutoBuilder- build #279 of nightly-ppc-lsb is complete: Exception [exception interrupted] Build details are at
*** YoctoAutoBuilder <YoctoAutoBuilder!> has quit IRC22:44
*** YoctoAutoBuilder <YoctoAutoBuilder!> has joined #yocto22:44
mulhernSuppose I was running a perl script on qemuppc and it complained because it couldn't find the module File::Basename in its search paths. File::Basename has been part of Perl core since 5.14.2. What should be my cpurse of action?22:45
mulhernIt seems to be able to find File::Spec.22:45
mulhernHow can I find out what yocto Perl module actually supplies this module?22:52
mulhernThe answer is, you can noodle around in the Perl workdir looking for that file name.22:56
*** davest <davest!~Adium@> has quit IRC22:56
bluelightningmulhern: perl-module-file-basename I guess22:56
mulhernYup…it's the correct one.22:57
mulhernBut here's another question.22:57
mulhernIs the reason that File::Spec is on qemuppc even though it's not in RDEPENDS of my package pure luck? Because there's another module perl-module-file-spec that seems to contain File::Spec but it's not in my RDEPENDS.22:59
mulhernI agree that the naming is helpfully consistent. But I also believe that there are some uber- yocto perl modules that contain more than one actual Perl module.23:00
*** davest <davest!~Adium@> has joined #yocto23:00
bluelightningmulhern: right; I'm not sure what the logic has been in how those were grouped23:01
*** hno <hno!~hno@squid/developer/hno> has joined #yocto23:02
-YoctoAutoBuilder- build #55 of eclipse-plugin-kepler is complete: Success [build successful] Build details are at
*** seebs <seebs!> has quit IRC23:06
*** seebs <seebs!> has joined #yocto23:07
-YoctoAutoBuilder- build #294 of nightly-intel-gpl is complete: Success [build successful] Build details are at
*** seebs <seebs!> has quit IRC23:11
*** seebs <seebs!> has joined #yocto23:15
*** seebs <seebs!> has quit IRC23:19
*** davest <davest!~Adium@> has quit IRC23:31
*** seebs <seebs!> has joined #yocto23:33
*** eren <eren!~eren@unaffiliated/eren> has quit IRC23:33
*** munch <munch!> has quit IRC23:42
*** hollisb <hollisb!~hollisb@> has quit IRC23:47
*** mulhern <mulhern!> has quit IRC23:51
*** mr_science <mr_science!~sarnold@gentoo/developer/nerdboy> has quit IRC23:53
*** sameo <sameo!~samuel@> has quit IRC23:55
*** pidge <pidge!> has quit IRC23:57

Generated by 2.11.0 by Marius Gedminas - find it at!