Thursday, 2019-04-04

*** la_croix <la_croix!> has joined #yocto00:03
*** la_croix <la_croix!> has quit IRC00:07
*** la_croix <la_croix!> has joined #yocto00:16
*** JaMa <JaMa!> has joined #yocto00:30
*** georgem_home <georgem_home!uid210681@gateway/web/> has quit IRC00:46
*** georgem_home <georgem_home!uid210681@gateway/web/> has joined #yocto00:47
*** armpit <armpit!~armpit@> has joined #yocto00:56
*** chandana73 <chandana73!~ckalluri@> has quit IRC00:58
*** learningc <learningc!> has joined #yocto01:06
*** otavio <otavio!~otavio@debian/developer/otavio> has quit IRC01:08
*** chandana73 <chandana73!~ckalluri@> has joined #yocto01:37
*** armpit <armpit!~armpit@> has quit IRC01:42
*** armpit2 <armpit2!~armpit@> has joined #yocto01:42
*** chandana73 <chandana73!~ckalluri@> has quit IRC01:43
*** learningc <learningc!> has quit IRC01:43
*** learningc <learningc!> has joined #yocto01:44
*** learningc <learningc!> has quit IRC01:45
*** armpit2 <armpit2!~armpit@> has quit IRC01:49
*** akuster <akuster!~armpit@> has joined #yocto01:49
*** akuster <akuster!~armpit@> has quit IRC01:51
*** armpit2 <armpit2!~armpit@> has joined #yocto01:51
*** armpit2 is now known as armpit01:55
*** learningc <learningc!> has joined #yocto01:59
*** learningc <learningc!> has joined #yocto02:00
armpitzeddii, you here ?02:13
* armpit maybe I'll send an email02:14
*** dv_ <dv_!> has quit IRC02:20
yoctiNew news from stackoverflow: How can I use bitbake to set /etc/timestamp? <>02:21
*** dv_ <dv_!> has joined #yocto02:34
*** la_croix <la_croix!> has quit IRC02:45
*** la_croix <la_croix!> has joined #yocto02:49
*** runde <runde!sid228344@gateway/web/> has quit IRC03:10
*** runde <runde!sid228344@gateway/web/> has joined #yocto03:12
*** runde <runde!sid228344@gateway/web/> has quit IRC03:14
*** fatalhalt <fatalhalt!> has quit IRC03:15
*** la_croix <la_croix!> has quit IRC03:16
*** runde <runde!sid228344@gateway/web/> has joined #yocto03:17
*** runde <runde!sid228344@gateway/web/> has quit IRC03:19
*** runde <runde!sid228344@gateway/web/> has joined #yocto03:21
*** la_croix <la_croix!> has joined #yocto03:23
*** georgem_home <georgem_home!uid210681@gateway/web/> has quit IRC03:36
*** saraf <saraf!~a_saraf@> has joined #yocto04:09
*** armpit <armpit!~armpit@> has quit IRC04:18
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC04:46
*** sjolley_ <sjolley_!> has quit IRC05:20
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto05:27
*** RB2 <RB2!> has quit IRC05:33
*** RB2 <RB2!> has joined #yocto05:33
*** armpit <armpit!~armpit@> has joined #yocto05:45
*** agust <agust!> has joined #yocto06:06
*** frsc <frsc!> has joined #yocto06:27
*** tprrt <tprrt!~tprrt@> has joined #yocto06:36
*** xtron <xtron!~xtron@> has joined #yocto06:40
xtrondoes u-boot support modifying configuration through *.cfg file, like SRC_URI += 'file://example.cfg'  ?06:40
*** Bunio_FH <Bunio_FH!> has joined #yocto06:52
*** fl0v0 <fl0v0!~fvo@> has joined #yocto06:58
*** kroon <kroon!~jkroon@> has joined #yocto07:04
*** lusus <lusus!~lusus@> has joined #yocto07:17
*** gabrbedd <gabrbedd!> has quit IRC07:28
*** florian_kc is now known as florian07:29
*** rburton <rburton!> has joined #yocto07:30
*** Bunio_FH <Bunio_FH!> has joined #yocto07:30
*** yacar_ <yacar_!~yacar@> has joined #yocto07:33
*** zeddii <zeddii!> has quit IRC07:50
*** TobSnyder <TobSnyder!> has joined #yocto07:52
*** frsc <frsc!> has quit IRC07:56
*** frsc <frsc!> has joined #yocto08:10
*** la_croix <la_croix!> has quit IRC08:40
*** cvasilak <cvasilak!~cvasilak@2a02:587:8117:600:b835:f77f:5b42:2987> has joined #yocto08:47
*** la_croix <la_croix!> has joined #yocto08:48
*** jku <jku!> has joined #yocto08:50
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has joined #yocto08:54
*** varjag <varjag!> has joined #yocto09:11
*** yacar_ <yacar_!~yacar@> has quit IRC09:50
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto10:00
willie2Hello, I'm still trying to do stuff I don't understand :) thankful for any tips10:00
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has quit IRC10:04
*** saraf <saraf!~a_saraf@> has quit IRC10:09
jofrwillie2: Make a kernel- and u-boot recipes that pull in those repos, build them and they should provide virtual/kernel and virtual/bootloader (respectively) and then in your image or machine recipes, you should set those as your preferred provider for those packages (the "virtual" ones).11:04
jofrIt's actually quite likely that you could even bbappend to your existing u-boot and kernel recipes and just override the SRC11:05
jofr(SRC_URI and SRCREV)11:07
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto11:07
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC11:10
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto11:12
*** yacar_ <yacar_!~yacar@> has joined #yocto11:16
willie2jofr: thanks for your help, a implementation question, I'm I supposed to create a new u-boot? e.g recipes-bsp/u-boot/
*** armpit <armpit!~armpit@> has quit IRC11:30
kanavinmarka, g-ir-scanner should not be executed for native recipes at all, if it is, then it's a bug somewhere11:31
kanavinwhich recipe is having the issue?11:32
*** berton <berton!~berton@2804:14d:4081:890b:e2d5:5eff:fef1:7a1f> has joined #yocto11:35
*** yacar_ <yacar_!~yacar@> has joined #yocto11:36
RPpsrcode: sorry to bother you, the lttng ptest timeout is causing us a few other problems. Is there a way I could easily fix/workaround it?11:36
RPalimon: happen to be around? I'm guessing you're travelling?11:37
*** berton <berton!~berton@2804:14d:4081:890b:e2d5:5eff:fef1:7a1f> has quit IRC11:41
*** berton <berton!~berton@2804:14d:4081:890b:e2d5:5eff:fef1:7a1f> has joined #yocto11:42
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC11:44
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has joined #yocto11:45
*** bluelightning_ <bluelightning_!~paul@pdpc/supporter/professional/bluelightning> has quit IRC11:47
*** berton <berton!~berton@2804:14d:4081:890b:e2d5:5eff:fef1:7a1f> has quit IRC11:47
jofrwillie2: Probably not....11:55
jofrwillie2: First of all, you should never change anything in the upstream layers.11:55
jofrwillie2: I always create your own layer where you override stuff from upstream. Otherwise you're going to have a bad day at some point.11:56
willie2jofr: In my own layer ofcourse11:56
*** berton <berton!~berton@2804:14d:4081:890b:e2d5:5eff:fef1:7a1f> has joined #yocto11:57
jofrSo in your layer, you should be able to create a u-boot_<version-or-%>.bbappend and then override the SRC* veriables11:57
willie2jofr: Now it looks like this
jofrwillie2: You have a couple of .bb's.. Sure there aren't some upstream recipes that you coulds .bbappend to instead?12:01
jofrwillie2: That you you're re-using the upstream code instead of duplicating it in your own repositoriy/layer12:01
jofrwillie2: That way you're*12:01
jofrI can't type today!12:02
*** berton_ <berton_!~berton@2804:14d:4081:890b:e2d5:5eff:fef1:7a1f> has joined #yocto12:02
willie2jofr: Well the qt application is custom and the scripts to take care of it, but i can probably use the poky/meta-recipes-bsp/u-boot. Since i think they based their custom u-boot on it12:03
*** berton <berton!~berton@2804:14d:4081:890b:e2d5:5eff:fef1:7a1f> has quit IRC12:04
luneffhey guys! please help the stupid me :-) I want to get chromium on x11. I need X. Should asking for "xorg-server" and something like "xserver-nodm-init" suffice? DISTRO_FEATURES set12:04
luneffany packagegroup with reasonable defaults?12:06
*** cvasilak <cvasilak!~cvasilak@2a02:587:8117:600:b835:f77f:5b42:2987> has quit IRC12:09
jofrwillie2: Cool.12:12
jofrwillie2: Are you over in Malmköping?12:12
willie2jofr: :o12:13
*** jku <jku!> has quit IRC12:13
willie2jofr: I'm not but they guys I'm doing this for are. Do you know them?12:14
jofrwillie2: Don't think so...12:14
rburtonluneff: core-image-x11 is an example of a image that just boots X12:15
willie2jofr: Then how did you figure that out?12:15
jofrwillie2: I just Googled Tjeders. And since (for some reason) our company ISP is in Sweden it favors swedish results or something  :P12:15
luneffrburton, thanks! It lists x11-base , will try12:16
willie2jofr: Oh :) Well i work at Acte solutions!12:16
kanavinRP: I am looking into the timeouts just now, it seems as though ptest-runner is erroneously thinking the tests haven't printed anything for the default timeout of 5 minutes and killing them off, even though they are12:30
RPkanavin: hmm, a bug in ptest-runner then?12:31
RPkanavin: rburton and I think when a timeout happens, things are not getting killed properly so we have a patch testining on the AB now to see if that is part of the issue12:32
RPkanavin: I think your theory is worth following12:32
kanavinRP: possibly, I am in the 'staring at the code' phase now12:32
rburtonkanavin: that was my hunch this morning too but i was trying to stare at code whilst talking :)12:32
kanavinextra complication: the thing is written in C12:32
RPkanavin: fair enough. I suspect multiple issues in here12:32
RPkanavin: we do have alimon around who wrote/maintains it12:33
*** jku <jku!> has joined #yocto12:33
*** armpit <armpit!~armpit@> has joined #yocto12:35
*** armpit <armpit!~armpit@> has quit IRC12:41
*** armpit2 <armpit2!~armpit@> has joined #yocto12:41
*** berton_ <berton_!~berton@2804:14d:4081:890b:e2d5:5eff:fef1:7a1f> has quit IRC12:43
kanavinrburton, RP: it's a buffering issue in the pipe between ptest-runner and ptests12:47
rburtonyay kanavin12:47
rburtontldr: "c is hard"12:47
kanavinptest-runner receives the child's output in big buffered chunks, and timeouts if the buffer is slow to fill12:47
rburtonhow big is big?12:48
jofrwillie2: I see! I'm in Denmark (Hillerød) - but I'm Icelandic myself. Are you across the water in Göteborg? Or over in Stockholm?12:48
kanavinmy unix-fu is slightly rusty, I don't remember right away how to control that12:48
*** baldgeek <baldgeek!~dan@> has joined #yocto12:48
rburtonkanavin: oh the send buffer?12:49
*** flying_sausages <flying_sausages!> has joined #yocto12:51
kanavinno, the fd pair created via pipe2() and passed to the child12:52
RPkanavin: why would that buffer large amounts?12:52
kanavinRP: I have no idea, but run for instance openssh ptest directly, and then via 'ptest-runner openssh' and note the difference in how things get written to the terminal from the child tests12:53
kanavinRP: need to run to grab lunch!12:53
willie2jofr: cool! I'm from Stockholm :)12:54
rburtonmust be buffering heavily if ptest-runner can actually timeout waiting for output12:54
RPrburton, kanavin: what doesn't happen in this code is the pipes don't get cleared after something is killed?12:54
RPand are reused between ptests?12:54
*** fbre <fbre!91fdde45@gateway/web/freenode/ip.> has joined #yocto12:55
RPrburton: I think that means that stderr gets dumped only when something later writes to it again (such as the failing python3 ssl test)12:56
RPwhich would explain why its in the logs at the same place each time12:57
rburtonneed to flush it out when bailing12:57
RPrburton: I'm puzzled why poll wouldn't say reading is possible sooner though12:59
fbreHi, I have a kernel image which is built with yocto and I can boot it from SD card. Now I copied it from SD card to the flash of the eval board, and try to boot from SD card. That fails. Why? Do I need to compile a kernel image of another type? If yes, where can I read that in the yocto docs?13:00
rburtonRP: seems like a safe thing to do would be to ensure that the pipes are flushed when timing out, and stop re-using them13:01
RPrburton: right, just not sure we fully understand why this is breaking13:01
Croftonfbre, how does it fail?13:03
*** tprrt <tprrt!~tprrt@> has quit IRC13:08
*** tprrt_ <tprrt_!~tprrt@> has joined #yocto13:08
willie2jofr:  I made a u-boot-imx_2016.04.bbappend that just adds SRC_URI +="git://my/local/repo. It builds but it is still using the old source.13:09
RPrburton: I think the problem is its not flushing output streams13:13
jofrwillie2: You need to either use = to replace it, or do a SRC_URI_remove first13:14
RPdoesn't explain the timeout but would explain the logging13:16
RPrburton, kanavin: look sane?13:27
RPrburton: I know the second patch is yours, will fix that, just want to quickly test before a meeting13:28
rburtonRP: looks reasonable13:31
fbreCrofton: If the SD card is plugged, it boots although the jumper pins are set to "boot from SPI NOR flash" and not from SD card. But if the SD card is not plugged into the eval board, simply nothing happens. The serial console doesn't show anything.13:33
kanavinRP: it reads from two decscriptors there, but you flush only when reading from the second one?13:39
*** jrypkec <jrypkec!a5e126f6@gateway/web/freenode/ip.> has joined #yocto13:40
Croftonfbre, what is the borad?13:41
fbreah, I found out now my mistake is to put the file "Image" (about 26MB) at address 0x0 of the flash of the board. But I should rather put the u-boot image to address 0x0, which is just about 60KB. Then that first stage u-boot loader loads the second stage u-boot loader which is about 600KB and that loads "Image" (which is the Linux kernel) as third step.13:49
fbreSorry, I have to understand the boot mechanism at first.13:50
fbreMy next question is to found out how I must change the yocto configuration in a way that the first stage u-boot should load the second-stage u-boot from SPI NOR flash instead of SD card.13:52
fbreDo you know where I find that in the yocto files?13:52
*** armpit2 <armpit2!~armpit@> has quit IRC13:56
fbreI think, as I wrongly flashed the Linux kernel (file is called "Image"), it still boots with SD card plugged because booting from SD card is a fallback if booting from SPI NOR flash fails.13:58
u1106I set IMAGE_FEATURES = "tools-profile tools-debug" in my image recipe just to see what nice tools that would give me, but the manifest remains unchanged. (The setting is at least not completely ignored, if I also add "foo" I get the expected error with the list of supported features)14:06
*** justanotherboy <justanotherboy!> has joined #yocto14:06
fbreMy u-boot image has the string "sd" in the filename. So I guess it's has built for SD card. I wonder what the magic yocto config file is to change the target device type to SPI NOR flash.14:10
u1106fbre: I have not the slightest idea, because I have never built U-Boot in Yocto. But the first place I would search around is the environment of your recipe. You get it using "bitbake -e". If you search who sets the sd part you might find possible alternatives.14:14
kergothfbre: most likely you need to adjust your UBOOT_CONFIG or UBOOT_MACHINE. you should examine the machine .conf for your machine. (conf/machine/${MACHINE}.conf)14:15
fbrecool hints, thank you, guys! :-)14:16
RPkanavin: I need to explain that, basically I avoid it flushing stdout all the time, only when stderr is in action14:17
RPkanavin: stdout should be the common case14:17
RP(you'd hope)14:17
kanavinRP: I did my own testing, and only the stdout fd ever gets any input. Also flushing does not resolve the problem at all; it seems like we do read from the input buffer all that there is :(14:18
fbreu1106: I think you must write the following instead: EXTRA_IMAGE_FEATURES_append += " tools-profile"14:19
RPkanavin: see the python3 test log output on the autobuilder, there is problematic output there on stderr afaict14:20
RPkanavin: I'm flushing the output buffer, not the input one14:20
*** sjolley_ <sjolley_!> has joined #yocto14:20
*** yann <yann!> has joined #yocto14:20
kanavinRP: I am testing with just openssh for now, and what I am seeing doesn't make any sense :( I am flushing the output buffers as well, but the 'truncated output written in chunks' problem is still there, which means the problem is in the input buffer somehow14:21
fbreu1106: I put that in an extra file, say my.conf  and then build yocto with:   bitbake core-image-minimal --read=my.conf14:22
*** la_croix <la_croix!> has quit IRC14:23
RPkanavin: I think we're looking at different problems14:23
fbreu1106: but you can also put it in your conf/local.conf14:23
RPkanavin: is it just at the end of the tests?14:23
kanavinnope, in the middle of them too14:23
kanavin                        if (pfds[0].revents != 0) {14:25
kanavin                                while ((n = read(fds[0], buf, WAIT_CHILD_BUF_MAX_SIZE)) > 0)14:25
kanavin-                                       fwrite(buf, n, 1, fps[0]);14:25
kanavin+                                       fwrite(buf, n, 1, fps[0]); fwrite("hallo", 5 ,1 ,fps[0]); fflush(fps[0]);14:25
u1106fbre: hmm, I think _append is always written with a "=" not with a "+=". Not sure whether the "+" would harm. The manual says IMAGE_FEATURES belongs into the recipe, not into conf
kanavinand same for fps[1]14:25
*** peacememories <peacememories!> has joined #yocto14:25
RPrburton: your patch seems dangerous as I think it caused the runner to commit suicide :/14:26
RPrburton: loads of ptests not in the output and it didn't run for as long14:27
RPrburton: only took an hour instead of three14:27
*** la_croix <la_croix!> has joined #yocto14:28
fbreu1106: I'm pretty sure it's the way as I suggest to you. Because I also installed that package tools-profile14:28
u1106Ok, I'll try. Maybe the code has not read the manual ;)14:29
RPrburton: small flaw in the patch, how does group in he child make it to the parent? :)14:29
fbreu1106: at least that works for me ;)14:30
RPrburton: needs to be -child14:30
markaRP: rburton: the gobject-introspection issue was a transient issue related to the fact I was pulling my build forward14:31
fbreu1106: you can also do this magic in your local.conf file:    CORE_IMAGE_EXTRA_INSTALL_append ?= "perf procps"14:32
markaonce I started to dig, pulling some commits off and doing more builds caused it to no longer be reproducible14:32
fbreu1106: the names I use are just examples of packages. You can use your own packages instead.14:33
markaI tried to reproduce the transient issue, pulling off several hundred commits and stepping forward, doing builds as I go. Unfortunately no joy.14:33
*** prabhakarlad <prabhakarlad!~prabhakar@> has left #yocto14:35
markaat any rate, no need to make any adjustments to the use of the scanner cache for the -native builds. nothing to see here.14:35
u1106fbre: sure I can install packages I know of / come to my mind and I have several already. I was just curious what "tools-profile" would provide, I could not find the list of dependencies in the source so I just tried to build it. But that seemed to confirm my reading of the source that there is nothing...14:38
markathe only outcome is a reminder I need to do more fresh builds before digging into a build failure14:38
*** peacememories <peacememories!> has quit IRC14:39
*** kroon <kroon!~jkroon@> has quit IRC14:41
fbreu1106: "tools-profile" contains all the kernel debugging Gedöns like trace-cmd and perf and so on14:43
*** Striking7 <Striking7!> has quit IRC14:43
fbreu1106: for profiling of the Linux kernel, and tracing and stuff14:43
fbreu1106: I don't know a command to show the content of a package either14:44
*** chandana73 <chandana73!~ckalluri@> has joined #yocto14:45
*** prabhakarlad <prabhakarlad!~prabhakar@> has joined #yocto14:45
u1106fbre: oe-pkg-util does that, but an IMAGE_FEATURE is not a package14:46
u1106fbre: right that packagegroup I also saw in the source. But why doesn't it get built and installed here?14:47
*** gabrbedd <gabrbedd!> has joined #yocto14:48
fbreu1106: not with my suggested lines either?14:48
u1106fbre: haven't been able to try yet, I have a "more important" build running14:49
*** prabhakarlad <prabhakarlad!~prabhakar@> has quit IRC14:50
*** prabhakarlad <prabhakarlad!~prabhakar@> has joined #yocto14:51
*** berton <berton!~berton@> has joined #yocto14:55
*** dreyna <dreyna!> has joined #yocto15:03
u1106fbre: s/oe-pkg-util/oe-pkgdata-util/ (Just noted when working on higher priority item that bash completed a bit differently than what I had typed in irc)15:04
fbreu1106: I have here:   CORE_IMAGE_EXTRA_INSTALL_append ?= "opkg"            and EXTRA_IMAGE_FEATURES ?= "package-management"               and PACKAGE_CLASSES = "package_ipk"15:07
fbreu1106: just to have the opkg stuff available15:08
u1106fbre: Thanks for your help for now, I need to return to this later, need to get some merge done in the next 50 minutes...15:10
fbreyo, I'm also almost on my way home :) See yeah15:11
*** yacar_ <yacar_!~yacar@> has quit IRC15:11
*** fbre <fbre!91fdde45@gateway/web/freenode/ip.> has quit IRC15:15
*** klemen <klemen!~textual@> has joined #yocto15:23
*** sarge_ <sarge_!~serj@> has joined #yocto15:24
*** yacar_ <yacar_!~yacar@> has joined #yocto15:32
*** TobSnyder <TobSnyder!> has quit IRC15:33
*** jae1 <jae1!6cd5440e@gateway/web/freenode/ip.> has joined #yocto15:35
RPkanavin: I'm wondering if you broke python3 relocation :/15:43
RPkanavin: ( removed the create_wrapper ${D}${bindir}/python${PYTHON_MAJMIN}  PYTHONHOME='${prefix}'  TERMINFO_DIRS='${sysconfdir}/terminfo:/etc/terminfo:/usr/share/terminfo:/usr/share/misc/terminfo:/lib/terminfo'  PYTHONNOUSERSITE='1')15:43
RPjae1: I think we need to add that bit back to the python3 recipe, then update as we discussed on #1320815:44
kanavinRP: could well be. I didn't add many bits of the'old stuff'15:45
kanavinRP: on the other hand, I made progress with the ptest buffering issue15:45
RPkanavin: I'm curious what you found?15:45
RPrburton: btw, in triage you got the python ptest issues, I took strace and lttng15:46
xtronhow to perform 'if NOT env exists ${var}' in hush shell for u-boot15:46
kanavinI just tested this, and with the patch, the output is received as at happens15:46
kanavin*as it happens15:46
kanavin(patch is erroneous, it adds some debug stuff, only the 'stdbuf' chunk is important)15:47
RPkanavin: can we call setlinebuf() on the fd directly rather than need coreutils?15:49
RPkanavin: good find though!15:50
kanavinRP: I think we can't - we operate on file descriptors, and setlinebuf operates on FILE*15:51
kanavinI do wonder what magic stdbuf does though15:51
kanavinI might go and read its source code15:52
RPkanavin: I was just thinking that...15:53
RPkanavin: sounds like wrappers around setvbuf15:54
*** klemen <klemen!~textual@> has quit IRC15:54
RPkanavin: unless the intermediate process is now doing the buffering :/15:55
kanavinRP: yes, a LD_PRELOAD hack15:57
*** jae1 <jae1!6cd5440e@gateway/web/freenode/ip.> has quit IRC16:04
*** alcroito <alcroito!> has joined #yocto16:14
alcroitoHi, is this the right place to ask about bitbake?16:15
*** fl0v0 <fl0v0!~fvo@> has quit IRC16:16
*** jeanba <jeanba!~jbl@> has joined #yocto16:16
*** tprrt_ <tprrt_!~tprrt@> has quit IRC16:20
*** chandana73 <chandana73!~ckalluri@> has quit IRC16:21
alcroitook. I'm wondering if it's possible to create a recipe or bbappend file which would remove building a certain recipe, but still keeps building its dependencies?16:21
alcroitoSo if A depends on B, i want to write an A.bbappend which would stop A from building, but keeps building B16:21
alcroitoreplace A.bbappend with any mechanism that could achieve that16:22
yoctiNew news from stackoverflow: CMake could not find Perl <>16:23
kanavinalcroito, create a new recipe that would have exactly same list of dependencies as A16:23
kanavinwhat is the use case?16:24
*** Bunio_FH <Bunio_FH!> has quit IRC16:25
luneffhey guys! has anyone tried installing Google Chrome Market plugins into a Yocto build? I think integrating h264ify from the beginning is a good idea :-)16:28
*** yacar_ <yacar_!~yacar@> has quit IRC16:31
alcroitokanavin that works if you have one package, but if i have a whole tree of packages, copy pasting isn't feasible. The use case is to get an sdk with a sysroot with all dependencies, without the actual packages16:37
alcroitoto be more precise, i'm trying to get a sysroot of all dependencies of qt, without actually building qt16:37
*** florian <florian!~florian_k@Maemo/community/contributor/florian> has quit IRC16:38
*** jeanba <jeanba!~jbl@> has quit IRC16:38
rburtonalcroito: dare i ask why?16:49
alcroitorburton yes, i'm working on the cmake qt port (build qt with cmake), and i want a sysroot with qt dependencies16:49
rburton*sysroot* or sdk16:49
alcroitosysroot, but that's provided by the sdk16:49
rburtonwhy not just add qt to the sdk and ignore the fact that qt is in it?16:50
alcroitobecause adding a new dependency recipe or modifying an existing one forces rebuilding whole of qt, and that takes too long16:51
alcroitohence my desire to get rid of the qt building part16:51
rburtonfine, just copy the dependency list16:51
alcroitoLike i said, it's not entirely feasible if they are chosen dynamically from multiple recipes and bbapends16:52
rburtonbitbake qt -e |grep DEPENDS=16:52
rburtonthere's the list16:52
alcroitook, that's a step in the direction that I needed. but that's dependencies for only one qt package, i'd have to do it multiple times for each module16:54
alcroitoBut coming back to the original question, it is not possible to dynamically alter which recipes should NOT be built, and to also get the dependencies of those recipes?16:57
rburtoni guess you could use a bbappend to delete qt's do_compile do_configure do_install etc etc16:59
kanavinRP: even after fixing the buffering, 5 minutes timeout seems genuinely too short for some of tests in python3 and lttng-tools16:59
kanavinRP: I am now re-running them outside of ptest-runner to determine just how much time they need17:00
kanavinrburton: ^^^17:00
RPkanavin: are you sure some of these aren't hangs? tests taking longer than 5 mins seems bad :/17:02
kergothOT, but ha,
RPkanavin: I know the lttng issue has a fix upstream17:02
alcroitoi assume do_compile, etc are tasks. Would it be possible to remove the tasks from a single location for multiple recipes, instead of doing it in multiple bbappend files?17:03
kanavinalcroito, just wondering what CPU and how much RAM do you have?17:03
alcroitosome 4c / 8th intel cpu, 32g ram17:04
kanavinalcroito, you might find that getting a 32 core threadripper might be cheaper than the time you lose fighting with this, and then building stuff on a low-core machine17:04
alcroitoheh, perhaps.17:05
alcroitoBut I'm stubborn like that17:06
kanavinand rumours are, a 64 core one is coming this year17:06
JaMaeven with 64 cores, rebuilding qtwebengine takes about the same time as building world with oe-core :/17:08
RPkanavin: stdbuf is horrible :/17:09
kanavinRP: alternatively, we might just raise ptest-runner's timeout from five minutes17:09
*** chandana73 <chandana73!~ckalluri@> has joined #yocto17:10
RPkanavin: the buffers should flush at 4k max. I wonder if pipe size is being a factor here17:11
RPkanavin: I'll ponder while I go for food17:11
kanavinRP: openssh definitely is not a hang, it completes fine here with the stdbuf fix applied17:11
kanavinRP: running python3 now to see which of its tests take long and whether it genuinely hangs17:11
RPkanavin: I suspect lttng genuinely does hang fwiw, I suspect the others dont17:12
kanavinRP: right, then I won't run that. python3's httplib test does seem stuck, I'll probably head home then.17:13
*** jae1 <jae1!~jaewon@> has joined #yocto17:13
*** la_croix <la_croix!> has quit IRC17:21
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has quit IRC17:22
*** Bunio_FH <Bunio_FH!> has joined #yocto17:23
*** la_croix <la_croix!> has joined #yocto17:29
alcroitook a different question, is it possible to create a unified sysroot that can be sourced via the setup environment shell script, without creating an sdk?17:32
*** Bunio_FH <Bunio_FH!> has quit IRC17:32
kergoththat's basically the definition of an sdk already, just not zipped/tarred up17:37
alcroitoyes, but from what i've seen the paths in the "environment-setup-cortexa9hf-neon-poky-linux-gnueabi" bash script expect the sysroot to be installed in a specific location, so it doesn't seem relocatable17:40
kergothsdk installation runs relocation scripts which fix this17:40
alcroitowhich means it won't work without installation17:41
kergothif those scripts aren't run, the sysroot won't be usable, as even if you deal with library relocation (i.e. $ORIGIN in rpath) that won't fix relocation issues in scripts (sed replacement) or dynamic linker (
kergothno sysroot with binaries you want to *run* will work without relocation17:41
kergothsdk or not17:41
kergothif it's just libraries and headers, it's fine17:41
alcroitofor running, of course, but i'm only concerned with build17:41
kergothand you can change how the sdk is packaged17:41
kergoththen it's irrelevent17:41
kergothis your only concern the hardcoded paths in environment-setup?17:42
*** varjag <varjag!> has quit IRC17:42
kergoththat can be trivially worked around, if you can assume a certain amount of sanity in the user's shell17:42
alcroitoCould you elaborate?17:43
kergoththat does it17:43
kergoththere's no *standard* method to determine the path of the script being sourced17:44
kergothi.e. posix doesn't define it17:44
kergothbut bash and zsh have their own methods, and some other shells will set $0, though not all17:44
kergothhence the comment about user shell sanity17:44
kergoththat append just addresses it for bash and zsh, the most common ones17:44
alcroitoSo the script essentially determines the location of the current environment dir name, and uses sed to replace the hardcoded paths with the determined location?17:46
kergothi think a combination of this append and customizing how the sdk is packaged (set SDK_PACKAGING_FUNC) should address your issue17:46
kergothit determines the location of itself (environment-setup) and assumes that's the root of the sdk and substitutes it, yes17:46
alcroitook, i'll have to give it a go, thanks!17:47
kergothnp, good luck with it17:47
kergothi should probably submit that append upstream at some point17:47
kergothslightly less work for the relocation scripts17:47
*** frsc <frsc!> has quit IRC18:04
*** berton <berton!~berton@> has quit IRC18:11
*** berton <berton!~berton@> has joined #yocto18:12
*** sk_tandt <sk_tandt!> has joined #yocto18:17
*** nerdboy <nerdboy!~sarnold@gentoo/developer/nerdboy> has joined #yocto18:22
*** la_croix <la_croix!> has quit IRC18:24
*** T_UNIX <T_UNIX!uid218288@gateway/web/> has quit IRC18:24
*** la_croix <la_croix!> has joined #yocto18:29
*** WillMiles <WillMiles!> has joined #yocto18:35
*** kaspter <kaspter!~Instantbi@> has quit IRC18:52
*** kaspter <kaspter!~Instantbi@> has joined #yocto18:53
*** jku <jku!> has quit IRC18:55
*** luneff <luneff!~yury@> has quit IRC18:57
*** Bunio_FH <Bunio_FH!> has joined #yocto19:02
*** Bunio_FH <Bunio_FH!> has quit IRC19:04
*** tgraydon <tgraydon!~textual@> has joined #yocto19:06
*** Bunio_FH <Bunio_FH!> has joined #yocto19:07
psrcodeRP: quick question on how the autobuilder work, does it ssh into the system and run ptest etc or does it uses the a tty/console redirection? I'm asking because I'm having trouble running the ptest for lttng-tools via runqemu nographic (when a lot of output is happening fast) but no problem when sshing into the system an running the ptest that way. Might be a problem in ptest-runner ...19:09
psrcodeit is most probably a problem in ptest-runner since I can execute the test manually and everything works fine19:10
*** bluelightning <bluelightning!~paul@pdpc/supporter/professional/bluelightning> has joined #yocto19:11
*** luneff <luneff!~yury@> has joined #yocto19:11
*** la_croix <la_croix!> has quit IRC19:16
*** la_croix <la_croix!> has joined #yocto19:17
*** georgem <georgem!~georgem@> has quit IRC19:31
*** georgem_ <georgem_!~georgem@> has joined #yocto19:31
*** georgem_ is now known as georgem19:32
RPpsrcode: it runs it via ssh19:38
RPpsrcode: is it an emulation speed issue with the console in runqemu?19:39
*** rcw <rcw!~rcw@> has joined #yocto19:39
psrcodetbh i'm not sure, it's a musl build and I can't get gdb to run neither gdbserver...19:40
RPpsrcode: we're having a few problems with ptest-runner's i/o :/19:40
RPpsrcode: ah, there was a thread about this somewhere19:40
psrcodeI would assume no since I can run the same test fine manually19:40
RPpsrcode: we're wondering if pie is broken on musl19:41
*** BCMM <BCMM!~BCMM@unaffiliated/bcmm> has quit IRC19:46
RPpsrcode: I'd love to not have ptest hanging in lttng if you have any idea how to just fix that piece! :) (or point me at how to fix it)19:46
psrcodewell I was about to send you the patches but stumbled upon this...19:47
psrcodei'll do a last checkup with ptest under ssh19:47
psrcodeabout PIE/musl, i'll be a bit bitter, but it wouldn't be the first time musl is *broken*. sorry khem. We have a saying here at efficios: "musl the poor's man glibc"19:51
RPpsrcode: it does sometimes have some challenges... ;-)19:55
*** justanotherboy <justanotherboy!> has quit IRC20:03
*** justanotherboy <justanotherboy!~justanoth@> has joined #yocto20:04
*** chandana73 <chandana73!~ckalluri@> has quit IRC20:05
bluelightninganyone have anything to start off ?20:09
bluelightningRP: rburton: ^20:09
bluelightningkhem also ^20:09
RPbluelightning: ?20:10
RPbluelightning: planning to merge that20:10
bluelightningRP: ok, thanks20:10
* RP hopes nobody cares/notices20:10
bluelightningnaturally I will be doing my usual commit trawl but advance pointers/raw material is helpful :)20:10
RPbluelightning: gcc-cross-initial and glibc-initial removal20:11
RPagain, hopefully most don't notice/care20:11
bluelightningright, worth noting though20:11
RPchange to use perl-cross ?20:11
*** chandana73 <chandana73!~ckalluri@> has joined #yocto20:13
JaMaRP: gcc-cross-initial and glibc-initial removal was most noticible when restoring gcc-7 recipes for warrior, but even there it was easy to follow what gcc-8 recipes did20:13
RPJaMa: right, I don't think there was anything gcc8 specific in what we did. Should have done it years ago :/20:13
JaMabluelightning: please mention ARM tune changes, but with the ongoing discussion now on the ML I'm not sure what the summary should say20:14
bluelightningJaMa: ok, I've short-noted it for now and hopefully the dust will settle before the release and then we can document it properly20:16
bluelightningRP: hmm, does the perl-cross change have any possibly user-visible fallout?20:17
bluelightninginteresting... I'd missed that python 3.4 introduced enum support20:24
RPbluelightning: just that it changed the perl build a lot and there may be sideeffects from it20:28
RPJaMa, bluelightning: I have no plans to change the tunes for 2.720:29
*** tz <tz!> has quit IRC20:29
*** tz <tz!> has joined #yocto20:29
*** justanotherboy <justanotherboy!~justanoth@> has quit IRC20:42
*** rcw <rcw!~rcw@> has quit IRC20:42
RPkanavin: I think we might be able to just add -u to the sed command in the openssh ptest runner20:45
JaMaRP: understood, I was thinking about thumb enabled by default (so that people aren't surprised that TUNE_PKGARCHs are now different and binary feeds broken, but it's already from thud, not new in warrior, sorry for noise20:47
*** Bunio_FH <Bunio_FH!> has joined #yocto20:47
JaMaRP: and the new changes might be hard to describe in release notes as there isn't good agreement if the change was for better or worse and what the tunes actually should do20:48
RPJaMa: right, those patches are 2.8 discussion and I'm still not convinced its the right thing to do. I need to reply to that thread20:48
JaMa105 build jobs in queue, time to take a nap :)20:49
RPJaMa: 'night!20:49
*** JaMa <JaMa!> has quit IRC20:49
*** tgraydon <tgraydon!~textual@> has quit IRC20:55
*** justanotherboy <justanotherboy!> has joined #yocto21:00
*** luneff <luneff!~yury@> has quit IRC21:02
*** tgraydon <tgraydon!~textual@> has joined #yocto21:07
*** jrypkec <jrypkec!a5e126f6@gateway/web/freenode/ip.> has quit IRC21:12
*** armpit2 <armpit2!~armpit@> has joined #yocto21:14
*** berton <berton!~berton@> has quit IRC21:15
*** armpit2 is now known as armpit21:20
*** armpit <armpit!~armpit@> has quit IRC21:35
*** armpit2 <armpit2!~armpit@> has joined #yocto21:35
*** armpit2 is now known as armpit21:35
*** agust <agust!> has quit IRC21:38
*** WillMiles <WillMiles!> has quit IRC21:40
psrcodeRP: let me know how it goes:
RPpsrcode: was just reading those and about to queue some tests, thanks!21:52
RPpsrcode: just fired a build with those in...21:54
*** justanotherboy <justanotherboy!> has quit IRC22:17
*** rburton <rburton!> has quit IRC22:19
*** rburton <rburton!> has joined #yocto22:36
*** rburton <rburton!> has quit IRC22:51
*** georgem_home <georgem_home!uid210681@gateway/web/> has joined #yocto22:58
*** sk_tandt <sk_tandt!> has quit IRC23:42

Generated by 2.11.0 by Marius Gedminas - find it at!