| *** kscherer <kscherer!~kscherer@bras-base-otwaon1146w-grc-33-70-53-64-242.dsl.bell.ca> has quit IRC (Quit: Konversation terminated!) | 00:18 | |
| *** qschulz <qschulz!~weechat@ns326003.ip-37-187-106.eu> has quit IRC (Read error: Connection reset by peer) | 00:32 | |
| *** qschulz <qschulz!~weechat@ns326003.ip-37-187-106.eu> has joined #yocto | 00:35 | |
| *** sakoman <sakoman!~steve@dhcp-72-253-4-112.hawaiiantel.net> has quit IRC (Quit: Leaving.) | 01:01 | |
| *** bps <bps!~bps@80.71.142.18> has joined #yocto | 01:04 | |
| *** seninha <seninha!~seninha@user/seninha> has quit IRC (Ping timeout: 255 seconds) | 01:12 | |
| *** bps <bps!~bps@user/bps> has quit IRC (Ping timeout: 265 seconds) | 01:42 | |
| *** Thorn <Thorn!~Thorn@user/thorn> has joined #yocto | 02:13 | |
| *** jclsn <jclsn!~jclsn@2a04:4540:6529:3000:2ce:39ff:fecf:efcd> has quit IRC (Ping timeout: 252 seconds) | 02:20 | |
| *** jclsn <jclsn!~jclsn@2a04:4540:6543:df00:2ce:39ff:fecf:efcd> has joined #yocto | 02:22 | |
| *** mckoan|away <mckoan|away!~marco@host-95-229-48-41.business.telecomitalia.it> has quit IRC (Read error: Connection reset by peer) | 02:25 | |
| *** mckoan|away <mckoan|away!~marco@host-95-229-48-41.business.telecomitalia.it> has joined #yocto | 02:26 | |
| *** tealbird <tealbird!~pidgin@c-98-248-236-18.hsd1.ca.comcast.net> has quit IRC (Ping timeout: 276 seconds) | 02:41 | |
| *** tealbird <tealbird!~pidgin@c-98-248-236-18.hsd1.ca.comcast.net> has joined #yocto | 02:54 | |
| *** tealbird <tealbird!~pidgin@c-98-248-236-18.hsd1.ca.comcast.net> has quit IRC (Ping timeout: 240 seconds) | 03:01 | |
| *** tealbird <tealbird!~pidgin@c-98-248-236-18.hsd1.ca.comcast.net> has joined #yocto | 03:16 | |
| *** tealbird1 <tealbird1!~pidgin@c-98-248-236-18.hsd1.ca.comcast.net> has joined #yocto | 03:22 | |
| *** tealbird <tealbird!~pidgin@c-98-248-236-18.hsd1.ca.comcast.net> has quit IRC (Ping timeout: 255 seconds) | 03:23 | |
| *** Thorn <Thorn!~Thorn@user/thorn> has quit IRC (Ping timeout: 255 seconds) | 04:13 | |
| *** sugarbeet <sugarbeet!~barbas@81.4.123.134> has quit IRC (Ping timeout: 240 seconds) | 04:24 | |
| *** sugarbeet <sugarbeet!~barbas@81.4.123.134> has joined #yocto | 04:36 | |
| *** _whitelogger <_whitelogger!~whitelogg@uruz.whitequark.org> has quit IRC (Remote host closed the connection) | 04:54 | |
| *** _whitelogger <_whitelogger!~whitelogg@uruz.whitequark.org> has joined #yocto | 04:55 | |
| *** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat) | 05:00 | |
| *** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has joined #yocto | 05:01 | |
| *** Notgnoshi <Notgnoshi!~quassel@184-83-95-131-static.midco.net> has quit IRC (Remote host closed the connection) | 05:04 | |
| *** tunahan <tunahan!~tunahan@78.188.72.174> has quit IRC (Quit: tunahan) | 05:04 | |
| *** tunahan <tunahan!~tunahan@78.188.72.174> has joined #yocto | 05:05 | |
| *** Notgnoshi <Notgnoshi!~quassel@184-83-95-131-static.midco.net> has joined #yocto | 05:05 | |
| *** thomasd13 <thomasd13!~thomas@DSL01.212.114.255.148.ip-pool.NEFkom.net> has joined #yocto | 05:23 | |
| *** goliath <goliath!~goliath@user/goliath> has joined #yocto | 06:13 | |
| *** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has joined #yocto | 06:14 | |
| *** frieder <frieder!~frieder@i577B9169.versanet.de> has joined #yocto | 06:14 | |
| *** bps <bps!~bps@80.71.142.18.ipv4.parknet.dk> has joined #yocto | 06:20 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 06:30 | |
| *** invalidopcode942 <invalidopcode942!~invalidop@50.1.244.144> has quit IRC (Quit: The Lounge - https://thelounge.chat) | 06:40 | |
| *** zeddiii <zeddiii!~zeddii@174.112.183.231> has quit IRC (Ping timeout: 240 seconds) | 06:50 | |
| *** zeddii <zeddii!~zeddii@174.112.183.231> has joined #yocto | 06:55 | |
| *** Thorn <Thorn!~Thorn@user/thorn> has joined #yocto | 06:58 | |
| *** paulbarker <paulbarker!~paulbarke@152.236.187.81.in-addr.arpa> has quit IRC (Ping timeout: 252 seconds) | 07:09 | |
| *** paulbarker <paulbarker!~paulbarke@152.236.187.81.in-addr.arpa> has joined #yocto | 07:10 | |
| *** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has joined #yocto | 07:14 | |
| *** zpfvo <zpfvo!~fvo@89.245.205.190> has joined #yocto | 07:17 | |
| mcfrisk | when some recipe fails to apply patches, build eventually fails. But when I enter devshell of the recipe, and something else goes wrong like other patches fail to apply too, then a lot more recipes start to get compiled. This is odd. | 07:17 |
|---|---|---|
| mcfrisk | takes to much time for bitbake exit when things fail | 07:18 |
| mcfrisk | now I wait for rust, cargo, clang etc native unpack tasks | 07:18 |
| *** michaelo <michaelo!~mike@shells.bootlin.com> has quit IRC (Ping timeout: 252 seconds) | 07:21 | |
| *** tperrot <tperrot!~tprrt@shells.bootlin.com> has quit IRC (Ping timeout: 250 seconds) | 07:21 | |
| *** abelloni <abelloni!~abelloni@2001:41d0:305:1000::2a58> has quit IRC (Ping timeout: 264 seconds) | 07:21 | |
| LetoThe2nd | yo dudX | 07:32 |
| *** zpfvo <zpfvo!~fvo@89.245.205.190> has quit IRC (Ping timeout: 265 seconds) | 07:33 | |
| mcfrisk | if this because devshell depends on all the native tools to be in sysroot? I guess so. need to find an alternative to avoid waiting for all the clang, rust, cargo things to compile before I can see if a patch can be dropped or not. the host dependencies are getting really complicated | 07:42 |
| *** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (Quit: ZZZzzz…) | 07:43 | |
| *** zpfvo <zpfvo!~fvo@i59F5CDBE.versanet.de> has joined #yocto | 07:48 | |
| *** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto | 07:57 | |
| *** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection) | 08:02 | |
| *** GNUmoon <GNUmoon!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto | 08:03 | |
| *** luffy[m]1 <luffy[m]1!~luffyinte@2001:470:69fc:105::3:4cd5> has joined #yocto | 08:07 | |
| *** amitk_ <amitk_!~amit@103.59.74.51> has joined #yocto | 08:10 | |
| *** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat) | 08:15 | |
| *** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has joined #yocto | 08:16 | |
| *** davidinux <davidinux!~davidinux@185.183.181.92> has joined #yocto | 08:17 | |
| wyre | hi guys, not sure why I'm having this issue WARNING: Setscene task (/home/pokyuser/builds/joifi-engicam-mx6-dunfell/sources/poky/meta/recipes-devtools/qemu/qemuwrapper-cross_1.0.bb:do_package_setscene) failed with exit code '1' - real task will be run instead for qemuwrapper-cross_1.0.bb:do_package_setscene | 08:26 |
| *** pidge <pidge!~pidge@194.110.145.185> has quit IRC (Ping timeout: 246 seconds) | 08:31 | |
| mcfrisk | wyre: were there files missing or corrupt on your sstate cache? If that was the case, then falling back to real tasks is handy | 08:35 |
| wyre | mcfrisk, so should I remove sstate-cache folder? | 08:38 |
| LetoThe2nd | i have a situation where I *think* wic damages a partition. the partition content is pre-generated, and the binary blob is fine judging by fsck. then it goes into wic, using a "part --source rawcopy" line, and the partition content is defective. any ideas/pointers? | 08:39 |
| mcfrisk | wyre: no, don't. the warning just means that sstate cache for that task failed and real task got executed instead. the build is recovering from the failure. You could try to understand what had gone wrong. possibly an interupted build or sstate cache action, or maybe files were really damaged. | 08:45 |
| *** bps <bps!~bps@user/bps> has quit IRC (Ping timeout: 255 seconds) | 09:03 | |
| *** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto | 09:04 | |
| *** vm1 <vm1!~vm1@165.1.243.138> has joined #yocto | 09:04 | |
| *** davidinux <davidinux!~davidinux@185.183.181.92> has quit IRC (Quit: WeeChat 3.5) | 09:07 | |
| *** amitk__ <amitk__!~amit@103.59.74.26> has joined #yocto | 09:10 | |
| *** amitk_ <amitk_!~amit@103.59.74.51> has quit IRC (Ping timeout: 276 seconds) | 09:13 | |
| *** prabhakarlad80 <prabhakarlad80!~prabhakar@pc.renesas.eu> has joined #yocto | 09:14 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Connection closed) | 09:14 | |
| *** prabhakarlad80 <prabhakarlad80!~prabhakar@pc.renesas.eu> has quit IRC (Client Quit) | 09:15 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto | 09:15 | |
| jbo | Hey guys, I am trying to create a new layer with the sole goal of modifying some configuration of the 'microchip-headless-image' recipe provided by meta-atmel. From what I understand by now, all I have to do is creating a new layer (eg. via bitbake-layers create-layer) and then having a .bbappend file in there named the same as the one supplied by meta-atmel. Is that correct? From there, do I have to do anything other than adding the layer using bitbake-layers | 09:15 |
| jbo | add-layer ? How can I verify that my .bbappend file is actually being processed? | 09:15 |
| vm1 | Hi. did you try bitbake-layers show-appends? | 09:19 |
| LetoThe2nd | jbo: bitbake -e and bitbake-layers show-appends. | 09:19 |
| mcfrisk | jbo: conf/bblayers.conf needs to have the new layer, then verify with "bitbake -e recipe" that your changes in bbappends are taking effect. | 09:19 |
| jbo | thanks, I'll give that a try | 09:20 |
| *** Idontknow <Idontknow!~Idontknow@43-127-61-5.reverse.tnp.net.uk> has joined #yocto | 09:24 | |
| Idontknow | Why should one learn yocto if there is always someone or some group that prepares all the meta- layers anyway? Please note I'm trying to get an understanding of the possible scenario's that one can find in practice (obviously there is a more advanced method of using it for a particular scenario). Because as an end-user I'll be spoiled and I need to | 09:27 |
| Idontknow | do some minor modifications at the end, so why should someone delve into the yocto project if everything is chewed for us? Again, I'm trying to understand it not deteriorate the amazing yocto project. | 09:27 |
| LetoThe2nd | Idontknow: two reasons, very practical: 1) somebody has to do the chewing, so the skill raises ones market value 2) the "minor modifications" are often not that minor, and trying to do them without at least some level of understanding leads to a lot of wasted time. | 09:29 |
| LetoThe2nd | Idontknow: especially the latter we see time and again. "i just want to...", but it often doesn't work like thatä. | 09:30 |
| *** ChanServ sets mode: +o LetoThe2nd | 09:38 | |
| *** ChanServ sets mode: -o LetoThe2nd | 09:38 | |
| *** bps <bps!~bps@193.89.194.60> has joined #yocto | 09:38 | |
| *** ChanServ sets mode: +o LetoThe2nd | 09:39 | |
| *** ChanServ sets mode: -o LetoThe2nd | 09:39 | |
| Idontknow | LetoThe2nd Now I know:) | 09:39 |
| Idontknow | thanks | 09:40 |
| Idontknow | Is Rust the new savior on the block that will take over in the technology space this decade? Especially with new projects coming up. | 09:45 |
| jbo | some say yes, others say no. | 09:45 |
| *** d-s-e <d-s-e!~d.s.e@2001:a61:12e1:1101:70f7:7954:e909:b6a3> has joined #yocto | 09:45 | |
| Idontknow | Because it makes it difficult to choose now which one to go for, C++ has established itself now but if I learn Rust there is currently nothing really going on... | 09:47 |
| jbo | I'm more than happy with modern C++. getting better on each release. | 09:48 |
| jbo | but this is not the channel for that. | 09:48 |
| jbo | these questions just spark heavily biased religious flamewars that won't provide you with a reasonable "answer" (because there probably isn't any other than "it depends") | 09:49 |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 09:50 | |
| vm1 | go with go ;-) | 09:50 |
| Idontknow | jbo true | 09:50 |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 09:50 | |
| Idontknow | vm1 I'd rather use assembly... | 09:50 |
| jbo | if that is your stake then I think rust it not for you. just use C++. | 09:51 |
| *** seninha <seninha!~seninha@user/seninha> has joined #yocto | 09:53 | |
| LetoThe2nd | Idontknow: it sounds like you either are trying to get confirmation from us for some idea you have. what is your actual goal, or reason why you joined us? "should I learn yocto", "should i use rust", "should i..." - such question should not be answered based on what somebody likes best, but what actually matches your requirements. so maybe better tell us about the *actual* project and requirements. | 09:55 |
| jbo | +1 | 09:55 |
| *** kanavin <kanavin!~Alexander@2a02:2454:29b:c000:59ca:78e1:31c2:e088> has joined #yocto | 09:56 | |
| Idontknow | LetoThe2nd The actual project is to create GUI's for embedded systems. GTK uses C, Slint uses Rust (beta stage), Qt uses C++, etc. However, Google said that in its chrome project 70% are bugs due to memory stuff going on (so C++ programming) which is why I'm doubting to delve into C++ in the first place. Rust seems to solve that problem, but there | 09:59 |
| Idontknow | isn't much going on in terms of actual big frameworks (slint is ju | 09:59 |
| Idontknow | slint has just started | 09:59 |
| LetoThe2nd | Idontknow: that is no requirement, thats a goal. | 10:00 |
| Idontknow | I don't want to spend all my time learning GTK+C or Qt+C++ and then after a year something hot comes up with Rust which solves the problems that Google is facing... | 10:00 |
| Idontknow | LetoThe2nd Can't a goal be a requirement for an engineer? | 10:00 |
| LetoThe2nd | Idontknow: no. | 10:00 |
| Idontknow | On job advertisements they say: Requirements: .... C++, etc. | 10:01 |
| LetoThe2nd | Idontknow: there are projects that have goals but no requirements, but those are rare (and mostly its just engineers ignoring that they have to think about requirements) | 10:01 |
| svuorela_ | memory stuff in c++ stuff is also happening more in old codebases from before allowing c++11, 17 and later... chrome's code base is very old. from before 2000. | 10:02 |
| Idontknow | LetoThe2nd hmm | 10:02 |
| LetoThe2nd | Idontknow: example: "has to build from source" is a possible requirement. "has be compliant to this licensing situation" is a requirement. "has to be maintained upstream for this period of time" is a requirement. | 10:02 |
| Idontknow | svuorela_ aaaah like that | 10:02 |
| Idontknow | LetoThe2nd I understand now | 10:03 |
| Idontknow | thanks | 10:03 |
| LetoThe2nd | Idontknow: so if your project is "i want to build a gui and i want to use the latest and coolest sh**tz", that is not a requirement, tbh, thats a junior/student/intern statement about a thing that will not leave their table. | 10:03 |
| LetoThe2nd | "has to run on this hardware" is a requirement. "has to fulfill this standard" is a requirement. | 10:05 |
| jbo | and on the notion of "rust seems to solve that problems" new languages arise all the time that claim to solve a problem. in practise, they rarely do - or they introduce new problems. There is no such thing as a free lunch. new hype languages come and go. some stay, but few do. | 10:05 |
| LetoThe2nd | "has to have this cool buzzword" is... marketing. | 10:05 |
| Idontknow | As a junior I want to be future-proof basically if I'm going to spend my time on it, but I'm glad I got your feedback (sorry if this wasn't the channel for it but there are some very smart people here, won't ask it in the future though) | 10:06 |
| Idontknow | Thanks!!! | 10:06 |
| jbo | when I invest time writing something I want to do it once and then re-use it for the decades to come. This is why I am still defaulting to C/C++ for most stuff. $NewHypedLanguage can disappear and definitely changes frequently enough to break working stuff. | 10:07 |
| LetoThe2nd | it just DEPENDS(tm) | 10:08 |
| jbo | also it's easy to use stuff written in C/C++ in other, higher level languages. you can use your C/C++ stuff in go, rust, javascript, python.... but it doesn't work the other way around. | 10:08 |
| jbo | but yes, as mentioned initially and now again by LetoThe2nd: "it depends" - as always. If you just need a one-off with no resuability requirements, do whatever. this always applies: the right tool for the job. | 10:09 |
| *** mihai2 <mihai2!~mihai@user/mihai> has joined #yocto | 10:09 | |
| Idontknow | jbo Good point, it was just that Google stated their problems and that they're switching to Rust (e..g. android codebase) and Rust is developed by some very good developers which made me doubt. Using C++ stuff in other languages is done by bindings which detoriate performance though | 10:09 |
| jbo | Idontknow, google also just brought 'carbon' to the world to solve problems. Google is not just one thing. And as a person having to work with google libraries, languages and infrastructure way too often I can tell you one thing: When google does something, it's to solve one of their problems. And the types of problems that Google has rarely to never applies to anybody else. | 10:10 |
| LetoThe2nd | jbo: think about this : "if you had problems the kind and scale Google has, you would not be here asking us" | 10:10 |
| LetoThe2nd | jbo: heh, great minds think alike it seems. | 10:11 |
| jbo | LetoThe2nd, indeed | 10:11 |
| jbo | LetoThe2nd, glad that I could illustrate that after my noob questions yesterday. | 10:11 |
| Idontknow | jbo LetoThe2nd You don't know how happy I am to get your feedback, thanks a lot I learnt so much! Wish you all the best! | 10:11 |
| rburton | urgh, i missed google announcing carbon. someone definitely is getting a bonus for each new language released. | 10:12 |
| jbo | Idontknow, this is personal/subjective: I spent time learning C and later C++. and I did it properly. And I do not regret it at all. Whenever other people are stuck because they can't do something because they only know $FancyLanguageA and $FancyLanguageB they are either incapable of learning the proper stuff (because they lack the deeper knowledge you get when doing C/C++) or they have to spend months learning $FancyLanguageC. Meanwhile, I can do virtually anything | 10:13 |
| jbo | with C/C++. | 10:13 |
| LetoThe2nd | jbo: i try (not always succeed, but hey!) to judge people by their behaviour, not by the level of their questions. | 10:13 |
| jbo | LetoThe2nd, reasonable approach +1. | 10:14 |
| LetoThe2nd | rburton: there has been a lot of word about them having bonuses for projects going live, and probably programming languages count as projects. | 10:14 |
| rburton | indeed | 10:14 |
| jbo | just had to increase my ubuntu VM disk because the yocto build aborted :x | 10:18 |
| *** Idontknow <Idontknow!~Idontknow@43-127-61-5.reverse.tnp.net.uk> has quit IRC (Quit: Client closed) | 10:19 | |
| rburton | rm_work ftw, in a vm | 10:20 |
| jbo | I assume that would make any subsequent builds rebuilding instead of doing incremental builds? | 10:21 |
| rburton | it removes the build tree for each recipe when they finish. if a recipe needs a rebuild it will build from scratch anyway. | 10:22 |
| rburton | _if_ you're doing incremental builds on a slow recipe that you're iterating on then you can disable it for that recipe. | 10:23 |
| jbo | thanks for the hint | 10:24 |
| *** ImNotABot <ImNotABot!~ImNotABot@43-127-61-5.reverse.tnp.net.uk> has joined #yocto | 10:24 | |
| barath | what are people's thoughts on properly isolating layers per multiconfig? it seems that currently layer priorities are calculated based on which layers are enabled for the "default" mc only. so another multiconfig might enable a layer not enabled in the "default" multiconfig, and it'll work, but all the bbfiles in that layer will be priority 0 because it those priorities are calculated for the "default" multiconfig... | 10:25 |
| jbo | it seems like my .bbappend to modify the microchip-headless-image has succeeded. It is being listed under bitbake-layers show-appends and it is currently no longer building nodejs (which I removed in my append file) | 10:26 |
| LetoThe2nd | jbo: tip: usually its *MUCH* better to create a standalone image, based on core-image-minimal or core-image-base and add from there, instead of tying stuff to an existing, bloated demo image and removing stuff. | 10:29 |
| ImNotABot | I get: ERROR: Task (/home/dell/poky/meta/recipes-connectivity/bluez5/bluez5_5.66.bb:do_compile) failed with exit code '1' and I am on the master branch, I'm trying to compile for qemu (arm). Is there something with the master branch because on internet they say to change the bluez version? | 10:29 |
| rburton | ImNotABot: can you share the actual error? | 10:29 |
| rburton | ImNotABot: also best to use a release branch, not master, unless you want to work on master. mickledore is about to release so use that if you want to feel modern. | 10:30 |
| ImNotABot | Sstate summary: Wanted 76 Local 0 Mirrors 0 Missed 76 Current 1530 (0% match, 95% complete) | 10:30 |
| ImNotABot | NOTE: Executing Tasks | 10:30 |
| ImNotABot | ERROR: bluez5-5.66-r0 do_compile: oe_runmake failed | 10:30 |
| ImNotABot | ERROR: bluez5-5.66-r0 do_compile: ExecutionError('/home/dell/poky/build/tmp/work/cortexa15t2hf-neon-poky-linux-gnueabi/bluez5/5.66-r0/temp/run.do_compile.53746', 1, None, None) | 10:30 |
| ImNotABot | ERROR: Logfile of failure stored in: /home/dell/poky/build/tmp/work/cortexa15t2hf-neon-poky-linux-gnueabi/bluez5/5.66-r0/temp/log.do_compile.53746 | 10:30 |
| ImNotABot | rburton I think I need to remove the build directory: https://community.nxp.com/t5/i-MX-Processors/bitbake-build-failed-error-code-1/td-p/1206161 (but then I have to rebuild and wait for everything) | 10:31 |
| *** yssh <yssh!~yssh@2401:4900:5137:8498:3ac1:943:d3a7:1c42> has joined #yocto | 10:31 | |
| rburton | removing build dir won't rebuild anything, as you have sstate | 10:31 |
| rburton | just don't delete sstate | 10:31 |
| ImNotABot | rburton ok thank you! | 10:31 |
| rburton | the actual error would be good though | 10:31 |
| rburton | that is saying "the task failed" | 10:31 |
| rburton | what is in log.do_compile.53746 | 10:32 |
| rburton | hm executionerror might suggest that your build dir is mangled, or your disk is very full, or something | 10:32 |
| ImNotABot | DEBUG: Executing python function autotools_aclocals | 10:32 |
| ImNotABot | DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common'] | 10:32 |
| ImNotABot | DEBUG: Python function autotools_aclocals finished | 10:33 |
| ImNotABot | DEBUG: Executing shell function do_compile | 10:33 |
| ImNotABot | NOTE: make -j 24 | 10:33 |
| ImNotABot | make --no-print-directory all-am | 10:33 |
| ImNotABot | make[1]: *** [Makefile:5689: monitor/btmon] Error 1 | 10:33 |
| ImNotABot | make: *** [Makefile:4468: all] Error 2 | 10:33 |
| ImNotABot | ERROR: oe_runmake failed | 10:33 |
| ImNotABot | WARNING: exit code 1 from a shell command. | 10:33 |
| ImNotABot | I did ctrl+c it when my internet speed dropped and then I re-run it again after re-connecting to another wifi access point | 10:33 |
| rburton | try bitbake bluez5 -C unpack to force it to rebuild | 10:33 |
| jbo | LetoThe2nd, that makes sense. I'll try to go down that road. I guess I can always have a look at the demo image to figure out which bits & pieces I might need. | 10:34 |
| ImNotABot | Is it generally recommended to use the latest release branch, for example mickledore? Or will the answer be: it depends:) | 10:34 |
| rburton | yes, unless you're developing yocto/oe then work on either the latest stable or LTS release | 10:34 |
| rburton | depending on your needs | 10:35 |
| rburton | (they have different lifetimes) | 10:35 |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 10:35 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto | 10:36 | |
| ImNotABot | rburton I've used "bitbake bluez5 -C unpack" and it seems to be working as it continues the build with no errors, currently at 96% | 10:36 |
| rburton | your rapid control-c probably left make writing broken files and make is terrible so it needed a clean | 10:37 |
| rburton | a single control-c will let all tasks finish cleanly and not cause problems like this | 10:37 |
| ImNotABot | Will force rebuilding take care of any broken files and thus the final image won't be corrupted? Single control-c seemed to be stuck so I pressed it again :( | 10:37 |
| rburton | it didn't finish compiling, so there are no broken files to install | 10:38 |
| ImNotABot | rburton Thanks it worked: NOTE: Tasks Summary: Attempted 1951 tasks of which 1912 didn't need to be rerun and all succeeded. | 10:38 |
| ImNotABot | Summary: There was 1 WARNING message. | 10:38 |
| ImNotABot | WARNING: /home/dell/poky/meta/recipes-connectivity/bluez5/bluez5_5.66.bb:do_unpack is tainted from a forced run | 10:38 |
| *** leo738 <leo738!~leo738@188-141-96-236.dynamic.upc.ie> has joined #yocto | 10:41 | |
| *** pidge <pidge!~pidge@194.110.145.185> has joined #yocto | 10:47 | |
| *** d-s-e <d-s-e!~d.s.e@2001:a61:12e1:1101:70f7:7954:e909:b6a3> has quit IRC (Ping timeout: 265 seconds) | 11:09 | |
| *** suwako[m] <suwako[m]!~suwakohot@2001:470:69fc:105::3:4c2d> has joined #yocto | 11:12 | |
| *** vm1 <vm1!~vm1@165.1.243.138> has quit IRC (Ping timeout: 245 seconds) | 11:20 | |
| *** vm1 <vm1!~vm1@165.1.243.138> has joined #yocto | 11:31 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 11:35 | |
| *** leo738 <leo738!~leo738@188-141-96-236.dynamic.upc.ie> has quit IRC (Quit: Client closed) | 11:39 | |
| *** amitk__ <amitk__!~amit@103.59.74.26> has quit IRC (Ping timeout: 265 seconds) | 11:40 | |
| *** yssh <yssh!~yssh@2401:4900:5137:8498:3ac1:943:d3a7:1c42> has quit IRC (Ping timeout: 245 seconds) | 11:46 | |
| ImNotABot | rburton I did expect the entire build to continue after "bitbake bluez5 -C unpack" but it seems I have to re trigger the build core-image-base (which is not a problem of course). With linux whenever I install vscode and it says it is missing a package and I install that missing package, then vscode continues installing after that which is pretty | 11:52 |
| ImNotABot | neat. | 11:52 |
| ImNotABot | Are the "core-image-*" pure examples or can they be used for production ready devices (bitbake core-image-base for example)? | 11:54 |
| rburton | ImNotABot: bitbake bluez5 will just build bluez5, yes | 11:54 |
| rburton | write your own images, so you own them | 11:54 |
| rburton | same reason you make your own distro and not ship product using poky | 11:55 |
| *** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto | 11:58 | |
| ImNotABot | poky is a example indeed. Could you please direct me to a starting point (as in the manual the main topic is centered around poky)? | 11:58 |
| ImNotABot | Because as it stands now, I do not understand why poky which builds a customizable bootable image should not be production ready? sorry | 12:00 |
| ImNotABot | even though poky is a reference/example | 12:00 |
| *** vm1 <vm1!~vm1@165.1.243.138> has quit IRC (Quit: Client closed) | 12:01 | |
| jbo | if I'd like to add alsa-utils to my core-minimal-image based layer, would I simply do a PACKAGES += alsa-utils or is it more invovled than that? | 12:07 |
| jbo | ah, seems like it's IMAGE_INSTALL += alsa-utils need to read up on the difference. | 12:09 |
| landgraf | jbo: IMAGE_INSTALL:append intead of += to avoid funny ordering issues | 12:10 |
| jbo | thank you! It appears to be building alsa-utils now :) | 12:12 |
| jbo | a question regarding kernel configs: I'm not yet clear whether I should use menuconfig and it then stores the .conf in the build (?) directory or whether the kernel config tweaks should also happen via my custom layer. could somebody provide a hint so I know which direction to dig? | 12:13 |
| *** ImNotABot <ImNotABot!~ImNotABot@43-127-61-5.reverse.tnp.net.uk> has quit IRC (Quit: Client closed) | 12:14 | |
| landgraf | jbo: docs.yoctoproject.org has good extensive documentation on the topic | 12:15 |
| landgraf | jbo: https://docs.yoctoproject.org/kernel-dev/common.html#configuring-the-kernel | 12:15 |
| landgraf | start from here ) | 12:15 |
| jbo | thanks! I was already in the process of reading that. I guess I just have to keep going :) | 12:17 |
| * zeddii is back. if you've been looking for me Mon/Tuesday, I'll be digging into email shortly | 12:28 | |
| jbo | A question regarding "2.6.1 Using menuconfig": https://docs.yoctoproject.org/kernel-dev/common.html#using-menuconfig | 12:29 |
| jbo | the instructions tell you to go to the poky dir, then running: bitbake linux-yocto -c kernel_configme -f | 12:29 |
| jbo | that also applies if I will subsequently run bitbake core-minimal-image right? | 12:30 |
| jbo | core-minimal-image* | 12:30 |
| jbo | running the command in the /poky dir yields: ERROR: Task do_kernel_configme does not exists for target core-image-minimal | 12:31 |
| *** tunahan <tunahan!~tunahan@78.188.72.174> has quit IRC (Quit: tunahan) | 12:34 | |
| *** tunahan <tunahan!~tunahan@78.188.72.174> has joined #yocto | 12:35 | |
| rburton | jbo: menuconfig is specific to the kernel, not the image | 12:36 |
| jbo | rburton, indeed. just trying to figure out whether there is any magic happening under the hood that would be good to know about - thanks for the clarification! | 12:37 |
| *** amitk_ <amitk_!~amit@103.59.74.41> has joined #yocto | 12:38 | |
| rburton | the magic is any recipe that inherits cml1 gets a menuconfig task | 12:38 |
| rburton | so thats the kernel and uboot | 12:38 |
| jbo | as in: the docs tell you to source oe-init-build-env first, which I do. but then that drops me into a new build dir rather than the build dir I was using for the core image before. Yocto will just pull the kernel from /build then when I later rebuild the core-image from my /build-myproject? | 12:39 |
| *** Xagen <Xagen!~Xagen@99-135-179-142.lightspeed.austtx.sbcglobal.net> has quit IRC (Ping timeout: 240 seconds) | 12:39 | |
| rburton | jbo: . oe-init-build-env takes a build directory name, and only uses ./build/ if you don't tell it otherwise | 12:39 |
| jbo | ah, so the idea is indeed to use the same build dir as I was before when doing the kernel config, right? | 12:39 |
| rburton | yeah, separate build directories are entirely separate | 12:40 |
| jbo | great - thanks for the clarification. | 12:40 |
| rburton | if you have multiple you can configure them to share DL_DIR and SSTATE_DIR | 12:40 |
| jbo | I'll save that for when I know what I'm actually doing :) | 12:40 |
| jbo | alright, doing the bitbake linux-yocto -c kernel_configme -f in my /build-myproject build dir yields the error that 'Nothing PROVIDES 'linux-yocto'. I assume that the atmel layer I use uses their own kernel and I need to figure out which one that is / what it is named, right? | 12:41 |
| jbo | linux-mchp it is :) | 12:41 |
| rburton | virtual/kernel will work and pick the right recipe | 12:43 |
| jbo | alright, that would be bitbake -c menuconfig virtual/kernel and my assumption is that virtual/* allows to setup sort of "symlinks"? | 12:44 |
| rburton | yeah | 12:45 |
| jbo | thanks! | 12:45 |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto | 12:59 | |
| *** rob_w <rob_w!~bob@host-82-135-31-73.customer.m-online.net> has quit IRC (Remote host closed the connection) | 12:59 | |
| jbo | okay, this seems to work out well. removed bluetooth support, created the image, flashed, booted -> no more bluetooth :) | 13:00 |
| rburton | you removed bluetooth by changing DISTRO_FEATURES, right | 13:00 |
| jbo | nah, removed bluetooth support from the kernel config (Networking support -> Bluetooth subsystem support) | 13:01 |
| *** davidinux <davidinux!~davidinux@217.146.90.114> has joined #yocto | 13:02 | |
| jbo | based on your comment/question I take it that this is not the way to go? | 13:02 |
| *** amitk_ <amitk_!~amit@103.59.74.41> has quit IRC (Ping timeout: 248 seconds) | 13:07 | |
| rburton | well, there's two parts. the kernel not supporting something doesn't stop bluez being in the images. | 13:08 |
| *** davidinux <davidinux!~davidinux@217.146.90.114> has quit IRC (Quit: WeeChat 3.5) | 13:21 | |
| *** d-s-e <d-s-e!~d.s.e@2001:a61:12e1:1101:70f7:7954:e909:b6a3> has joined #yocto | 13:27 | |
| jbo | indeed | 13:34 |
| jbo | I did assume that the core-image-minimal wouldn't include something such as bluetooth functionalities/utilities. | 13:35 |
| jbo | but I'm still in the process of getting comfortable with the overal system & environment | 13:35 |
| *** kscherer <kscherer!~kscherer@bras-base-otwaon1146w-grc-33-70-53-64-242.dsl.bell.ca> has joined #yocto | 13:39 | |
| landgraf | jbo: "Everything Is Better With Bluetooth" (c) | 13:51 |
| jbo | hah :p | 13:52 |
| jbo | just did an ifconfig eth0 down on my target device and it rebooted. fun. | 13:52 |
| *** sakoman <sakoman!~steve@dhcp-72-253-4-112.hawaiiantel.net> has joined #yocto | 13:57 | |
| *** Xagen <Xagen!~Xagen@4.14.206.69> has joined #yocto | 13:59 | |
| *** Spooster <Spooster!~Spooster@50.231.134.226> has joined #yocto | 14:04 | |
| *** Spooster <Spooster!~Spooster@50.231.134.226> has quit IRC (Read error: Connection reset by peer) | 14:04 | |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 260 seconds) | 14:09 | |
| *** nemik <nemik!~nemik@76.74.126.42> has joined #yocto | 14:09 | |
| *** nemik <nemik!~nemik@76.74.126.42> has quit IRC (Ping timeout: 246 seconds) | 14:13 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 14:14 | |
| *** rcw <rcw!~rcwoolley@45.72.202.88> has joined #yocto | 14:35 | |
| *** Minvera <Minvera!~Minvera@user/Minvera> has joined #yocto | 14:51 | |
| *** ajfriesen <ajfriesen!~ajfriesen@p54b94d31.dip0.t-ipconnect.de> has quit IRC (Quit: The Lounge - https://thelounge.chat) | 15:00 | |
| *** Xagen <Xagen!~Xagen@4.14.206.69> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…) | 15:01 | |
| *** Xagen <Xagen!~Xagen@4.14.206.69> has joined #yocto | 15:03 | |
| *** ajfriesen <ajfriesen!~ajfriesen@p54b94d31.dip0.t-ipconnect.de> has joined #yocto | 15:05 | |
| *** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto | 15:19 | |
| *** amitk_ <amitk_!~amit@103.59.74.41> has joined #yocto | 15:33 | |
| *** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (Quit: xmn) | 15:33 | |
| *** bps <bps!~bps@user/bps> has quit IRC (Ping timeout: 252 seconds) | 15:41 | |
| *** pidge <pidge!~pidge@194.110.145.185> has quit IRC (Ping timeout: 276 seconds) | 15:50 | |
| *** d-s-e <d-s-e!~d.s.e@2001:a61:12e1:1101:70f7:7954:e909:b6a3> has quit IRC (Quit: Konversation terminated!) | 16:00 | |
| *** rfuentess <rfuentess!~rfuentess@static-5-51-117-151.ftth.abo.bbox.fr> has quit IRC (Remote host closed the connection) | 16:07 | |
| *** meego <meego!~meego@2a01:e0a:e5:3260:2501:2d1:34ea:c30> has joined #yocto | 16:08 | |
| *** starblue <starblue!~juergen@dslb-094-221-186-056.094.221.pools.vodafone-ip.de> has quit IRC (Ping timeout: 256 seconds) | 16:11 | |
| *** zpfvo <zpfvo!~fvo@i59F5CDBE.versanet.de> has quit IRC (Remote host closed the connection) | 16:11 | |
| *** amitk_ <amitk_!~amit@103.59.74.41> has quit IRC (Ping timeout: 248 seconds) | 16:22 | |
| *** frieder <frieder!~frieder@i577B9169.versanet.de> has quit IRC (Remote host closed the connection) | 16:23 | |
| *** ptsneves <ptsneves!~Thunderbi@84.47.155.82> has quit IRC (Ping timeout: 248 seconds) | 16:33 | |
| *** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Quit: Ex-Chat) | 16:36 | |
| *** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 255 seconds) | 16:38 | |
| *** tunahan <tunahan!~tunahan@78.188.72.174> has quit IRC (Quit: tunahan) | 16:45 | |
| *** tunahan <tunahan!~tunahan@78.188.72.174> has joined #yocto | 16:45 | |
| *** jtoomey <jtoomey!~jtoomey@149.199.80.130> has joined #yocto | 17:00 | |
| *** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto | 17:03 | |
| meego | Mmh can *.inc files be required from another layer? I'm trying to extend a raspberry machine, and have created a new machine definition that contains "require conf/machine/include/raspberrypi3-64.inc" but it fails | 17:03 |
| *** thomasd13 <thomasd13!~thomas@DSL01.212.114.255.148.ip-pool.NEFkom.net> has quit IRC (Ping timeout: 246 seconds) | 17:09 | |
| *** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat) | 17:10 | |
| *** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has joined #yocto | 17:11 | |
| *** amitk_ <amitk_!~amit@103.59.74.41> has joined #yocto | 17:26 | |
| *** tangofoxtrot <tangofoxtrot!~tangofoxt@user/tangofoxtrot> has quit IRC (Remote host closed the connection) | 17:27 | |
| *** tangofoxtrot <tangofoxtrot!~tangofoxt@user/tangofoxtrot> has joined #yocto | 17:29 | |
| *** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Quit: alessioigor) | 17:29 | |
| *** florian_kc <florian_kc!~florian@dynamic-093-131-085-167.93.131.pool.telefonica.de> has joined #yocto | 17:31 | |
| *** rfs613 <rfs613!~rfs613@rfs.netwinder.org> has quit IRC (Ping timeout: 250 seconds) | 17:31 | |
| jbo | meego, as I understood the way to do this is by creating a new layer and then overriding the machine config in there (so you don't have to include anything) | 17:34 |
| *** LocutusOfBorg <LocutusOfBorg!~locutusof@user/locutusofborg> has quit IRC (Quit: ZNC 1.8.2+deb3 - https://znc.in) | 17:37 | |
| meego | jbo: oooh i'll look into this thanks! | 17:38 |
| jbo | meego, https://docs.yoctoproject.org/dev/dev-manual/layers.html | 17:39 |
| *** Thorn <Thorn!~Thorn@user/thorn> has quit IRC (Ping timeout: 248 seconds) | 17:42 | |
| *** starblue <starblue!~juergen@67-130-142-46.pool.kielnet.net> has joined #yocto | 17:44 | |
| *** yssh <yssh!~yssh@223.178.151.157> has joined #yocto | 17:48 | |
| *** florian_kc <florian_kc!~florian@dynamic-093-131-085-167.93.131.pool.telefonica.de> has quit IRC (Ping timeout: 250 seconds) | 17:50 | |
| *** vladest <vladest!~Thunderbi@2a02:1210:760b:9500:ee8f:691a:1b42:69ac> has quit IRC (Ping timeout: 256 seconds) | 17:57 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed) | 18:05 | |
| *** seninha <seninha!~seninha@user/seninha> has quit IRC (Remote host closed the connection) | 18:14 | |
| *** yssh <yssh!~yssh@223.178.151.157> has quit IRC (Quit: Client closed) | 18:17 | |
| *** yssh <yssh!~yssh@2401:4900:5137:8498:3ac1:943:d3a7:1c42> has joined #yocto | 18:17 | |
| *** yssh <yssh!~yssh@2401:4900:5137:8498:3ac1:943:d3a7:1c42> has quit IRC (Client Quit) | 18:17 | |
| *** florian_kc <florian_kc!~florian@dynamic-093-131-085-167.93.131.pool.telefonica.de> has joined #yocto | 18:20 | |
| *** LocutusOfBorg <LocutusOfBorg!~locutusof@93-50-192-18.ip153.fastwebnet.it> has joined #yocto | 18:31 | |
| *** PobodysNerfect_ <PobodysNerfect_!~PobodysNe@84.214.105.47> has quit IRC (Quit: Gone to sleep. ZZZzzz…) | 18:45 | |
| *** Xagen <Xagen!~Xagen@4.14.206.69> has quit IRC (Ping timeout: 260 seconds) | 18:49 | |
| *** seninha <seninha!~seninha@user/seninha> has joined #yocto | 18:50 | |
| *** Thorn <Thorn!~Thorn@user/thorn> has joined #yocto | 18:52 | |
| *** florian_kc <florian_kc!~florian@dynamic-093-131-085-167.93.131.pool.telefonica.de> has quit IRC (Ping timeout: 276 seconds) | 18:54 | |
| *** PobodysNerfect <PobodysNerfect!~PobodysNe@84.214.105.47> has joined #yocto | 19:09 | |
| *** Thorn <Thorn!~Thorn@user/thorn> has quit IRC (Quit: We be chillin' - IceChat style) | 19:12 | |
| *** Thorn <Thorn!~Thorn@user/thorn> has joined #yocto | 19:21 | |
| *** ajfriesen <ajfriesen!~ajfriesen@p54b94d31.dip0.t-ipconnect.de> has quit IRC (Quit: The Lounge - https://thelounge.chat) | 19:24 | |
| *** bps <bps!~bps@80.71.142.18.ipv4.parknet.dk> has joined #yocto | 19:27 | |
| *** ajfriesen <ajfriesen!~ajfriesen@p54b94d31.dip0.t-ipconnect.de> has joined #yocto | 19:29 | |
| *** PobodysNerfect <PobodysNerfect!~PobodysNe@84.214.105.47> has quit IRC (Quit: Gone to sleep. ZZZzzz…) | 19:29 | |
| *** amitk_ <amitk_!~amit@103.59.74.41> has quit IRC (Remote host closed the connection) | 19:30 | |
| *** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has quit IRC (Quit: The Lounge - https://thelounge.chat) | 19:30 | |
| *** Wouter0100670440 <Wouter0100670440!~Wouter010@entry.nbg.netvos.nl> has joined #yocto | 19:31 | |
| *** starblue <starblue!~juergen@67-130-142-46.pool.kielnet.net> has quit IRC (Ping timeout: 250 seconds) | 20:00 | |
| *** florian_kc <florian_kc!~florian@dynamic-093-131-085-167.93.131.pool.telefonica.de> has joined #yocto | 20:02 | |
| *** meego <meego!~meego@2a01:e0a:e5:3260:2501:2d1:34ea:c30> has quit IRC (Quit: Leaving...) | 20:11 | |
| *** Haxxa <Haxxa!~Haxxa@202-65-68-206.ip4.superloop.au> has quit IRC (Quit: Haxxa flies away.) | 20:15 | |
| *** Haxxa <Haxxa!~Haxxa@202.65.68.206> has joined #yocto | 20:17 | |
| *** seninha <seninha!~seninha@user/seninha> has quit IRC (Remote host closed the connection) | 20:23 | |
| *** seninha <seninha!~seninha@user/seninha> has joined #yocto | 20:24 | |
| *** bps <bps!~bps@user/bps> has quit IRC (Ping timeout: 260 seconds) | 20:40 | |
| *** bps <bps!~bps@80.71.142.18.ipv4.parknet.dk> has joined #yocto | 20:47 | |
| *** starblue <starblue!~juergen@dslb-094-221-186-056.094.221.pools.vodafone-ip.de> has joined #yocto | 20:54 | |
| *** vladest <vladest!~Thunderbi@adsl-89-217-204-83.adslplus.ch> has joined #yocto | 20:54 | |
| *** car1t <car1t!~car1t@149.224.144.206.dynamic-pppoe.dt.ipv4.wtnet.de> has joined #yocto | 21:03 | |
| *** Minvera <Minvera!~Minvera@user/Minvera> has quit IRC (Read error: Connection reset by peer) | 21:04 | |
| *** tunahan <tunahan!~tunahan@78.188.72.174> has quit IRC (Quit: tunahan) | 21:15 | |
| *** tunahan <tunahan!~tunahan@78.188.72.174> has joined #yocto | 21:15 | |
| *** car1t <car1t!~car1t@149.224.144.206.dynamic-pppoe.dt.ipv4.wtnet.de> has quit IRC (Quit: leaving) | 21:27 | |
| *** Xagen <Xagen!~Xagen@99-135-179-142.lightspeed.austtx.sbcglobal.net> has joined #yocto | 21:30 | |
| *** dgriego <dgriego!~dgriego@user/dgriego> has quit IRC (Ping timeout: 250 seconds) | 21:44 | |
| *** seninha <seninha!~seninha@user/seninha> has quit IRC (Quit: Leaving) | 21:45 | |
| *** dgriego <dgriego!~dgriego@user/dgriego> has joined #yocto | 21:46 | |
| *** seninha <seninha!~seninha@user/seninha> has joined #yocto | 21:47 | |
| *** bps <bps!~bps@user/bps> has quit IRC (Ping timeout: 248 seconds) | 21:50 | |
| *** florian_kc <florian_kc!~florian@dynamic-093-131-085-167.93.131.pool.telefonica.de> has quit IRC (Ping timeout: 252 seconds) | 21:54 | |
| *** LocutusOfBorg <LocutusOfBorg!~locutusof@93-50-192-18.ip153.fastwebnet.it> has quit IRC (Quit: ZNC 1.8.2+deb3 - https://znc.in) | 22:02 | |
| *** Thorn <Thorn!~Thorn@user/thorn> has quit IRC (Ping timeout: 260 seconds) | 22:07 | |
| *** Dracos-Carazza <Dracos-Carazza!~Dracos-Ca@94.31.103.247> has quit IRC (Ping timeout: 246 seconds) | 22:11 | |
| *** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 248 seconds) | 22:19 | |
| *** nemik <nemik!~nemik@207.237.248.190> has joined #yocto | 22:24 | |
| *** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Quit: Leaving) | 22:25 | |
| *** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto | 22:40 | |
| *** florian_kc <florian_kc!~florian@dynamic-093-131-085-167.93.131.pool.telefonica.de> has joined #yocto | 22:44 | |
| *** seninha <seninha!~seninha@user/seninha> has quit IRC (Quit: Leaving) | 22:56 | |
| *** florian_kc <florian_kc!~florian@dynamic-093-131-085-167.93.131.pool.telefonica.de> has quit IRC (Ping timeout: 255 seconds) | 22:57 | |
| *** rfs613 <rfs613!~rfs613@rfs.netwinder.org> has joined #yocto | 23:11 | |
| *** seninha <seninha!~seninha@user/seninha> has joined #yocto | 23:22 | |
| *** sugarbeet <sugarbeet!~barbas@81.4.123.134> has quit IRC (Ping timeout: 255 seconds) | 23:46 | |
| *** sugarbeet <sugarbeet!~barbas@81.4.123.134> has joined #yocto | 23:56 | |
| *** Thorn <Thorn!~Thorn@user/thorn> has joined #yocto | 23:56 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!