| *** dv_ <dv_!~dv@62.178.50.190> has joined #yocto | 00:00 | |
| *** davisr <davisr!~davisr@cpe-184-58-235-7.wi.res.rr.com> has joined #yocto | 00:24 | |
| *** learningc <learningc!~pi@121.121.99.192> has quit IRC | 00:37 | |
| *** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC | 00:46 | |
| *** MiskaX <MiskaX!i23wnbbyc5@2001:2060:72::3> has joined #yocto | 00:56 | |
| *** learningc <learningc!~pi@121.121.99.192> has joined #yocto | 01:04 | |
| *** moto-timo <moto-timo!~ttorling@fsf/member/moto-timo> has quit IRC | 01:07 | |
| *** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC | 01:41 | |
| *** davisr <davisr!~davisr@cpe-184-58-235-7.wi.res.rr.com> has quit IRC | 01:53 | |
| *** Emantor <Emantor!~Emantor@magratgarlick.emantor.de> has quit IRC | 02:20 | |
| *** Emantor <Emantor!~Emantor@magratgarlick.emantor.de> has joined #yocto | 02:22 | |
| *** davisr <davisr!~davisr@cpe-184-58-235-7.wi.res.rr.com> has joined #yocto | 02:53 | |
| *** davisr <davisr!~davisr@cpe-184-58-235-7.wi.res.rr.com> has quit IRC | 02:58 | |
| *** dev1990 <dev1990!~dev@asx191.neoplus.adsl.tpnet.pl> has quit IRC | 03:14 | |
| *** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has quit IRC | 04:43 | |
| *** stacktrust <stacktrust!~stacktrus@cpe-104-162-194-186.nyc.res.rr.com> has quit IRC | 04:49 | |
| *** khem <khem!~khem@unaffiliated/khem> has quit IRC | 04:52 | |
| *** khem <khem!~khem@unaffiliated/khem> has joined #yocto | 04:55 | |
| *** stacktrust <stacktrust!~stacktrus@cpe-104-162-194-186.nyc.res.rr.com> has joined #yocto | 05:02 | |
| *** stacktrust <stacktrust!~stacktrus@cpe-104-162-194-186.nyc.res.rr.com> has quit IRC | 05:12 | |
| *** stacktrust <stacktrust!~stacktrus@cpe-104-162-194-186.nyc.res.rr.com> has joined #yocto | 05:18 | |
| *** mrc3 <mrc3!~mrc3@linaro/mrc3> has quit IRC | 05:29 | |
| *** mrc3 <mrc3!~mrc3@linaro/mrc3> has joined #yocto | 05:30 | |
| *** learningc <learningc!~pi@121.121.99.192> has quit IRC | 05:41 | |
| *** King_InuYasha <King_InuYasha!~King_InuY@fedora/ngompa> has quit IRC | 06:02 | |
| *** King_InuYasha <King_InuYasha!~King_InuY@fedora/ngompa> has joined #yocto | 06:02 | |
| *** kamel_b <kamel_b!~kamel@ec2-52-47-93-88.eu-west-3.compute.amazonaws.com> has quit IRC | 06:05 | |
| *** kamel_b <kamel_b!~kamel@ec2-52-47-93-88.eu-west-3.compute.amazonaws.com> has joined #yocto | 06:06 | |
| *** learningc <learningc!~pi@121.121.99.192> has joined #yocto | 06:06 | |
| *** stew-dw <stew-dw!~stew-dw@172.58.84.67> has quit IRC | 06:32 | |
| *** stew-dw <stew-dw!~stew-dw@172.58.84.67> has joined #yocto | 06:32 | |
| yocti | New news from stackoverflow: How to compile C++ file for Sama5d27-som1-ek kit <https://stackoverflow.com/questions/59692219/how-to-compile-c-file-for-sama5d27-som1-ek-kit> | 06:34 |
|---|---|---|
| *** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto | 08:08 | |
| *** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC | 08:52 | |
| *** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto | 09:44 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto | 10:12 | |
| *** guerinoni <guerinoni!~guerinoni@host89-129-dynamic.21-79-r.retail.telecomitalia.it> has joined #yocto | 10:51 | |
| *** dev1990 <dev1990!~dev@asx191.neoplus.adsl.tpnet.pl> has joined #yocto | 11:03 | |
| *** MeanEngi <MeanEngi!5fa87c99@95.168.124.153> has quit IRC | 11:14 | |
| RP | khem: https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/629 | 12:01 |
| RP | (glibc build) | 12:01 |
| *** kreyren[m] <kreyren[m]!~kreyrenm]@ip-86-49-115-152.net.upcbroadband.cz> has quit IRC | 12:21 | |
| *** kreyren[m] <kreyren[m]!~kreyrenm]@ip-86-49-115-152.net.upcbroadband.cz> has joined #yocto | 12:27 | |
| *** agust <agust!~agust@p508B64CC.dip0.t-ipconnect.de> has joined #yocto | 12:39 | |
| *** JaMa <JaMa!~martin@109.238.218.228> has joined #yocto | 12:42 | |
| *** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC | 13:12 | |
| *** MeanEngi <MeanEngi!5fa87c99@95.168.124.153> has joined #yocto | 13:23 | |
| MeanEngi | Hey peeps, | 13:23 |
| MeanEngi | are there some docs available on the major components of bitbake? | 13:24 |
| MeanEngi | Am currently trying to understand the relation between the bitbake server ans the ui_module/ | 13:24 |
| MeanEngi | It seems like when invoking bitbake the server gets spun in a new process with 3 pipe endpoints endpoints available as communication channels | 13:28 |
| RP | MeanEngi: Its not really documented unfortunately :( | 13:29 |
| MeanEngi | I'm trying to see if it's a correct mental model to observer the ui_module as the main actor feeding the server with all the info | 13:29 |
| RP | MeanEngi: I personally visualise it as the ui_module issues commands and then gets events back to tell it what happened | 13:29 |
| MeanEngi | Thanks :) | 13:30 |
| RP | MeanEngi: Its designed that the cooker/server does the actual work and the ui is what interacts with the user in some way, be it commandline, web interface or whatever | 13:30 |
| RP | MeanEngi: there is the challenge this all got retrofitted to an existing codebase so its not as clean as would be ideal | 13:31 |
| RP | MeanEngi: I do try and clean it up when I have time | 13:31 |
| MeanEngi | And what part is responsible for working with paths and locating .conf, .bb files etc? | 13:31 |
| RP | MeanEngi: the cooker/server | 13:31 |
| RP | MeanEngi: cookerdata.py specifically | 13:32 |
| MeanEngi | @rp: Thanks | 13:32 |
| MeanEngi | (hmm, still finding my way with IRC :p ) | 13:33 |
| RP | MeanEngi: you disappeared once before, before I could answer one of your questions! | 13:33 |
| MeanEngi | So it's safe enough to say that everything "Cooker" related relates to the activity on the server? | 13:34 |
| RP | MeanEngi: the cooker is effectively the server | 13:34 |
| RP | it reads commands from the controlling UI and then handles them, sending events back to say what happened | 13:35 |
| RP | multiple UIs can read the event stream | 13:35 |
| RP | only one can control | 13:35 |
| RP | MeanEngi: Do you have a goal in mind when looking at this out of interest? | 13:36 |
| MeanEngi | RP Just out of interest, am gathering some content for the presentation on FOSDEM about debugging recipes :) | 13:37 |
| RP | MeanEngi: fair enough, I'm just wondering if there is anything specific I can offer :) | 13:37 |
| RP | the tinfoil APIs are quite neat and underused | 13:37 |
| RP | (they let you start up a cooker and do things to it) | 13:37 |
| MeanEngi | What exactly are you referring to with "tinfoil API"? (feel free to refer to code) | 13:38 |
| RP | MeanEngi: you may wonder how devtool or recipetool work, they connect to a bitbake server using the tinfoil API | 13:39 |
| RP | oe-pkgdata-util may be a simpler example | 13:40 |
| RP | lib/bb/tinfoil.py | 13:40 |
| MeanEngi | And bitbake isn't using that API? | 13:42 |
| *** guerinoni <guerinoni!~guerinoni@host89-129-dynamic.21-79-r.retail.telecomitalia.it> has quit IRC | 13:42 | |
| MeanEngi | "bitbake" - the mode of operating with the server by using "bitbake ..." from the cli | 13:42 |
| RP | MeanEngi: correct | 13:43 |
| *** learningc <learningc!~pi@121.121.99.192> has quit IRC | 13:43 | |
| RP | MeanEngi: bitbake is too specialised for building recipes to be able to become other tools | 13:43 |
| RP | we created tinfoil to allow other tools to connect into and use the cooker | 13:44 |
| RP | MeanEngi: tinfoil and bitbake use the same command interfaces behind the scenes. The commands the server supports are in lib/bb/commands.py | 13:45 |
| MeanEngi | Just reading the docstring for Tinfoil. Is "Querying bitbake internals" something other than "communicating with the Cooker/server"? | 13:46 |
| RP | MeanEngi: no, same thing | 13:47 |
| MeanEngi | (this is just for my conceptual understanding, don't aim to nitpick on the wording :p ) | 13:47 |
| RP | MeanEngi: tinfoil is a wrapper so we can change bitbake internally and attempt to provide a consistent user API | 13:47 |
| MeanEngi | I guess at this level up abstraction (the one where we introduced the server and the ui_module) I'm not clear what you mean when you say bitbake :) | 13:48 |
| MeanEngi | *of abstraction | 13:48 |
| RP | MeanEngi: no, bitbake can mean several things | 13:48 |
| *** learningc <learningc!~pi@121.121.99.192> has joined #yocto | 13:51 | |
| MeanEngi | RP: Thanks. You also mentioned about the question I had a while back... The one about the starting point for the server to act on commands from the ui_module? | 13:55 |
| RP | MeanEngi: right, its runCommand and runAsyncCommand in command.py, called from server/process.py iirc | 13:56 |
| RP | ProcessServer::main() specificallly | 13:56 |
| MeanEngi | Right, think it was this line: https://github.com/openembedded/bitbake/blob/master/lib/bb/ui/knotty.py#L447 | 13:59 |
| *** ifan <ifan!d973313a@217-115-49-58.cust.bredband2.com> has quit IRC | 14:02 | |
| MeanEngi | Where the "<recipe>" from the cli invocation "<bitbake recipe>" gets passed to the cooker. | 14:03 |
| MeanEngi | Just looking at the https://github.com/openembedded/bitbake/blob/master/lib/bb/server/process.py#L331 (the runCommand in server/process.py) | 14:03 |
| MeanEngi | That still doesn't seem to be the server runtime but some data being sent through a channel to the server | 14:04 |
| MeanEngi | I guess I'd expect something where the server is either in a blocking in a socket read or a callback... | 14:05 |
| MeanEngi | It would than start the processing once it receives the command with something (from a different thread/process calls runCommand)? | 14:06 |
| MeanEngi | A side question :P . The server is a different thread or a process? I've noticed multiple threads after "setup_bitbake" is invoked but have noticed some parent/child pipe passing which does point to processes... | 14:09 |
| RP | MeanEngi: https://github.com/openembedded/bitbake/blob/master/lib/bb/server/process.py#L212 ProcessServer::main() as I said | 14:15 |
| RP | MeanEngi: yes, ProcessServer sets up its own process. In bitbake memres mode it can stay in memory | 14:16 |
| MeanEngi | RP: Thanks :+1: | 14:22 |
| *** goliath <goliath!~goliath@clnet-p04-043.ikbnet.co.at> has joined #yocto | 14:29 | |
| *** enen92 <enen92!~miguelbor@148.63.172.143> has joined #yocto | 15:04 | |
| enen92 | Hey all. Maybe someone can offer some tips. After building the yocto image, I want to create a simple webpage that lists all the used tools and respective licenses. Right now this is an external script that I manually run after the image is finished. I'd love to incorporate it somehow as a build step so it is kept in sync after each build. Any recommendation or similar implementation I could search for? | 15:07 |
| RP | enen92: postfuncs of the image do_image_complete task? | 15:07 |
| enen92 | Looks like exactly what I'm looking for. Do you know of anyway I can access the license folder from my script? | 15:09 |
| RP | enen92: pass in the variable name from the function? | 15:11 |
| enen92 | I need to read a bit about this. Thanks a lot for your help | 15:18 |
| *** enen92 <enen92!~miguelbor@148.63.172.143> has quit IRC | 15:35 | |
| *** tgamblin <tgamblin!~tgamblin@CPE64777de11593-CM64777de11590.cpe.net.cable.rogers.com> has joined #yocto | 15:51 | |
| khem | RP: it seems mips has issues | 15:57 |
| khem | so its mainly core-image-sato and sato-sdk | 16:05 |
| RP | khem: yes, so it would seem | 16:12 |
| RP | khem: doing my best to give you data at this point | 16:12 |
| JaMa | khem: did you resolve the eglfs issue somehow yesterday? I'm seeing the same now without x11 | 16:12 |
| khem | RP: I looked at them | 16:12 |
| khem | and I also see that qemumips/VGA patch that I sent could be in picture | 16:13 |
| RP | khem: I feel like I'm drowning in problems :( | 16:13 |
| RP | khem: I removed it from the rerun so it causes issues of its own | 16:13 |
| khem | JaMa: not yet, got busy in fires elsewhere :) | 16:13 |
| JaMa | khem: ok, I'll have a look, just didn't want to duplicate the work if you had a fix somewhere | 16:14 |
| khem | RP: yeah ok, my tests were with core-image-weston and systemd but I think I need core-image-sato${-sdk} with sysvinit | 16:14 |
| khem | JaMa: thanks, I will be happy, btw. QT5.14 worked well with musl on x86/qemu so its a good beginning | 16:15 |
| RP | khem: I think -sato{-sdk} with systemd is also unwell | 16:15 |
| khem | RP: core-image-sato-sdk dies in boot | 16:15 |
| RP | khem: but yes | 16:16 |
| RP | khem: right | 16:16 |
| khem | but core-image-sato reports x11 errors | 16:16 |
| khem | arent they using same init system | 16:16 |
| RP | khem: qemumips-alt is systemd, qemumips is sysvinit | 16:16 |
| JaMa | khem: I've rebased the musl patches in qtwebengine to apply in 5.14, when you have some spare build cycles, please trigger musl qtwebengine build as well | 16:16 |
| khem | ah | 16:16 |
| khem | JaMa: http://errors.yoctoproject.org/Errors/Build/96540/ | 16:17 |
| JaMa | khem: I've fixed this in master-next | 16:19 |
| khem | JaMa: cool all of them ? | 16:20 |
| *** guerinoni <guerinoni!~guerinoni@host89-129-dynamic.21-79-r.retail.telecomitalia.it> has joined #yocto | 16:20 | |
| JaMa | yes, all patches to apply, but haven't built them yet (not even with glibc) | 16:20 |
| JaMa | I've also applied your fuzz-patch fix for before 5.14 upgrade | 16:21 |
| khem | RP: I saw that archlinux enabled seccomp in file utility by default and I am sure other distros will follow soon and pseudo makes seccomp unhappy | 16:21 |
| khem | RP: I think this issue is going to get severe in future distros we need to fix pseudo | 16:21 |
| khem | JaMa: ok, and the other two packages ? | 16:22 |
| RP | khem: the tumbleweed autobuilders are disabled due to this | 16:23 |
| RP | khem: debian already tried this and then backed seccomp out, it breaks too much | 16:23 |
| khem | RP: arch did same but they have re-enabled it since they think the issues they hit are fixed | 16:23 |
| RP | khem: I agree finding a solution would be good but I have no idea who will work on it or when :( | 16:24 |
| RP | khem: we should perhaps have a bug for it? Maybe a wrapper around file adding the -S option is the best we can do for now? | 16:24 |
| khem | I straced it but its hard to strace when peudo is in between since we dont know which syscall is being trapped | 16:25 |
| RP | khem: I think the issue that that pseudo translates the syscalls to things normal file doesn't use/expect | 16:26 |
| khem | RP: I think the problem is that file allows fixes set of syscalls now, and pseudo munges them and seccomp does not like it | 16:26 |
| RP | khem: right | 16:26 |
| khem | either it replaces them or changes signatures I dont know | 16:26 |
| RP | khem: its that pseudo batches large groups together in its wrappers | 16:26 |
| JaMa | khem: wildwest and whiteboard? I don't know what these 2 are and the rrors are strange, are you saying that it's caused by Qt upgrade? | 16:27 |
| khem | JaMa:they are from meta-atmel but depend on qt5 | 16:27 |
| khem | RP: perhaps file -s is a good option for now I agree | 16:28 |
| RP | khem: we really need a way to detect when file on a system has secomp enabled. If we have that we could have sanity inject a wrapper | 16:29 |
| *** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC | 16:30 | |
| khem | hmm -s might not work since file under pseudo crashed on ordinary files too | 16:33 |
| RP | khem: -S, not -s | 16:33 |
| khem | yeah I see | 16:42 |
| khem | RP: so basically run something like `readelf -d HOSTTOOLS_DIR/file | grep libseccomp` or `ldd HOSTTOOLS_DIR/file | grep libseccomp` | 16:45 |
| *** pohly <pohly!~pohly@p5B05600C.dip0.t-ipconnect.de> has joined #yocto | 17:07 | |
| *** pohly <pohly!~pohly@p5B05600C.dip0.t-ipconnect.de> has quit IRC | 17:14 | |
| *** zeddii <zeddii!~zeddii@CPEe8de27b71faa-CM64777d5e8820.cpe.net.cable.rogers.com> has quit IRC | 17:18 | |
| RP | khem: fancy sorting a patch for the sanity code? :) | 17:29 |
| *** davisr <davisr!~davisr@cpe-184-58-235-7.wi.res.rr.com> has joined #yocto | 17:57 | |
| *** guerinoni <guerinoni!~guerinoni@host89-129-dynamic.21-79-r.retail.telecomitalia.it> has quit IRC | 18:32 | |
| *** comptroller <comptroller!~comptroll@47-213-227-146.paolcmtc01.res.dyn.suddenlink.net> has quit IRC | 18:54 | |
| *** zeddii <zeddii!~zeddii@CPEe8de27b71faa-CM64777d5e8820.cpe.net.cable.rogers.com> has joined #yocto | 18:57 | |
| *** comptroller <comptroller!~comptroll@47-213-227-146.paolcmtc01.res.dyn.suddenlink.net> has joined #yocto | 19:04 | |
| khem | RP: thinking about it dont know if I will get to do it soon enough | 19:06 |
| khem | RP: if glibc passes all tests without qemumips/vga patch then dont yet merge it | 19:06 |
| khem | I want to run glibc testsuites and see if all is ok | 19:07 |
| *** bcran <bcran!~bcran@muon.bluestop.org> has quit IRC | 19:16 | |
| *** bcran <bcran!~bcran@muon.bluestop.org> has joined #yocto | 19:16 | |
| *** florian <florian!~florian_k@Maemo/community/contributor/florian> has joined #yocto | 19:16 | |
| *** davisr_ <davisr_!~davisr@cpe-184-58-235-7.wi.res.rr.com> has joined #yocto | 19:18 | |
| *** rewitt1 <rewitt1!~rewitt@134.134.139.74> has joined #yocto | 19:19 | |
| *** dev1990_ <dev1990_!~dev@asx191.neoplus.adsl.tpnet.pl> has joined #yocto | 19:21 | |
| *** davisr <davisr!~davisr@cpe-184-58-235-7.wi.res.rr.com> has quit IRC | 19:21 | |
| *** rewitt <rewitt!rewitt@nat/intel/x-sgemhlollnwjxdtv> has quit IRC | 19:21 | |
| *** junland <junland!~junland@142.93.201.46> has quit IRC | 19:21 | |
| *** dev1990 <dev1990!~dev@asx191.neoplus.adsl.tpnet.pl> has quit IRC | 19:21 | |
| *** ecclescake <ecclescake!~tomeccles@78.40.148.171> has quit IRC | 19:24 | |
| *** ecclescake <ecclescake!~tomeccles@78.40.148.171> has joined #yocto | 19:24 | |
| *** kreyren[m] <kreyren[m]!~kreyrenm]@ip-86-49-115-152.net.upcbroadband.cz> has quit IRC | 19:24 | |
| khem | I have pushed refresh patch kraj/glibc-2.31 | 19:25 |
| *** kreyren[m] <kreyren[m]!~kreyrenm]@ip-86-49-115-152.net.upcbroadband.cz> has joined #yocto | 19:30 | |
| *** pohly <pohly!~pohly@p5B05600C.dip0.t-ipconnect.de> has joined #yocto | 20:11 | |
| *** pohly <pohly!~pohly@p5B05600C.dip0.t-ipconnect.de> has quit IRC | 20:27 | |
| *** juvenal_ <juvenal_!~juvenal@187.19.15.34> has joined #yocto | 20:54 | |
| *** juvenal_ <juvenal_!~juvenal@187.19.15.34> has quit IRC | 21:26 | |
| *** juvenal_ <juvenal_!~juvenal@187.19.15.34> has joined #yocto | 21:33 | |
| *** juvenal_ <juvenal_!~juvenal@187.19.15.34> has quit IRC | 21:45 | |
| *** agust <agust!~agust@p508B64CC.dip0.t-ipconnect.de> has quit IRC | 22:15 | |
| *** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC | 22:55 | |
| *** JaMa <JaMa!~martin@109.238.218.228> has quit IRC | 23:40 | |
| RP | khem: so you want me to run another test run? we do run the test suites on the AB iirc | 23:43 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!