*** seebs <seebs!~seebs@199.91.180.138> has joined #yocto | 00:26 | |
*** sjolley <sjolley!sjolley@nat/intel/x-aipeugouqkboqopt> has quit IRC | 00:32 | |
*** nitink <nitink!~nitink@134.134.137.75> has quit IRC | 00:59 | |
*** seebs <seebs!~seebs@199.91.180.138> has quit IRC | 01:07 | |
*** nitink <nitink!nitink@nat/intel/x-yrczvdkeecxdcyar> has joined #yocto | 01:15 | |
*** radhus <radhus!~radhus@sevh.radhuset.org> has quit IRC | 01:29 | |
*** jjardon_ <jjardon_!sid723@gateway/web/irccloud.com/x-zgggysrjhrpjhehf> has joined #yocto | 01:29 | |
*** demonimin_ <demonimin_!~demonimin@pro75-5-88-162-203-35.fbx.proxad.net> has joined #yocto | 01:29 | |
*** demonimin_ <demonimin_!~demonimin@unaffiliated/demonimin> has joined #yocto | 01:29 | |
*** kscherer_ <kscherer_!~kscherer@128.224.252.2> has joined #yocto | 01:30 | |
*** ipuustin_ <ipuustin_!~ipuustin@2002:591b:2160::1> has joined #yocto | 01:30 | |
*** nslu2-log_ <nslu2-log_!~nslu2-log@140.211.169.184> has joined #yocto | 01:30 | |
*** radhus <radhus!~radhus@sevh.radhuset.org> has joined #yocto | 01:31 | |
*** seebs <seebs!~seebs@home.seebs.net> has joined #yocto | 01:31 | |
*** kscherer <kscherer!~kscherer@128.224.252.2> has quit IRC | 01:32 | |
*** Ptishell <Ptishell!~surply_p@217.109.146.26> has quit IRC | 01:32 | |
*** hsychla__ <hsychla__!~hsychla@77-64-175-89.dynamic.primacom.net> has quit IRC | 01:32 | |
*** ancky <ancky!~ancky@2a01:4f8:d12:1d05::2> has quit IRC | 01:33 | |
*** demonimin <demonimin!~demonimin@unaffiliated/demonimin> has quit IRC | 01:33 | |
*** jjardon <jjardon!sid723@gateway/web/irccloud.com/x-bgfkqhfvwogkwzrm> has quit IRC | 01:33 | |
*** nslu2-log <nslu2-log!~nslu2-log@140.211.169.184> has quit IRC | 01:33 | |
*** ipuustin <ipuustin!~ipuustin@2002:591b:2160::1> has quit IRC | 01:33 | |
*** nslu2-log_ is now known as nslu2-log | 01:33 | |
*** jjardon_ is now known as jjardon | 01:33 | |
*** ancky <ancky!~ancky@2a01:4f8:d12:1d05::2> has joined #yocto | 01:33 | |
*** Ptishell <Ptishell!~surply_p@217.109.146.26> has joined #yocto | 01:35 | |
*** radhus <radhus!~radhus@sevh.radhuset.org> has quit IRC | 01:38 | |
*** surply_p <surply_p!~surply_p@217.109.146.26> has joined #yocto | 01:38 | |
*** Calchan_ <Calchan_!~calchan@smtp.gentoo.org> has joined #yocto | 01:41 | |
*** Calchan_ <Calchan_!~calchan@gentoo/developer/calchan> has joined #yocto | 01:41 | |
*** mago__ <mago__!~mago@c193-14-123-186.cust.tele2.se> has joined #yocto | 01:42 | |
*** Calchan <Calchan!~calchan@gentoo/developer/calchan> has quit IRC | 01:42 | |
*** mago_ <mago_!~mago@c193-14-123-186.cust.tele2.se> has quit IRC | 01:42 | |
*** jmpdelos <jmpdelos!~polk@97-121-178-67.clsp.qwest.net> has quit IRC | 01:42 | |
*** ecdhe <ecdhe!~ecdhe@173-22-126-166.client.mchsi.com> has quit IRC | 01:42 | |
*** cbzx <cbzx!~cbzx@CPE0015f275ebd6-CM00195edd810c.cpe.net.cable.rogers.com> has quit IRC | 01:42 | |
*** Ptishell <Ptishell!~surply_p@217.109.146.26> has quit IRC | 01:42 | |
*** k-s <k-s!~gustavo@enlightenment/developer/k-s> has quit IRC | 01:42 | |
*** smo <smo!canuck@smocean.eveny.ca> has quit IRC | 01:42 | |
*** radhus__ <radhus__!~radhus@sevh.radhuset.org> has joined #yocto | 01:42 | |
*** k-s[WORK] <k-s[WORK]!~gustavo@ec2-54-207-56-134.sa-east-1.compute.amazonaws.com> has joined #yocto | 01:42 | |
*** k-s[WORK] <k-s[WORK]!~gustavo@enlightenment/developer/k-s> has joined #yocto | 01:42 | |
*** radhus__ is now known as radhus | 01:42 | |
*** ecdhe <ecdhe!~ecdhe@173-22-126-166.client.mchsi.com> has joined #yocto | 01:44 | |
*** smo <smo!canuck@me.wantsmo.com> has joined #yocto | 01:46 | |
*** Calchan_ is now known as Calchan | 01:46 | |
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has quit IRC | 01:48 | |
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has joined #yocto | 01:50 | |
*** dlan <dlan!~dennis@gentoo/developer/dlan> has quit IRC | 01:53 | |
*** dlan <dlan!~dennis@gentoo/developer/dlan> has joined #yocto | 01:53 | |
*** jmpdelos <jmpdelos!~polk@97-121-178-67.clsp.qwest.net> has joined #yocto | 01:53 | |
*** sjolley <sjolley!sjolley@nat/intel/x-nklwghqciqvqornb> has joined #yocto | 01:53 | |
*** wgao <wgao!~wgao@106.120.101.38> has quit IRC | 02:16 | |
*** wgao <wgao!~wgao@106.120.101.38> has joined #yocto | 02:25 | |
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto | 02:25 | |
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC | 02:34 | |
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto | 02:34 | |
*** nitink <nitink!nitink@nat/intel/x-yrczvdkeecxdcyar> has left #yocto | 02:45 | |
*** orkim_ <orkim_!~orkim@unaffiliated/orkim> has quit IRC | 02:45 | |
*** nitink <nitink!~nitink@134.134.139.72> has joined #yocto | 02:49 | |
*** orkim <orkim!~orkim@unaffiliated/orkim> has joined #yocto | 03:18 | |
*** michael_e_brown <michael_e_brown!~michael_e@99-23-196-16.lightspeed.austtx.sbcglobal.net> has joined #yocto | 03:31 | |
*** surply_p <surply_p!~surply_p@217.109.146.26> has quit IRC | 03:44 | |
*** surply_p <surply_p!~surply_p@217.109.146.26> has joined #yocto | 03:45 | |
*** jkridner|work <jkridner|work!~jkridner@93-32-62-161.ip32.fastwebnet.it> has quit IRC | 04:07 | |
*** rjv <rjv!3df6bac6@gateway/web/freenode/ip.61.246.186.198> has quit IRC | 04:10 | |
*** Crofton|work <Crofton|work!~balister@pool-108-44-95-192.ronkva.east.verizon.net> has quit IRC | 04:20 | |
*** Crofton|work <Crofton|work!~balister@pool-71-171-35-135.ronkva.east.verizon.net> has joined #yocto | 04:33 | |
*** nitink <nitink!~nitink@134.134.139.72> has quit IRC | 04:35 | |
*** rjv16 <rjv16!3df6bac6@gateway/web/freenode/ip.61.246.186.198> has joined #yocto | 05:32 | |
rjv16 | Hi | 05:32 |
---|---|---|
*** bhav <bhav!3df6bac6@gateway/web/freenode/ip.61.246.186.198> has joined #yocto | 05:33 | |
bhav | Hi all | 05:33 |
*** rjv16 <rjv16!3df6bac6@gateway/web/freenode/ip.61.246.186.198> has quit IRC | 05:35 | |
*** nitink <nitink!~nitink@134.134.139.72> has joined #yocto | 05:36 | |
*** RP <RP!~richard@port-195-158-157-135.static.isionline-dialin.de> has quit IRC | 05:45 | |
bhav | I am getting some missing symbol error with GCC-4.4.2 which I have compiled using openembedded bitbake | 05:45 |
*** zecke <zecke!~ich@91.66.224.184> has joined #yocto | 05:46 | |
bhav | Please refer to http://pastebin.com/iBV29p1h link for more details | 05:46 |
*** TobSnyder <TobSnyder!~schneider@ip92341b76.dynamic.kabel-deutschland.de> has joined #yocto | 06:17 | |
*** nitink <nitink!~nitink@134.134.139.72> has quit IRC | 06:19 | |
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has quit IRC | 06:21 | |
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has joined #yocto | 06:24 | |
*** mago__ is now known as mago_ | 06:25 | |
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has quit IRC | 06:26 | |
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has joined #yocto | 06:27 | |
*** gvy <gvy!~mike@altlinux/developer/mike> has joined #yocto | 06:29 | |
*** RP <RP!~richard@62.156.150.201> has joined #yocto | 06:50 | |
*** belen <belen!~Adium@192.198.151.44> has joined #yocto | 06:52 | |
*** tasslehoff <tasslehoff!~Tasslehof@77.40.182.98> has joined #yocto | 06:57 | |
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-fguolauwwrgqriak> has joined #yocto | 07:00 | |
*** jbrianceau_away is now known as jbrianceau | 07:01 | |
*** eballetbo <eballetbo!~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net> has joined #yocto | 07:06 | |
*** belen <belen!~Adium@192.198.151.44> has quit IRC | 07:07 | |
*** rperier <rperier!~quassel@ubuntu/member/rperier> has quit IRC | 07:13 | |
*** rperier <rperier!~quassel@2001:41d0:52:100::44a> has joined #yocto | 07:14 | |
*** rperier <rperier!~quassel@ubuntu/member/rperier> has joined #yocto | 07:14 | |
*** RP <RP!~richard@62.156.150.201> has quit IRC | 07:20 | |
*** adelcast <adelcast!~adelcast@130.164.62.224> has quit IRC | 07:21 | |
*** bluelightning <bluelightning!~paul@83.217.123.106> has joined #yocto | 07:24 | |
*** bluelightning <bluelightning!~paul@83.217.123.106> has quit IRC | 07:24 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 07:24 | |
*** adelcast <adelcast!~adelcast@130.164.62.224> has joined #yocto | 07:35 | |
*** kbouhara <kbouhara!~kbouhara@hyperion.atermes.fr> has joined #yocto | 07:49 | |
*** surply_p is now known as Ptishell | 07:54 | |
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has quit IRC | 08:11 | |
*** FunkyPenguin <FunkyPenguin!~quassel@opensuse/member/FunkyPenguin> has joined #yocto | 08:13 | |
kbouhara | Hello all, Im getting the following issue when adding qt5 toolchain package group to my own image packagegroup: * satisfy_dependencies_for: Cannot satisfy the following dependencies for packagegroup-qemu-image: * qtwebkit-mkspecs * qtwebkit-qmlplugins * qtwebkit (= 5.3.2-r0) * | 08:16 |
kbouhara | does anyone faced the same issue ? | 08:16 |
bluelightning | morning all | 08:23 |
bluelightning | kbouhara: I haven't but it would be worth double-checking the README file for meta-qt5 to ensure you haven't missed any configuration | 08:23 |
*** belen <belen!~Adium@192.198.151.44> has joined #yocto | 08:28 | |
*** zecke <zecke!~ich@91.66.224.184> has quit IRC | 08:34 | |
*** ddom <ddom!~ddom@p4FFABDCF.dip0.t-ipconnect.de> has joined #yocto | 08:46 | |
*** belen <belen!~Adium@192.198.151.44> has quit IRC | 08:48 | |
*** jimBaxter <jimBaxter!~jbaxter@jimbax.plus.com> has joined #yocto | 08:50 | |
*** belen <belen!~Adium@192.198.151.44> has joined #yocto | 08:51 | |
*** falk0n <falk0n!~falk0n@89.154.11.73> has joined #yocto | 08:53 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 09:02 | |
*** tmpsantos <tmpsantos!~tmpsantos@192.198.151.43> has joined #yocto | 09:04 | |
*** bluelightning <bluelightning!~paul@83.217.123.106> has joined #yocto | 09:07 | |
*** bluelightning <bluelightning!~paul@83.217.123.106> has quit IRC | 09:07 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 09:07 | |
*** linu_ <linu_!ca004dc6@gateway/web/freenode/ip.202.0.77.198> has joined #yocto | 09:17 | |
*** ant_work <ant_work!~ant__@host54-128-static.10-188-b.business.telecomitalia.it> has joined #yocto | 09:20 | |
kbouhara | bluelightning: ok I'll do that thanks | 09:24 |
*** frsc <frsc!~frsc@host-89-242-129-124.as13285.net> has joined #yocto | 09:31 | |
*** lpapp <lpapp!~lpapp@kde/lpapp> has joined #yocto | 09:32 | |
lpapp | hi, I have never understood this dependency: gdbserver: unsatisfied recommendation for glibc-thread-db | 09:32 |
lpapp | it looks broken to me | 09:32 |
lpapp | ERROR: Nothing PROVIDES 'glibc-thread-db' | 09:33 |
lpapp | it is probably some eglibc package instead, but I assume this ought to be fixed. | 09:33 |
*** sce <sce!~sce@connected-labs-gw1.ter2.neodc.mpl.cust.as8218.eu> has joined #yocto | 09:35 | |
sce | hello | 09:35 |
sce | is there a way to display my DISTRO_FEATURES var ? | 09:35 |
lpapp | sce: bitbake -e foo | grep ^DISTRO_FEATURES? | 09:36 |
*** phantoxe <phantoxe!~destroy@acarlosss.broker.freenet6.net> has joined #yocto | 09:47 | |
*** dv__ <dv__!~quassel@chello062178118086.5.14.vie.surfer.at> has joined #yocto | 09:47 | |
*** dv_ <dv_!~quassel@chello062178118086.5.14.vie.surfer.at> has quit IRC | 09:48 | |
bluelightning | lpapp: meta/recipes-core/eglibc/eglibc-package.inc:RPROVIDES_eglibc-thread-db = "glibc-thread-db" | 09:48 |
lpapp | bluelightning: yeah, I think that should be removed, IMHO. | 09:49 |
bluelightning | why? | 09:49 |
lpapp | see above, it is source of confusion. | 09:49 |
lpapp | I have been looking for the package everywhere for about half an hour. | 09:50 |
lpapp | and could not find anywhere. | 09:50 |
bluelightning | the source *is* eglibc | 09:50 |
bluelightning | that line is from the eglibc recipe | 09:50 |
lpapp | no | 09:50 |
bluelightning | yes | 09:50 |
lpapp | oh, well, I will not argue. | 09:50 |
lpapp | if you think I have had fun-time looking for the package, there is nothing to discuss. | 09:50 |
lpapp | will just fix it in our fork. | 09:51 |
bluelightning | that package exists here, going right back to dylan | 09:54 |
*** zecke <zecke!~ich@91.66.224.184> has joined #yocto | 09:54 | |
bluelightning | it gets renamed to libthread-db1 per debian library package renaming, but that's all handled internally | 09:55 |
lpapp | let us just drop the topic, you do not see my pain, and I feel it insane. We will not reach any agreement with two completely conflicting opinion. | 09:55 |
bluelightning | I don't know why that library package would not exist on your system | 09:55 |
bluelightning | bottom line is gdb expects that library to exist, removing the dependency would be the wrong thing to do | 09:55 |
lpapp | it has nooooothing to do with removing a dependency. | 09:57 |
lpapp | when opkg tells me a package is missing, I *expect* bitbake to build the package for me if I say bitbake package. | 09:58 |
lpapp | it *should* figure out the details. | 09:58 |
lpapp | that is one serious flaw in my opinion | 09:58 |
lpapp | secondly, when I say bitbake eglibc (or whatever), it does not yield any such packages, either. That is the second big problem. | 09:58 |
lpapp | at least these are problems for me anyhow; ymmv. | 09:59 |
lpapp | I have been trying to solve such a simple issue for about 40 minutes now. Still could not understand what is going on. | 09:59 |
lpapp | and *anyway*, when I say bitbake gdbserver, it should provide all the dependencies automatically, that is the third big problem of mine. | 10:00 |
bluelightning | and normally, it does | 10:00 |
bluelightning | do you have an eglibc-thread-db directory under the packages-split directory for eglibc? | 10:01 |
lpapp | the fourth big problem of mine is that I do not know why it is not optional. | 10:04 |
lpapp | I am not using any threading after all. | 10:04 |
lpapp | or is it necessary for gdbserver to keep working because it is written with threads? | 10:05 |
*** zecke <zecke!~ich@91.66.224.184> has quit IRC | 10:05 | |
lpapp | re 3: find ./tmp/deploy/ipk/ -name \*glibc-thread-db\* yields nothing, but I have nativesdk-eglibc/2.17-r3/packages-split/nativesdk-eglibc-thread-db | 10:05 |
bluelightning | lpapp: as I said above, the package is renamed to libthread-db1 as per debian library package renaming | 10:07 |
bluelightning | do you have an eglibc-thread-db directory under the packages-split directory for eglibc? | 10:07 |
lpapp | why is it renamed and _not_ required that way with opkg? | 10:09 |
lpapp | this is what I was trying to write... | 10:09 |
lpapp | that is bad bad bad bad bad | 10:10 |
bluelightning | opkg should know that libthread_db1 provides that | 10:10 |
lpapp | but _the user_ will not know. | 10:10 |
lpapp | that is the whole point I am trying to make. | 10:10 |
bluelightning | the user shouldn't have to care | 10:10 |
lpapp | yeah, right ... | 10:11 |
lpapp | he should care about wasting an hour :) | 10:11 |
lpapp | to install gdbserver on the board lol | 10:11 |
bluelightning | if you answer my question we can start to debug it, otherwise there's not a lot I can do | 10:11 |
lpapp | I think I already did, and I also do not see what to debug here. | 10:12 |
lpapp | it is fundamentally flawed IMHO, and should be revamped. | 10:12 |
lpapp | if X is the dependency, opkg should say X, no matter what. | 10:12 |
lpapp | you can think of it the other way around, too, if opkg says X, no matter what, Yocto should generate that. | 10:12 |
bluelightning | like I said, normally it does | 10:13 |
lpapp | no no no, you said there is no eglibc-thread-db package. | 10:13 |
JaMa | you can also disable debian.bbclass if you want | 10:13 |
lpapp | let me put it clear: | 10:13 |
lpapp | [1] opkg says eglibc-thread-db -> find ./tmp/deploy/ipkg -name \*eglibc-thread-db\* should find it | 10:13 |
lpapp | OR | 10:14 |
lpapp | [2] opkg says libthread-db1 | 10:14 |
lpapp | everything else is "fun-time" for the end user. | 10:14 |
JaMa | grep packages files so that you cover also all RPROVIDES | 10:14 |
JaMa | using find to do that is stupid | 10:14 |
JaMa | and not surprising that it doesn't cover all cases | 10:15 |
lpapp | doing simple things to achieve the goal is not stupid IMHO | 10:15 |
lpapp | and _anyway_, grep will not help, see above: meta/recipes-core/eglibc/eglibc-package.inc:RPROVIDES_eglibc-thread-db = "glibc-thread-db" | 10:15 |
bluelightning | the point is either the package is there or it isn't, so far we haven't even been able to determine that | 10:15 |
JaMa | lpapp: "simple things" which searches for something else than what you need and what opkg sees _is_ stupid | 10:16 |
lpapp | that _is_ stupid yes, but that means _opkg_ and/or _Yocto_ is stupid, too, in this sense. | 10:16 |
lpapp | it should make life hard, not difficult | 10:17 |
lpapp | who cares about some debian thing. | 10:17 |
JaMa | packages-split as suggested by Paul or greping Packages files is what you need and what opkg will use to determine if the runtime provider is there or not | 10:17 |
lpapp | it just confuses the user. I will certainly patch that out in our fork since IMHO, makes.sense.no.dat. | 10:17 |
lpapp | I understand that is what is needed, but what I am trying to write is, that is _not_ what should be needed. | 10:18 |
gebreselaisi | hey guys | 10:18 |
gebreselaisi | any idea who should provide system-auth? | 10:18 |
gebreselaisi | the pam config file? | 10:18 |
bluelightning | no need to patch it out, just disable debian.bbclass... and if you don't like the dependency at all, use a bbappend to clear it, problem solved | 10:18 |
lpapp | the whole system should not be this complex, since it is really superfluously unnecessary IMHO, with all due respect whoever wrote this "feature". | 10:18 |
lpapp | in fact, I am not even using a debian system, hack. | 10:19 |
lpapp | nor on the host, nor on the target, why on earth would it be automagically done like that by default?/ | 10:19 |
lpapp | I see zero gain, and it wasted one hour of my time as well as some of yours all ... | 10:20 |
JaMa | because it's very useful for majority of distributions | 10:20 |
lpapp | right, we will need to agree to disagree, but I guess that is what forks are good for :) | 10:20 |
JaMa | OE allows you to configure and customize what you want, you don't need to call it "fork" every body has own configuration and that's how it's supposed to be used | 10:21 |
lpapp | no, I do not want this debian class mess in my tree at all | 10:22 |
lpapp | I *do not* want it to be configurable. | 10:23 |
lpapp | I want it to be killed with fire in our tree, so that no one can waste the valuable developer time with it. | 10:23 |
JaMa | heh, I'm off - going to watch trees grow.. | 10:24 |
lpapp | and even if this debian mess is silently and automagically screwed up under the new user, the opkg generation *should* be modified so that opkg does report the renamed stuff. | 10:25 |
lpapp | I have never seen any distribution yet that reports dependency foo, but then you cannot find such a package, and rightfully so IMHO. | 10:26 |
lpapp | so I am not sure what majority was referred above. | 10:26 |
lpapp | even in debian, if I get a missing dependency, I can find that package for installation. | 10:27 |
lpapp | IMHO, it is some broken debian class or something :) | 10:27 |
lpapp | an end user of the system is _not_ supposed to dig into oe/yocto/poky/whatever sources to install a dependency on the distribution. That is not acceptable. It is the system developer that understand the buildsystem, but the end user should _not_. | 10:28 |
lpapp | it is just again, anti-KISS design IMHO. | 10:28 |
lpapp | understands* | 10:28 |
lpapp | if any, I would personally make the default in our fork "no no debian" and give a big warning if someone enables it, but I do not see the need for enabling it altogether, personally. | 10:29 |
*** S_A <S_A!3df6bac6@gateway/web/freenode/ip.61.246.186.198> has joined #yocto | 10:30 | |
S_A | Hi! I need to add support of radeon driver (xf86-video-ati) in my target machine. Any idea how to add | 10:31 |
S_A | ? | 10:31 |
lpapp | I do not even mention the missing documentation for disabling a class, because that is just 100th rank issue, although it goes undocumented or at least it is very hard to discover. I have been trying to grep for it in the documentation, but nothing gives me an example, really. | 10:32 |
lpapp | S_A: get that from the bloated meta-oe layer | 10:33 |
lpapp | S_A: the layer indexer is your friend, http://layers.openembedded.org/layerindex/branch/master/recipes/?q=xf86-video-ati | 10:33 |
bluelightning | lpapp: git grep INHERIT.*debian will tell you that debian.bbclass is enabled through INHERIT_DISTRO, then just set that var to a value that does not include "debian" | 10:35 |
*** belen <belen!~Adium@192.198.151.44> has quit IRC | 10:35 | |
*** belen <belen!~Adium@192.198.151.44> has joined #yocto | 10:36 | |
lpapp | no, it will not. | 10:36 |
bluelightning | lpapp: as with the other changes, you do not need to fork in order to change it | 10:36 |
lpapp | I am using my own tree, I do not have the poky history. Again, I am not a poky developer, I am a poky _end user_. | 10:36 |
lpapp | I think there is some confusion what end user means. | 10:36 |
bluelightning | well, you can of course do as you please, I gave you the answer in any case | 10:36 |
lpapp | bluelightning: huh? I do not need to fork it to kill it with fire? | 10:37 |
lpapp | I want *my tree* to not even considerate it by default, and going even more: I do not want anyone to enable it ever. | 10:37 |
bluelightning | you do not need to fork poky in order to change things like this, you can just set variables in your distro config | 10:37 |
lpapp | I do not see how that can ever happen without fork. | 10:37 |
bluelightning | we do this so that you have less pain when it comes to upgrade | 10:37 |
lpapp | quilt has existed for decades, much less painful than finding a single dependency. | 10:38 |
bluelightning | I'm not sure how that relates to this... | 10:38 |
lpapp | nvm | 10:38 |
*** b00^wk <b00^wk!~dry@port-92-196-88-232.dynamic.qsc.de> has joined #yocto | 10:39 | |
*** hsychla_ <hsychla_!~hsychla@77-64-175-89.dynamic.primacom.net> has joined #yocto | 10:41 | |
lpapp | like I said an hour ago, we will not reach any common agreement here. We have different definitions of what end user is. | 10:42 |
lpapp | from the ground up, essentially. | 10:42 |
bluelightning | our system allows for different distro policies to exist, it even makes it relatively easy for those to be applied on top of the core metadata without changing that core, saving time when that core is upgraded | 10:43 |
bluelightning | the acknowledgement that people want to be able to do different things with the system is built-in | 10:44 |
lpapp | yeah, I, as a distribution developer, fantastically wasted one hour after our user also wasted a significant amount of time. | 10:44 |
*** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has quit IRC | 10:44 | |
lpapp | you think this is wonderful, I think it is awkward, let it be so. We will not convince each other. | 10:45 |
bluelightning | I do not claim it is perfect, I never would | 10:45 |
lpapp | but I am used to not getting my pain heard here anyway :( | 10:46 |
bluelightning | to be frank a lot of that is about how you ask for things sometimes | 10:47 |
bluelightning | or how you respond when an attempt is made to help work through what the problem is | 10:47 |
JaMa | true, I'm still partially interested to see if the package was really created or missing | 10:48 |
JaMa | but instead of simple answer, there is useless discussion about configuration/killing-with-fire | 10:48 |
lpapp | useless for you, and marginal for me. | 10:48 |
lpapp | whether it was created was completely irrelevant, but no, it was not created as I said at least twice. | 10:48 |
JaMa | no you didn't | 10:49 |
lpapp | I am sorry if you had missed it twice. | 10:49 |
lpapp | I gave up on writing it the third time if people do not read what I write. | 10:49 |
lpapp | anyway, I am off /me fixing this in the fork | 10:49 |
JaMa | all you said is that there isn't a file with that filename | 10:49 |
JaMa | which isn't the same thing as "runtime provider" | 10:49 |
*** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has joined #yocto | 10:50 | |
lpapp | in our project, there will be no such stupid time wasters. | 10:50 |
lpapp | that is, what opkg will report will be the dependency, no hidden magic to confuse the user | 10:50 |
lpapp | Yocto does not give this option to us by default, so we have to tweak, no not configure, at all. | 10:50 |
lpapp | configure means I already wasted one hour (effectively more) and our end user, too. | 10:51 |
lpapp | it is too late to realize this is configure. | 10:51 |
lpapp | the time is already wasted; this is not acceptable. | 10:51 |
JaMa | so again you're moving the discussion somewhere else and we'll never know if there is something wrong with gdbserver or not | 10:51 |
*** jonte <jonte!~Jonte@83.218.80.242> has joined #yocto | 10:51 | |
lpapp | JaMa: http://meta.stackexchange.com/questions/66377/what-is-the-xy-problem | 10:53 |
*** belen <belen!~Adium@192.198.151.44> has quit IRC | 10:53 | |
JaMa | I guess not, but I don't want to waste more of my time _trying_ to help you stop wasting your time | 10:53 |
*** belen <belen!~Adium@192.198.151.44> has joined #yocto | 10:53 | |
lpapp | thanks. | 10:53 |
JaMa | 11:34:37 < lpapp> hi, I have never understood this dependency: gdbserver: unsatisfied recommendation for glibc-thread-db | 10:54 |
JaMa | 11:34:41 < lpapp> it looks broken to me | 10:54 |
lpapp | JaMa: I do not think you understand my issue, let it be so. | 10:55 |
lpapp | you think the real issue is whether libfoo-db blabla is generated. | 10:55 |
lpapp | whereas that is red herring in my opinion. | 10:55 |
lpapp | (that is why I linked the XY problem thread above because I think that demonstrates the situation here) | 10:56 |
bluelightning | let me explain how this could have gone | 10:56 |
bluelightning | hypothetically | 10:57 |
bluelightning | is the package produced? no it's empty and thus never exists, why? let's look at the configure output... right, we're configuring out threading, therefore that package shouldn't be expected to exist | 10:58 |
bluelightning | then we could look at trying to pick that up and not having the dependency under those circumstances | 10:58 |
bluelightning | now, I've no idea if that's what's happening, because we weren't able to follow any kind of debugging path even though doing that might seem pointless to you | 10:58 |
bluelightning | it's only in digging to find the root cause (as pointed out in the link you yourself posted above) that we can get to that point | 10:59 |
lpapp | I wrote it several times what my root cause is. Do I really need to write it again? I can, but I do not feel appreciated by not being heard. | 11:00 |
lpapp | "That is, you are trying to solve problem X, and you think solution Y would work, but instead of asking about X when you run into trouble, you ask about Y." -> My problem is X, you are asking about Y. | 11:01 |
bluelightning | if you did then somehow I missed it; and saying "I already said it I won't say it again" probably takes more effort than just repeating it | 11:01 |
lpapp | my problem is: why on earth do I have to install a different package than mentioned?? | 11:01 |
bluelightning | maybe what you said and what I was asking about were two different things | 11:02 |
lpapp | your question is: do you have the renamed package generated?? | 11:02 |
bluelightning | yes, I was attempting to figure out why you even got the failure | 11:02 |
lpapp | so, you confirm you were asking about Y, and I was interested in X, great. Now, let us not go through that again. | 11:03 |
bluelightning | why is there no package named eglibc-thread-db or even glibc-thread-db ? because of debian renaming; and we talked about how to turn that off, which is an option that is already available | 11:03 |
*** belen <belen!~Adium@192.198.151.44> has quit IRC | 11:03 | |
lpapp | yes, I realized it *after* wasting my and my user's time. | 11:04 |
lpapp | wonderful, but not that stuff again ever. | 11:04 |
*** belen <belen!~Adium@192.198.151.44> has joined #yocto | 11:04 | |
lpapp | just .... not! | 11:04 |
lpapp | not not not, this is not acceptable, and I am very likely not alone. | 11:04 |
lpapp | whether the libfoo-db stuff is generated is Y answer. | 11:04 |
lpapp | I do not care whether it is generated or not. I want opkg to report the right stuff for me * all the time * _and_ * by default *. | 11:05 |
lpapp | that means, it is not configuration, it is default, when I clone Yocto. | 11:05 |
bluelightning | opkg can only report what it knows, and all it knows is that a dependency exists on glibc-thread-db and nothing in all of the packages produced provides that | 11:05 |
lpapp | I do not care. It is unacceptable, the system needs improvement. This is not a configuration thing. | 11:06 |
lpapp | anyone cloning Yocto will get into this trouble without superknowledge upfront. | 11:06 |
lpapp | Sorry, but this is not acceptable in _my_ projects with due respect whatever others do. | 11:06 |
bluelightning | I think that might be an exaggeration, because just cloning and building the system to start with I don't think you could hit this error | 11:07 |
bluelightning | you have spent time making quite considerable modifications to your system including changes to poky itself, in your fork | 11:07 |
*** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has quit IRC | 11:07 | |
lpapp | of course, none of the patches was accepted in upstream ever :) | 11:08 |
bluelightning | that is provably false | 11:08 |
lpapp | were* | 11:08 |
bluelightning | some of your patches were not accepted, sure | 11:08 |
lpapp | I am probably blacklisted from contribution. | 11:08 |
lpapp | but I do not care. I think I got all the information that I needed to proceed with my ideas, thanks. | 11:09 |
bluelightning | not at all, we accept reasonable changes from all community members | 11:09 |
*** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has joined #yocto | 11:18 | |
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto | 11:23 | |
*** Net147 <Net147!~Net147@unaffiliated/net147> has joined #yocto | 11:23 | |
*** zecke <zecke!~ich@91.66.224.184> has joined #yocto | 11:26 | |
*** blitz00 <blitz00!stefans@nat/intel/x-rpaedzfvhqxutdlr> has joined #yocto | 11:30 | |
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has joined #yocto | 11:30 | |
*** tasslehoff <tasslehoff!~Tasslehof@77.40.182.98> has left #yocto | 11:35 | |
*** ddalex <ddalex!~ddalex@83.217.123.106> has quit IRC | 11:39 | |
*** ddalex <ddalex!~ddalex@5-14-9-134.residential.rdsnet.ro> has joined #yocto | 11:40 | |
*** RP <RP!~richard@62.156.150.201> has joined #yocto | 11:49 | |
*** RP <RP!~richard@62.156.150.201> has quit IRC | 12:05 | |
*** ritou <ritou!52e6ff24@gateway/web/freenode/ip.82.230.255.36> has joined #yocto | 12:06 | |
ritou | has anyone built image for raspberry b+ with oe? | 12:08 |
*** zeddii_home <zeddii_home!~zeddii_ho@CPEe8de27b71faa-CMbcc810032faf.cpe.net.cable.rogers.com> has joined #yocto | 12:09 | |
lpapp | ritou: yes | 12:10 |
ritou | lpapp: is there any info about that somewhere? id like to crossbuild stuff for the b+ i found older posts but not sure this would work with b+ : http://www.cnx-software.com/2013/07/05/12mb-minimal-image-for-raspberry-pi-using-the-yocto-project/ | 12:11 |
*** rjv16 <rjv16!3df6bac6@gateway/web/freenode/ip.61.246.186.198> has joined #yocto | 12:12 | |
rjv16 | Hi | 12:12 |
ritou | http://www.pimpmypi.com/blog/blogPost.php?blogPostID=7 | 12:13 |
rjv16 | Can anyone guide me to integrate Xorg graphic driver | 12:13 |
*** phantoxe <phantoxe!~destroy@acarlosss.broker.freenet6.net> has quit IRC | 12:17 | |
*** phantoxe <phantoxe!~destroy@a89-152-21-144.cpe.netcabo.pt> has joined #yocto | 12:19 | |
*** lumag <lumag!~lumag@nat-min.mentorg.com> has joined #yocto | 12:27 | |
*** likewise <likewise!~likewise@62.156.150.204> has joined #yocto | 12:30 | |
*** likewise <likewise!~likewise@62.156.150.204> has quit IRC | 12:31 | |
*** likewise <likewise!~likewise@62.156.150.204> has joined #yocto | 12:33 | |
*** likewise <likewise!~likewise@62.156.150.204> has quit IRC | 12:34 | |
sce | hello, does someone know why largefile in DISTRO_FEATURES is an optional distro features | 12:40 |
sce | hello, does someone know why largefile in DISTRO_FEATURES is an optional distro feature | 12:40 |
bluelightning | sce: it's been that way for a long time; perhaps on older 32-bit systems there were memory constraint issues with having it enabled and it wasn't really needed? not sure | 12:42 |
sce | okay so no know sideeffect ? | 12:43 |
bluelightning | of enabling it or removing it? | 12:43 |
bluelightning | it's on by default | 12:43 |
sce | yes in poky.conf you mean ? | 12:44 |
sce | i'm having a special conf that's why it was not on | 12:44 |
sce | but i wanted to confirm that there is no sideeffects | 12:44 |
bluelightning | poky.conf adds it but it's actually defaulted to on in OE-Core's defaultsetup.conf as well | 12:44 |
bluelightning | no, I wouldn't think there would be any sideeffects | 12:45 |
bluelightning | it's not necessarily complete for 32-bit systems, that's a separate issue though (there is a bug open to track that) | 12:45 |
sce | ok thx for your enlightning ;) | 12:46 |
lpapp | sce: because what is the point of enabling it if you do not need it? | 12:47 |
lpapp | it would be illogical to do so. | 12:47 |
sce | i need it that's the point | 12:47 |
lpapp | see, in my case, I have a very small flash, so inherently, I cannot have large files. | 12:47 |
lpapp | I answered this: "hello, does someone know why largefile in DISTRO_FEATURES is an optional distro feature" | 12:48 |
sce | but i guess my team sets originally the DISTRO_FEATURES without largefile | 12:48 |
canci | is there some documentation on how EXPORT_FUNCTIONS works? | 12:50 |
lpapp | the ... what? | 12:51 |
sce | anyway thx alll | 12:52 |
*** rjv16 <rjv16!3df6bac6@gateway/web/freenode/ip.61.246.186.198> has quit IRC | 12:52 | |
canci | (I have one bbclass here which defines do_compile() and another class which sets foo_do_compile() and uses EXPORT_FUNCTIONS - and I am not really sure if/how I can use both classes together) | 12:52 |
lpapp | canci: http://www.yoctoproject.org/docs/1.6/bitbake-user-manual/bitbake-user-manual.html#flexible-inheritance-for-class-functions | 12:52 |
*** Adam_ <Adam_!3df6bac6@gateway/web/freenode/ip.61.246.186.198> has joined #yocto | 12:52 | |
Adam_ | Hi | 12:52 |
canci | lpapp: thank you | 12:52 |
Adam_ | Can anyone provide me information about how to integrate bx-org display driver in YOcto | 12:54 |
*** ritou <ritou!52e6ff24@gateway/web/freenode/ip.82.230.255.36> has quit IRC | 12:56 | |
*** gvy <gvy!~mike@altlinux/developer/mike> has quit IRC | 12:58 | |
*** Net147 <Net147!~Net147@unaffiliated/net147> has quit IRC | 13:02 | |
*** madisox <madisox!~madison@70.90.175.93-BusName-ca.sfba.hfc.comcastbusiness.net> has joined #yocto | 13:03 | |
*** ddalex <ddalex!~ddalex@5-14-9-134.residential.rdsnet.ro> has quit IRC | 13:07 | |
*** Adam_ <Adam_!3df6bac6@gateway/web/freenode/ip.61.246.186.198> has quit IRC | 13:09 | |
*** Adam_ <Adam_!3df6bac6@gateway/web/freenode/ip.61.246.186.198> has joined #yocto | 13:09 | |
Adam_ | I am trying to use xorg graphics driver with the yocto project | 13:10 |
Adam_ | Can anyone plese help me out in integrating | 13:10 |
*** Siecje <Siecje!~Siecje@128.224.252.2> has joined #yocto | 13:13 | |
bluelightning | Adam_: which graphics driver? | 13:22 |
bluelightning | is there already a recipe that builds and/or packages it? | 13:23 |
*** ddalex <ddalex!~ddalex@83.217.123.106> has joined #yocto | 13:24 | |
Adam_ | I am having a recipe | 13:25 |
Adam_ | ati_raedon | 13:25 |
Adam_ | i have enabled the kernel mode settings | 13:26 |
bluelightning | ok, so it seems like you'd only need to add the package to your image then | 13:30 |
bluelightning | see here for several ways of doing that: http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#usingpoky-extend-customimage | 13:30 |
Adam_ | ok | 13:32 |
Adam_ | Is there any way of compilig Xorg alone | 13:35 |
*** nitink <nitink!nitink@nat/intel/x-bgciqqyzrkrpqwgn> has joined #yocto | 13:45 | |
*** cbzx <cbzx!~cbzx@CPE0015f275ebd6-CM00195edd810c.cpe.net.cable.rogers.com> has joined #yocto | 13:50 | |
*** TobSnyder <TobSnyder!~schneider@ip92341b76.dynamic.kabel-deutschland.de> has quit IRC | 13:59 | |
*** ddalex <ddalex!~ddalex@83.217.123.106> has quit IRC | 14:04 | |
bluelightning | Adam_: I guess bitbake xserver-xorg | 14:05 |
*** nitink <nitink!nitink@nat/intel/x-bgciqqyzrkrpqwgn> has quit IRC | 14:05 | |
*** Gintaro <Gintaro!~gintaro@geertswei.nl> has quit IRC | 14:20 | |
*** likewise <likewise!~likewise@62.156.150.204> has joined #yocto | 14:25 | |
*** sce <sce!~sce@connected-labs-gw1.ter2.neodc.mpl.cust.as8218.eu> has quit IRC | 14:26 | |
*** sce <sce!~sce@connected-labs-gw1.ter2.neodc.mpl.cust.as8218.eu> has joined #yocto | 14:27 | |
*** Gintaro <Gintaro!~gintaro@geertswei.nl> has joined #yocto | 14:37 | |
*** SorenHolm <SorenHolm!~quassel@5634f347.rev.stofanet.dk> has joined #yocto | 14:42 | |
*** b00^wk <b00^wk!~dry@port-92-196-88-232.dynamic.qsc.de> has quit IRC | 14:52 | |
*** nitink <nitink!nitink@nat/intel/x-bxfoeoybmenjqmie> has joined #yocto | 15:04 | |
*** ericho <ericho!Erich@nat/intel/x-cqrathqkdoohkzln> has joined #yocto | 15:07 | |
*** tmpsantos <tmpsantos!~tmpsantos@192.198.151.43> has quit IRC | 15:08 | |
blloyd | is there a way to specify that a recipe cannot be built in parallel with any other package? I have a very strange failure case with boost, where it fails to build when building an image, but if built as a target (cleannstate of boost first), it succeeds. Happened multiple times now on two different boxes. | 15:08 |
icanicant | I'm sure it's a FAQ but, is there any way to remove an item from DISTRO_FEATURES without having to make your own distro? (No matter how hacky) | 15:08 |
blloyd | have you tried setting DISTRO_FEATURES = "FEATURES YOU NEED" in local.conf? | 15:10 |
icanicant | blloyd: ah yes, doing that now, but i'd like a solution that works automatically for multiple developers | 15:11 |
blloyd | add that line to a layer.conf file? | 15:11 |
icanicant | blloyd: ah those are parsed at the right time. thanks, i'll give that a go. | 15:13 |
ndec | note that if you just want to remove features, you can do DISTRO_FEATURES_remove = "foo" | 15:14 |
icanicant | ndec: it looks like that one is not in dora | 15:14 |
blloyd | ndec: cool. When did _remove get added. And is it documented? | 15:14 |
blloyd | because I haven't seen it in master docs either... | 15:15 |
bluelightning | blloyd: how does boost fail? | 15:15 |
ndec | i think it was added in dora. | 15:16 |
bluelightning | with regard to advertising DISTRO_FEATURES_remove, I'm wary of anything that discourages people from creating their own distro config | 15:16 |
bluelightning | if anything we should be making that part easier rather than making it easy to avoid | 15:16 |
*** blitz00 <blitz00!stefans@unaffiliated/blitz00> has quit IRC | 15:17 | |
*** dmoseley1 <dmoseley1!~dmoseley@162-196-2-81.lightspeed.chrlnc.sbcglobal.net> has joined #yocto | 15:17 | |
bluelightning | filling up local.conf with things that belong in the distro config if left unchecked can lead to problems reproducing the same build later on another machine | 15:18 |
blloyd | I'm not entirely sure what fails it first time. However, once failed I've looked and cc1plus segfaults on almost instantly on subsequent attempts to build. I suspect it's a resource fauilure where an invalid .o or .a is left and later calls crash when using it. | 15:18 |
bluelightning | blloyd: hmm... boost is quite large, is it possible you're running out of memory and the OOM killer is getting involved? a quick look at the kernel log should reveal if that's the case | 15:19 |
blloyd | I looked and didn't see it. That is exactly what I suspected. Why I asked about something to restrict it. Cut down on resources used at the time. But 16GB with 64GB virtual ram shouldn't run out of ram.... | 15:20 |
*** frsc1 <frsc1!~frsc@host-89-242-129-124.as13285.net> has joined #yocto | 15:21 | |
*** frsc_ <frsc_!~frsc@host-84-13-124-11.opaltelecom.net> has joined #yocto | 15:24 | |
*** frsc <frsc!~frsc@host-89-242-129-124.as13285.net> has quit IRC | 15:24 | |
*** likewise <likewise!~likewise@62.156.150.204> has quit IRC | 15:25 | |
*** frsc1 <frsc1!~frsc@host-89-242-129-124.as13285.net> has quit IRC | 15:27 | |
bluelightning | blloyd: right, scratch that then | 15:28 |
*** lpapp <lpapp!~lpapp@kde/lpapp> has left #yocto | 15:28 | |
bluelightning | it sounds odd, what we'd really want is more information on that first failure | 15:28 |
bluelightning | to answer your question, there is no workaround other than setting dependencies such that one must occur before the other | 15:29 |
blloyd | For full disclosure: I do have a .bbappend for boost to enable some of the libraries that were not enabled by the official package. I like how the latest package handles it's python now. | 15:30 |
bluelightning | ok, that might account for us not seeing the issue up to now, but it doesn't necessarily excuse us from fixing it ;) | 15:31 |
blloyd | thanks blue. What I suspected, but was hopeful in case there was some new capability I hadn't noticed yet. | 15:31 |
bluelightning | I guess what I'd say is, if you manage to get more info on the initial failure please file a bug to track it and include the info on what extra libs you're enabling | 15:32 |
blloyd | Yes, especialy since I plan to propose ALL boost libraries get built, and there is a library that shouldn't be built all the time do it just like the python library is done now. | 15:32 |
*** k-s[WORK] is now known as k-s | 15:35 | |
blloyd | from a diagnosing the problem standpoint, is there a somewhat easy way to see after a build completes what tasks were running in parallel? For instance, if boost build tries to use a file that is being written by another parallel job causing the segfault, it would be helpful to know what other tasks were making sysroot mods at the time. | 15:37 |
bluelightning | so, kind of | 15:37 |
bluelightning | there is support for writing out a "bootchart" style chart which shows which tasks were executing when | 15:37 |
bluelightning | I wonder if that will always show enough of an overlap to be definitive though, but it may be worth looking at | 15:38 |
bluelightning | the odd thing is if it really is just do_rootfs, that shouldn't ever be making changes to the sysroot | 15:39 |
*** dmoseley1 <dmoseley1!~dmoseley@162-196-2-81.lightspeed.chrlnc.sbcglobal.net> has quit IRC | 15:40 | |
blloyd | should and is are too different things, unfortunately. But I was mostly wondering about the possibility of a auto dependency discovery adding usage of a library the image has but which boost recipe doesn't consider a dependency. If the library isn't all the way there then it could account for a build failure that leaves bad .o files. | 15:43 |
*** ddom <ddom!~ddom@p4FFABDCF.dip0.t-ipconnect.de> has quit IRC | 15:51 | |
bluelightning | right, yes that could happen | 15:51 |
bluelightning | we do have a script to check for that sort of thing but I believe it's more suited to testing in world build situations | 15:51 |
bluelightning | I'm not 100% familiar with boost itself but if it does checks within configure to see what dependencies are available and actually reports what is being enabled, you could build just boost from clean (or just from sstate), then build your image and then rebuild boost and see if the configure logs (or even the output with buildhistory) are different | 15:53 |
kergoth | we have a built in sanity check now for runtime deps (e.g. auto-added shlib deps) which are missing build deps, afaik, if thats what you mean by usage of a library | 15:54 |
*** T0mW <T0mW!~Tom@70.15.161.110.res-cmts.t132.ptd.net> has quit IRC | 15:54 | |
*** sjolley <sjolley!sjolley@nat/intel/x-nklwghqciqvqornb> has quit IRC | 15:55 | |
bluelightning | kergoth: right, in master, yes | 15:55 |
*** SorenHolm <SorenHolm!~quassel@5634f347.rev.stofanet.dk> has quit IRC | 15:57 | |
*** eballetbo <eballetbo!~eballetbo@43.Red-2-139-180.staticIP.rima-tde.net> has quit IRC | 15:59 | |
*** phantoxe <phantoxe!~destroy@a89-152-21-144.cpe.netcabo.pt> has quit IRC | 16:03 | |
*** phantoxe <phantoxe!~destroy@acarlosss.broker.freenet6.net> has joined #yocto | 16:04 | |
*** falk0n <falk0n!~falk0n@89.154.11.73> has quit IRC | 16:16 | |
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has quit IRC | 16:18 | |
*** mranostay <mranostay!~mranostay@pdpc/supporter/active/mranostay> has joined #yocto | 16:18 | |
*** sjolley <sjolley!~sjolley@134.134.137.71> has joined #yocto | 16:23 | |
*** ant_work <ant_work!~ant__@host54-128-static.10-188-b.business.telecomitalia.it> has quit IRC | 16:54 | |
*** jbrianceau is now known as jbrianceau_away | 17:02 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 17:37 | |
*** belen <belen!Adium@nat/intel/x-ckxnxudukzokzomp> has joined #yocto | 17:46 | |
*** phantoxe <phantoxe!~destroy@acarlosss.broker.freenet6.net> has quit IRC | 17:48 | |
*** cbzx <cbzx!~cbzx@CPE0015f275ebd6-CM00195edd810c.cpe.net.cable.rogers.com> has quit IRC | 17:54 | |
*** cbzx <cbzx!~cbzx@CPE0015f275ebd6-CM00195edd810c.cpe.net.cable.rogers.com> has joined #yocto | 17:54 | |
*** smartin__ <smartin__!~smartin@ivr94-4-82-229-165-48.fbx.proxad.net> has joined #yocto | 18:18 | |
*** sce <sce!~sce@connected-labs-gw1.ter2.neodc.mpl.cust.as8218.eu> has quit IRC | 18:32 | |
*** jkridner <jkridner!~jkridner@107.19.188.166> has joined #yocto | 18:43 | |
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto | 18:43 | |
*** bboozzoo1away <bboozzoo1away!~mborzecki@78-10-193-111.static.ip.netia.com.pl> has joined #yocto | 18:52 | |
*** bboozzoo_away <bboozzoo_away!~mborzecki@osu194.internetdsl.tpnet.pl> has quit IRC | 18:52 | |
*** eren <eren!~eren@unaffiliated/eren> has quit IRC | 18:52 | |
*** void-dev_ <void-dev_!~voidweb@monoceres.uberspace.de> has joined #yocto | 18:53 | |
*** void-dev <void-dev!~voidweb@monoceres.uberspace.de> has quit IRC | 18:53 | |
*** eren <eren!~eren@unaffiliated/eren> has joined #yocto | 18:53 | |
*** jonte <jonte!~Jonte@83.218.80.242> has quit IRC | 18:53 | |
*** Sput <Sput!~sputnick@quassel/developer/sput> has quit IRC | 18:53 | |
*** mckoan|away <mckoan|away!~marco@unaffiliated/mckoan> has quit IRC | 18:54 | |
*** mckoan|away <mckoan|away!~marco@host56-7-static.30-87-b.business.telecomitalia.it> has joined #yocto | 18:54 | |
*** malik_ <malik_!~malik@anything.ukeer.de> has quit IRC | 18:56 | |
*** Marex <Marex!~Marex@195.140.253.167> has quit IRC | 18:57 | |
*** canci <canci!~nobody@nat-119.westnetz.org> has quit IRC | 18:57 | |
*** ionte <ionte!~jonatan@c-6147e055.164-1-64736c10.cust.bredbandsbolaget.se> has quit IRC | 18:57 | |
*** ionte <ionte!~jonatan@c-6147e055.164-1-64736c10.cust.bredbandsbolaget.se> has joined #yocto | 18:57 | |
*** ericho <ericho!Erich@nat/intel/x-cqrathqkdoohkzln> has quit IRC | 18:58 | |
*** smo <smo!canuck@me.wantsmo.com> has quit IRC | 18:58 | |
*** lumag <lumag!~lumag@nat-min.mentorg.com> has quit IRC | 18:58 | |
*** vignatti <vignatti!~vignatti@annarchy.freedesktop.org> has quit IRC | 18:58 | |
*** DarkKnight_ <DarkKnight_!~quassel@HSI-KBW-149-172-141-211.hsi13.kabel-badenwuerttemberg.de> has quit IRC | 18:58 | |
*** canci <canci!~nobody@nat-119.westnetz.org> has joined #yocto | 18:58 | |
*** malik <malik!~malik@anything.ukeer.de> has joined #yocto | 18:58 | |
*** DarkKnight <DarkKnight!~quassel@HSI-KBW-149-172-141-211.hsi13.kabel-badenwuerttemberg.de> has joined #yocto | 18:58 | |
*** Sput <Sput!~sputnick@quassel/developer/sput> has joined #yocto | 18:58 | |
*** Marex <Marex!~Marex@195.140.253.167> has joined #yocto | 18:59 | |
*** vignatti <vignatti!~vignatti@annarchy.freedesktop.org> has joined #yocto | 18:59 | |
*** smo <smo!canuck@me.wantsmo.com> has joined #yocto | 19:02 | |
*** jonte <jonte!~Jonte@83.218.80.242> has joined #yocto | 19:07 | |
*** alimon <alimon!~alimon@134.134.137.73> has quit IRC | 19:11 | |
*** lumag <lumag!~lumag@nat-min.mentorg.com> has joined #yocto | 19:11 | |
*** jbrianceau_away <jbrianceau_away!uid10952@gateway/web/irccloud.com/x-fguolauwwrgqriak> has quit IRC | 19:11 | |
*** hsychla_ <hsychla_!~hsychla@77-64-175-89.dynamic.primacom.net> has quit IRC | 19:17 | |
*** alimon <alimon!~alimon@134.134.137.73> has joined #yocto | 19:18 | |
*** jimBaxter <jimBaxter!~jbaxter@jimbax.plus.com> has quit IRC | 19:22 | |
*** junland <junland!~junland@173.255.47.222> has joined #yocto | 19:24 | |
*** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has joined #yocto | 19:32 | |
*** bluelightning <bluelightning!~paul@2001:8b0:258:7d7a:2ad2:44ff:fe40:9209> has quit IRC | 19:32 | |
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 19:32 | |
*** ericho <ericho!~Erich@192.55.55.41> has joined #yocto | 19:45 | |
*** rwoolley <rwoolley!~rwoolley@128.224.252.2> has joined #yocto | 19:57 | |
*** cbzx <cbzx!~cbzx@CPE0015f275ebd6-CM00195edd810c.cpe.net.cable.rogers.com> has quit IRC | 20:08 | |
*** cbzx <cbzx!~cbzx@CPE0015f275ebd6-CM00195edd810c.cpe.net.cable.rogers.com> has joined #yocto | 20:09 | |
*** junland <junland!~junland@173.255.47.222> has quit IRC | 20:11 | |
*** zecke <zecke!~ich@91.66.224.184> has quit IRC | 20:14 | |
*** kscherer_ <kscherer_!~kscherer@128.224.252.2> has quit IRC | 20:18 | |
*** SorenHolm <SorenHolm!~quassel@5634f347.rev.stofanet.dk> has joined #yocto | 20:24 | |
*** cbzx <cbzx!~cbzx@CPE0015f275ebd6-CM00195edd810c.cpe.net.cable.rogers.com> has quit IRC | 20:26 | |
*** cbzx <cbzx!~cbzx@CPE0015f275ebd6-CM00195edd810c.cpe.net.cable.rogers.com> has joined #yocto | 20:27 | |
*** junland <junland!~junland@173.255.47.222> has joined #yocto | 20:34 | |
*** SorenHolm <SorenHolm!~quassel@5634f347.rev.stofanet.dk> has quit IRC | 20:43 | |
*** junland <junland!~junland@173.255.47.222> has quit IRC | 20:50 | |
*** junland <junland!~junland@173.255.47.222> has joined #yocto | 20:50 | |
*** SorenHolm <SorenHolm!~quassel@5634f347.rev.stofanet.dk> has joined #yocto | 20:51 | |
*** belen <belen!Adium@nat/intel/x-ckxnxudukzokzomp> has quit IRC | 20:52 | |
*** rwoolley <rwoolley!~rwoolley@128.224.252.2> has quit IRC | 20:55 | |
*** frsc_ <frsc_!~frsc@host-84-13-124-11.opaltelecom.net> has quit IRC | 20:58 | |
*** nitink <nitink!nitink@nat/intel/x-bxfoeoybmenjqmie> has quit IRC | 20:59 | |
*** Siecje <Siecje!~Siecje@128.224.252.2> has left #yocto | 21:08 | |
*** belen <belen!Adium@nat/intel/x-gvbwttyyuwaggaok> has joined #yocto | 21:12 | |
*** hsychla_ <hsychla_!~hsychla@77-64-175-89.dynamic.primacom.net> has joined #yocto | 21:13 | |
*** hramrach_ <hramrach_!~hramrach@gateway/tor-sasl/hramrach> has quit IRC | 21:18 | |
*** belen <belen!Adium@nat/intel/x-gvbwttyyuwaggaok> has quit IRC | 21:19 | |
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has quit IRC | 21:23 | |
*** stryx` <stryx`!~stryx@unaffiliated/stryx/x-3871776> has joined #yocto | 21:30 | |
*** RP <RP!~richard@port-195-158-157-135.static.isionline-dialin.de> has joined #yocto | 21:31 | |
*** smartin__ <smartin__!~smartin@ivr94-4-82-229-165-48.fbx.proxad.net> has quit IRC | 21:32 | |
*** cbzx <cbzx!~cbzx@CPE0015f275ebd6-CM00195edd810c.cpe.net.cable.rogers.com> has quit IRC | 21:35 | |
*** hramrach_ <hramrach_!~hramrach@gateway/tor-sasl/hramrach> has joined #yocto | 21:37 | |
*** cbzx <cbzx!~cbzx@CPE0015f275ebd6-CM00195edd810c.cpe.net.cable.rogers.com> has joined #yocto | 21:46 | |
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC | 21:47 | |
*** jkridner <jkridner!~jkridner@107.19.188.166> has joined #yocto | 21:47 | |
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has joined #yocto | 21:48 | |
*** jkridner <jkridner!~jkridner@pdpc/supporter/active/jkridner> has quit IRC | 21:48 | |
*** junland <junland!~junland@173.255.47.222> has quit IRC | 21:49 | |
*** cbzx <cbzx!~cbzx@CPE0015f275ebd6-CM00195edd810c.cpe.net.cable.rogers.com> has quit IRC | 21:50 | |
*** bfederau <bfederau!~quassel@service.basyskom.com> has quit IRC | 22:01 | |
*** bfederau <bfederau!~quassel@service.basyskom.com> has joined #yocto | 22:01 | |
*** hsychla_ <hsychla_!~hsychla@77-64-175-89.dynamic.primacom.net> has quit IRC | 22:22 | |
*** SorenHolm <SorenHolm!~quassel@5634f347.rev.stofanet.dk> has quit IRC | 22:38 | |
*** edsiper <edsiper!edsiper@monkeyhttpd.osuosl.org> has joined #yocto | 22:41 | |
*** nitink <nitink!nitink@nat/intel/x-jsgzslvejjnpggya> has joined #yocto | 22:56 | |
*** blloyd_ <blloyd_!~blloyd@COX-66-210-177-72-static.coxinet.net> has joined #yocto | 22:56 | |
*** blloyd <blloyd!~blloyd@COX-66-210-177-72-static.coxinet.net> has quit IRC | 22:57 | |
*** madisox <madisox!~madison@70.90.175.93-BusName-ca.sfba.hfc.comcastbusiness.net> has quit IRC | 22:57 | |
*** nerdboy <nerdboy!~sarnold@gatekeeper.gentoogeek.org> has quit IRC | 23:16 | |
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto | 23:16 | |
*** likewise <likewise!~likewise@92.69.197.187> has joined #yocto | 23:21 | |
*** likewise <likewise!~likewise@92.69.197.187> has quit IRC | 23:22 | |
*** likewise <likewise!~likewise@92.69.197.187> has joined #yocto | 23:22 | |
*** likewise <likewise!~likewise@92.69.197.187> has quit IRC | 23:25 | |
*** likewise <likewise!~likewise@92.69.197.187> has joined #yocto | 23:57 |
Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!