Wednesday, 2022-08-10

*** 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 #yocto00:35
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.)01:16
*** RobertBerger <RobertBerger!~rber|res@88-117-83-121.adsl.highway.telekom.at> has joined #yocto01:32
*** rber|res <rber|res!~rber|res@88-117-83-121.adsl.highway.telekom.at> has quit IRC (Ping timeout: 268 seconds)01:34
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Remote host closed the connection)01:36
*** otavio_ <otavio_!~otavio@200.102.164.25> has quit IRC (Remote host closed the connection)01:38
*** starblue <starblue!~juergen@dslb-094-221-182-149.094.221.pools.vodafone-ip.de> has quit IRC (Ping timeout: 268 seconds)01:39
*** starblue <starblue!~juergen@dslb-094-220-109-120.094.220.pools.vodafone-ip.de> has joined #yocto01:41
*** otavio <otavio!~otavio@200.102.164.25> has joined #yocto01:42
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto02:21
*** jmiehe1 <jmiehe1!~Thunderbi@user/jmiehe> has joined #yocto03:18
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Ping timeout: 268 seconds)03:20
*** jmiehe1 is now known as jmiehe03:20
*** Patrick60 <Patrick60!~Patrick@p200300efdf1ac600069226fffe49341c.dip0.t-ipconnect.de> has joined #yocto03:53
*** amitk <amitk!~amit@103.208.69.36> has joined #yocto04:06
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.)04:24
*** thomasd13 <thomasd13!~thomasd13@DSL01.212.114.255.148.ip-pool.NEFkom.net> has joined #yocto05:41
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 268 seconds)05:59
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto05:59
*** GNUmoon2 <GNUmoon2!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection)06:03
*** GNUmoon2 <GNUmoon2!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto06:04
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 268 seconds)06:04
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto06:04
*** Adrian_ <Adrian_!~e@dynamic-002-243-003-109.2.243.pool.telefonica.de> has joined #yocto06:05
wyrehi guys, I've got this append https://bpa.st/62BQ for the kernel recipe I need to provide to the machine I'm building my image for but my question is ... how may I control if the 0002-modify-crit-temp.patch is included in the image or not? I'd like just to include this patch for a dev image, not the production one.06:17
wyreI mean ... the problem is though I make a custom machine ... I will need also to use the linux-engicam kernel06:18
wyreshould I copy the entire linux-engicam recipe into a whole custom recipe for the kernel called in another way?06:19
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Ping timeout: 268 seconds)06:21
wyrethe point is I'd like to include the patch depending on the image, nor the machine, because if I create a different machine both will use the very same source code for the kernel, but not the patches.06:22
*** wkawka <wkawka!~wkawka@84-10-27-202.static.chello.pl> has joined #yocto06:38
*** ecdhe <ecdhe!~ecdhe@user/ecdhe> has quit IRC (Read error: Connection reset by peer)06:39
*** ecdhe <ecdhe!~ecdhe@user/ecdhe> has joined #yocto06:40
*** sanderz <sanderz!~sanderz@144.132.213.32> has joined #yocto06:50
sanderzI'm trying to build a vendor kernel supplied as part of a buildroot set of files. I put the kernel directory into my own git repo and then updated the vendor's kernel recipe to pull that down (instead of the original vendor kernel). I keep getting a few '| fatal: not a git repository (or any of the parent directories): .git' errors - I am probably06:54
sanderzdoing something incredible naive but if anyone could point to how I could debug this that would be appreciated.06:54
*** mvlad <mvlad!~mvlad@2a02:2f08:4a10:7900:24d7:51ff:fed6:906d> has joined #yocto06:55
sanderzTo be clear, that error occurs during the 'do_compile' stage, around here:06:56
sanderz|   GEN     Makefile06:56
sanderz|   CALL    /home/david/rockchip-platform/Yocto/build-squeezy-rider-rv1126/tmp/work-shared/rockchip-rk3588-evb/kernel-source/scripts/atomic/check-atomics.sh06:56
sanderz|   CALL    /home/david/rockchip-platform/Yocto/build-squeezy-rider-rv1126/tmp/work-shared/rockchip-rk3588-evb/kernel-source/scripts/checksyscalls.sh06:56
sanderz|   CHK     include/generated/compile.h06:56
sanderz| fatal: not a git repository (or any of the parent directories): .git06:56
sanderz|   GEN     .version06:56
sanderz|   CHK     include/generated/compile.h06:56
sanderz|   LD      vmlinux.o06:56
*** zpfvo <zpfvo!~fvo@i59F5CFC9.versanet.de> has joined #yocto06:58
*** frieder <frieder!~frieder@200116b8241433810000000000002000.dip.versatel-1u1.de> has joined #yocto06:58
wkawkaHi, what exit code 137 means in do_package_write_rpm taks?07:01
*** ptsneves <ptsneves!~Thunderbi@031011128120.dynamic-3-poz-k-0-2-0.vectranet.pl> has joined #yocto07:12
*** GillesM <GillesM!~gilles@129.179.5.84.rev.sfr.net> has joined #yocto07:22
*** Patrick60 <Patrick60!~Patrick@p200300efdf1ac600069226fffe49341c.dip0.t-ipconnect.de> has quit IRC (Quit: Client closed)07:24
*** dev1990 <dev1990!~dev@159-205-91-89.adsl.inetia.pl> has joined #yocto07:25
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has joined #yocto07:25
*** alessioigor <alessioigor!~alessioig@185.178.95.254> has quit IRC (Client Quit)07:26
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto07:35
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto07:43
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 252 seconds)07:44
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto07:44
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 268 seconds)07:49
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto07:49
*** kanavin <kanavin!~Alexander@2a02:2454:29b:3b00:d35d:e3cf:58b5:748b> has quit IRC (Quit: Leaving)07:50
*** florian <florian!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto07:51
*** kanavin <kanavin!~Alexander@2a02:2454:29b:3b00:d35d:e3cf:58b5:748b> has joined #yocto07:55
qschulzwyre: proper way is to have either a development distribution or a development machine07:57
qschulzwyre: other options are to have two device trees and have the bootloader pick the correct one before booting Linux (or use a device tree overlay)07:58
qschulzor to modify the device tree directly from the image recipe in the rootfs directly07:58
qschulzbut you very likely want a distribution because the "I only want this for the development image" scope will grow over time and there'll be a point where doing anything without a different distribution will be a LOT of pain, maybe even near impossible to do07:59
*** ardo <ardo!~ardo@host-188-10-58-99.business.telecomitalia.it> has quit IRC (Read error: Connection reset by peer)07:59
*** ardo <ardo!~ardo@host-188-10-58-99.business.telecomitalia.it> has joined #yocto08:00
qschulzsanderz: Hehehe, this very much seems like a bad vendor kernel you got there08:00
qschulzyou probably have some git commands in the kernel Makefile08:00
qschulzI had this once with Amlogic kernels running some git command on build08:01
*** ardo <ardo!~ardo@host-188-10-58-99.business.telecomitalia.it> has quit IRC (Read error: Connection reset by peer)08:04
sanderzqschulz Yeah this is between two Rockchip kernels and your comment confirms my suspicions.08:06
*** ardo <ardo!~ardo@host-188-10-58-99.business.telecomitalia.it> has joined #yocto08:06
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)08:08
sanderzqschulz Thank you.08:11
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto08:11
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has joined #yocto08:13
*** dev1990 <dev1990!~dev@159-205-91-89.adsl.inetia.pl> has quit IRC (Quit: Konversation terminated!)08:28
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 268 seconds)08:29
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto08:29
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has quit IRC (Ping timeout: 255 seconds)08:33
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 268 seconds)08:34
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto08:34
*** xmn <xmn!~xmn@cpe-72-225-198-203.nyc.res.rr.com> has joined #yocto08:35
*** ptsneves <ptsneves!~Thunderbi@031011128120.dynamic-3-poz-k-0-2-0.vectranet.pl> has quit IRC (Ping timeout: 252 seconds)08:37
*** sanderz <sanderz!~sanderz@144.132.213.32> has quit IRC (Ping timeout: 252 seconds)09:07
*** ptsneves <ptsneves!~Thunderbi@85-128-83-172.static.ip.netia.com.pl> has joined #yocto09:08
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)09:13
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto09:30
*** Adrian_ <Adrian_!~e@dynamic-002-243-003-109.2.243.pool.telefonica.de> has quit IRC (Ping timeout: 268 seconds)09:30
*** argonautx <argonautx!~argonautx@muedsl-82-207-240-114.citykom.de> has joined #yocto09:36
*** GillesM <GillesM!~gilles@129.179.5.84.rev.sfr.net> has quit IRC (Quit: Leaving)09:51
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 252 seconds)09:59
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto09:59
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 252 seconds)10:03
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto10:04
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 244 seconds)10:09
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto10:09
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 255 seconds)10:13
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto10:14
*** starblue <starblue!~juergen@dslb-094-220-109-120.094.220.pools.vodafone-ip.de> has quit IRC (Ping timeout: 268 seconds)10:15
*** starblue <starblue!~juergen@dslb-094-220-109-120.094.220.pools.vodafone-ip.de> has joined #yocto10:17
*** ptsneves <ptsneves!~Thunderbi@85-128-83-172.static.ip.netia.com.pl> has quit IRC (Quit: ptsneves)10:22
*** ptsneves <ptsneves!~Thunderbi@85-128-83-172.static.ip.netia.com.pl> has joined #yocto10:23
T_UNIX[m]hi10:30
T_UNIX[m]is there some kind of filter/whatever to tell bitbake to retry if the build failed tue to segfault or some compiler error?10:31
LetoThe2ndyo dudX10:33
LetoThe2ndT_UNIX[m]: in the hope that.... the build magically works the second time? (hint: the answer is "no")10:33
*** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:af5f:ab68:d10d:ff32> has quit IRC (Quit: vladest)10:33
*** vladest <vladest!~Thunderbi@2001:1715:9d9c:c530:c2e4:4196:316:34dc> has joined #yocto10:35
T_UNIX[m]LetoThe2nd: I guess it depends on the error. I'm talking about insufficcient resources and insufficient handling, that leads to SEGV or an internal compiler error. This depends on the amount of resources available at a single point. Now usually I'm using x tasks in parallel. Depending on just which these tasks are, that are executed in parallel the available memory is not enough.10:37
LetoThe2ndT_UNIX[m]: you are shortcutting a number of things here. first and foremost, bitbake doesn't know *why* a build fails. the executable returns a non-null state, and thats it. second, if your setup suffers such "transient" errors, then the key is to fix the setup - not introduce band aids that essentially go like "try as often as you want until you get a lucky punch"10:39
*** ptsneves <ptsneves!~Thunderbi@85-128-83-172.static.ip.netia.com.pl> has quit IRC (Read error: Connection reset by peer)10:45
*** ptsneves1 <ptsneves1!~Thunderbi@85-128-83-172.static.ip.netia.com.pl> has joined #yocto10:45
T_UNIX[m]<LetoThe2nd> "T_UNIX: you are shortcutting a..." <- Sure, understood. This would just be a lazy workaround, for my travel machine. Bitbake does not know about this kind of error OTB. But, if I can read these errors from the log, so could a filter tool.10:45
*** ptsneves1 is now known as ptsneves10:47
LetoThe2ndT_UNIX[m]: if at all, then it would rather make sense to find some means of adjusting parallelisation/resource usage.10:48
*** seninha <seninha!~seninha@user/seninha> has joined #yocto10:57
*** ptsneves1 <ptsneves1!~Thunderbi@85-128-83-172.static.ip.netia.com.pl> has joined #yocto11:14
*** ptsneves <ptsneves!~Thunderbi@85-128-83-172.static.ip.netia.com.pl> has quit IRC (Ping timeout: 252 seconds)11:14
*** davidinux <davidinux!~davidinux@81.22.36.108> has quit IRC (Ping timeout: 268 seconds)11:15
*** ptsneves1 <ptsneves1!~Thunderbi@85-128-83-172.static.ip.netia.com.pl> has quit IRC (Read error: Connection reset by peer)11:15
*** ptsneves <ptsneves!~Thunderbi@85-128-83-172.static.ip.netia.com.pl> has joined #yocto11:15
*** davidinux <davidinux!~davidinux@net-130-25-196-102.cust.vodafonedsl.it> has joined #yocto11:16
*** ptsneves <ptsneves!~Thunderbi@85-128-83-172.static.ip.netia.com.pl> has quit IRC (Read error: Connection reset by peer)11:17
*** ptsneves1 <ptsneves1!~Thunderbi@85-128-83-172.static.ip.netia.com.pl> has joined #yocto11:17
*** ptsneves1 <ptsneves1!~Thunderbi@85-128-83-172.static.ip.netia.com.pl> has quit IRC (Client Quit)11:18
*** ptsneves <ptsneves!~Thunderbi@85-128-83-172.static.ip.netia.com.pl> has joined #yocto11:20
T_UNIX[m]<LetoThe2nd> "T_UNIX: if at all, then it would..." <- that would be the "more right" thing to do, I assume.11:28
*** davidinux <davidinux!~davidinux@net-130-25-196-102.cust.vodafonedsl.it> has quit IRC (Ping timeout: 268 seconds)11:32
*** davidinux <davidinux!~davidinux@92.118.62.166> has joined #yocto11:32
vmesonT_UNIX[m]: could try using the /proc/pressure limits we added in master recently and let me know if that helps? BB_PRESSURE_MAX_CPU = "500" in your local.conf?11:35
LetoThe2ndvmeson: https://youtu.be/ISveIzgq_kQ11:37
wyreqschulz, sure, my point is not as how to handle different kernels as how to handle different kernel patches11:38
wyreI mean ... the kernel is the same and currently I'm using a bbappend recipe11:38
vmesonLetoThe2nd: bitbake's theme song!11:38
wyrebut not sure if I should just create a different kernel recipe in the machine dev case, for example11:38
LetoThe2ndvmeson: +111:38
*** Adrian_ <Adrian_!~e@dynamic-002-243-003-109.2.243.pool.telefonica.de> has joined #yocto11:44
jclsn[m]I have an issue where SRC_URI:append = "git://git@some.gitlab.repo.git" doesn't get appended. How to debug this? I have tried -D, but that kind of overwhelmed me11:48
jclsn[m]Well SRC_URI:append = " git:/..."11:49
jclsn[m]Didn't forget the space11:49
LetoThe2ndjclsn[m]: usual first try: bitbake-getvar11:50
jclsn[m]Everything else gets appended, just not the Gitlab link11:50
jclsn[m]Yeah I did11:50
jclsn[m]It says it gets appended, but doesn't land in the final string11:50
qschulzwyre: the source code is not the same if you need a patch in one case and not the other11:52
LetoThe2ndjclsn[m]: what happens if you place something else at the very same instance of appending.11:52
* jclsn[m] sent a code block: https://libera.ems.host/_matrix/media/r0/download/libera.chat/27d42c94c60caca98eeb6751bdb3f3ff2a13246711:52
qschulzwyre: you also don't need a different recipe if you use two machines11:52
qschulzyou can just add SRC_URI:append:machine2 = " file://machine2.patch" to your kernel recipe then11:53
jclsn[m]What is in question is the ${CST_CERTS}, which contains the Gitlab link11:53
wyreqschulz, well, but I need to patch the very same source code in both cases11:53
LetoThe2ndjclsn[m]: AIUI the externalsrce effectively kills everything else.11:53
jclsn[m]LetoThe2nd: Why? Can you link a doc entry?11:55
jclsn[m]Currently studying the bitbake docu again anyway11:56
LetoThe2ndjclsn[m]: i cannot, thats just my guess/impression. what happens if you disable that?11:56
jclsn[m]LetoThe2nd: It is not part of my append file, so I guess in the original imx-boot recipe11:57
jclsn[m]Let me see11:57
LetoThe2ndjclsn[m]: in your workspace, that suggest you did something with devtool11:57
jclsn[m]Ah let me reset11:58
T_UNIX[m]<vmeson> "T_UNIX: could try using the /..." <- I assume the bottleneck is the available memory. But thanks for pointing this out.11:59
qschulzT_UNIX[m]: BB_PRESSURE_MAX_MEMORY then12:01
qschulzT_UNIX[m]: you can also limit the number of threads used by Bitbake12:01
wyreqschulz, so you mean I may add SRC_URI:append:machineX in the linux-engicam_%.bbappend recipe and then create two separate machine conf files containing essentially the same but being named differently?12:01
qschulzwyre: that, or a new distro conf file but yes12:02
T_UNIX[m]<qschulz> "T_UNIX: BB_PRESSURE_MAX_MEMORY..." <- when was this introduced? I cannot find any docs on it. I assume it's dynamically generated?12:16
perdmannHi, is there any simple way to save the kernel error before my device gets a reset? Some kind of "Errormemory" I have disabled persistent logs to prevent SDcard damage12:18
qschulzT_UNIX[m]: docs patches are pending, added very recently to amster12:21
qschulzT_UNIX[m]: https://lists.yoctoproject.org/g/docs/message/311212:21
T_UNIX[m]good to know, thanks. I'm using `kirkstone`, so that'll have to wait 🙂12:22
*** brazuca <brazuca!~brazuca@2804:7f4:3590:6971:f0df:4ebf:3f81:5374> has joined #yocto12:23
jclsn[m]LetoThe2nd: Ah now it is there. Thx12:35
LetoThe2ndjclsn[m]: have fun!12:41
*** brazuca <brazuca!~brazuca@2804:7f4:3590:6971:f0df:4ebf:3f81:5374> has quit IRC (Quit: Client closed)12:43
wyreqschulz, not sure why I'm having these messages https://bpa.st/2Z3Q when I've got the files in the folder https://bpa.st/J4JA12:43
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 255 seconds)12:44
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto12:44
vmesonT_UNIX[m]:  kirkstone, oh well. By limiting CPU pressure, we've found that memory usage and pressure is also reduced.12:44
qschulzwyre: add imx6ull-joifigea to your MACHINE_OVERRIDES in your new machine configuration file otherwise it's going to be a pain12:45
wyreqschulz, I've done finally a different distro instead a different machine12:46
wyrehttps://bpa.st/TIVA12:46
wyrethat's the kernel bbappend recipe12:46
qschulz(or the original name of the machine conf file)12:47
wyreqschulz, as I've said I didn't a different machine conf file but a different distro conf file12:48
qschulzwyre: FILESEXTRAPATHS_prepend => FILESEXTRAPATHS:prepend12:48
qschulzI see you're using dunfell so that shouldn't be the issue12:48
qschulzbut still, try to not mix override syntax in the same recipe12:49
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 255 seconds)12:49
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto12:49
wyreqschulz, so I should use SRC_URI_append_joifi-dev = " ...12:49
wyreright?12:49
qschulzwyre: SRC_URI:append:joifi-dev = "" => you need a leading space here12:49
qschulzwyre: I would HIGHLY recommend using the new syntax now, so SRC_URI:append:joifi-dev12:49
qschulzwyre: KERNEL_DEVICETREE_append => KERNEL_DEVICETREE:append12:50
wyreqschulz, https://bpa.st/TJAQ12:50
wyreI think I got you 😉12:50
wyreI think it was because of the leading space12:51
wyreso it was looking ro a file called ....pathfile12:51
qschulzwyre: yup it was the missing leading space12:51
wyresorry <name>.patchfile12:51
qschulzyup12:52
*** GNUmoon2 <GNUmoon2!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection)12:53
*** GNUmoon2 <GNUmoon2!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto12:53
wyrenice, qschulz thank you 😊 but ... still not sure about what's causing a problem I've been having since some time ... I have to rerun bitbake to get it working, because the first time it's not able to patch the dts ... 😞 https://bpa.st/JCSA13:09
wyrenot sure if I have to redo the patch ... 🤔 because I can read "Patch needs to be refreshed."13:10
qschulzwyre: re-running bitbake shouldn't fix the issue so I'm surprised13:12
qschulzyou should probably rebase your patch on the proper kernel version13:12
qschulzI would suggest to remove the SRC_URI:append:whatever temporarily and then use devtool modify virtual/kernel to modify the sources, then create the patch and replace the one you have in your layer13:13
qschulz(don't forget to devtool reset when finished)13:13
*** brazuca <brazuca!~brazuca@2804:7f4:3590:6971:8c94:68da:503b:9e7f> has joined #yocto13:14
* RP has an interesting bitbake patch for class scope issues. I suddenly realised how we could implement it13:37
*** marc1 <marc1!~marc@ipagstaticip-ad9375f2-382c-b511-8ac1-9541f69fe50f.sdsl.bell.ca> has joined #yocto13:44
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto13:50
qschulzRP: could some class actually belong to both recipe and global scopes? would such a thing make sense?13:51
JPEWRP: Ah, that's actually quite simple13:52
JPEWqschulz: I believe that would just be a "global" class?13:52
RPJPEW: hopefully simple but effective13:53
qschulzRP: oof to the docs changes though :p13:54
RPqschulz: an opportunity to clarify the scope of classes ;-)13:54
qschulzJPEW: I don't think it's a good idea to have a class that can be both inherit in the global and recipe scope to be in classes-global13:54
qschulzthat would be a bit confusing (at least it is to me, but that might be the 4h of sleep talking right now)13:55
qschulzRP: yup!13:55
JPEWqschulz: No.... I meant I don't know why you have a class that did that. It seems like that's just a "global" class and there would be no reason include it in a recipe also13:55
RPqschulz: you couldn't put it in classes-global and have it work in recipe scope13:55
JPEW(but I might be misunderstanding some use case also)13:56
RPJPEW: some classes do work in both today but really were designed to be used one way only13:56
qschulzJPEW: no particular example to give, just trying to see if this is a possible scenario, and if so, how are we supposed to handle it13:56
qschulzRP: on another topic, I'm not happy with the solution I came up with for unifying the migration manuals on the docs website. I think i'll still work a bit on it to show what's left and what are the (nasty) shortcomings13:57
RPqschulz: ok, it is a tricky problem :/13:58
JPEWIs there a way to see the docs for un-supported releases (like gatesgarth?)14:04
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has quit IRC (Quit: Leaving.)14:05
*** agners <agners!~ags@2a02:169:3df5:10::ed4> has joined #yocto14:05
RPJPEW: I think the releases are in the index, just not in the drop down14:05
*** sakoman <sakoman!~steve@dhcp-72-253-6-214.hawaiiantel.net> has joined #yocto14:06
JPEWAH, "Outdated release manuals" Excellent14:06
qschulzyup14:06
qschulzor add the release number or release name after docs.yoctoproject.org/ in the URL14:07
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 268 seconds)14:09
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto14:09
qschulzJPEW: and you'll see that the outdated release manuals is not up-to-date on e.g. dunfell version of the docs :/14:11
landgrafRP: thank you for your comment on dropbear/ssh conflict bug. I'll try to find proper place for exclude_complimentary. I had some ideas when I was fixing this in Oniro need to find them14:13
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 268 seconds)14:14
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto14:14
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has joined #yocto14:14
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 268 seconds)14:19
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto14:19
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 268 seconds)14:24
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto14:24
*** F_Adrian <F_Adrian!~F_Adrian@62.32.0.69> has joined #yocto14:27
*** Estrella___ <Estrella___!~quassel@192-063-174-177.res.spectrum.com> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)14:39
*** gsalazar <gsalazar!~gsalazar@132.120.90.149.rev.vodafone.pt> has quit IRC (Read error: Connection reset by peer)14:39
*** gsalazar <gsalazar!~gsalazar@132.120.90.149.rev.vodafone.pt> has joined #yocto14:39
*** Estrella__ <Estrella__!~quassel@192-063-174-177.res.spectrum.com> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)14:40
*** Estrella <Estrella!~quassel@134.238.165.31> has quit IRC (Remote host closed the connection)14:40
*** Estrella <Estrella!~quassel@192-063-174-177.res.spectrum.com> has joined #yocto14:41
RPlandgraf: I'd wondered if we make things parallel install and have openssh "win" over dropbear but I think it would just confuse things more14:41
*** manuel1985 <manuel1985!~manuel198@2a02:1748:dd5c:f290:c5b2:fdff:b718:9edf> has quit IRC (Ping timeout: 268 seconds)14:44
ykronsHi all14:54
ykronsI want to debug a recipe where the do_configure is changing the package source code, but if I do a bitbake -c devshell <recipe>, I get a shell but the do_configuration action have not been done. Is there a way to have do_configure applied in the devshell?14:56
*** ptsneves <ptsneves!~Thunderbi@85-128-83-172.static.ip.netia.com.pl> has quit IRC (Ping timeout: 268 seconds)15:01
qschulzykrons: just run -c configure followed by -c devshell?15:03
ykronsthat way it seems the changes are not applied15:07
*** florian_kc <florian_kc!~florian@port-217-146-132-69.static.as20676.net> has quit IRC (Ping timeout: 252 seconds)15:13
ykronsI have just checked and the run.do_configure doesn't include my change, something is wrong somewhere else.15:13
*** gsalazar <gsalazar!~gsalazar@132.120.90.149.rev.vodafone.pt> has quit IRC (Quit: Leaving)15:15
*** gsalazar <gsalazar!~gsalazar@132.120.90.149.rev.vodafone.pt> has joined #yocto15:16
*** Estrella <Estrella!~quassel@192-063-174-177.res.spectrum.com> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)15:17
*** Estrella <Estrella!~quassel@192-063-174-177.res.spectrum.com> has joined #yocto15:24
*** seninha <seninha!~seninha@user/seninha> has quit IRC (Ping timeout: 252 seconds)15:26
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)15:27
khemzeddii: I think vboxdrivers recipe still has issues with new kernel see https://autobuilder.yoctoproject.org/typhoon/#/builders/88/builds/189315:50
zeddiiI wondered about that. The kernel-source probably isn't in place before that install of the stdarg.h15:52
zeddiiI never saw that locally. but could be racing.15:52
*** PascalBach[m] <PascalBach[m]!~bachpmatr@2001:470:69fc:105::1d3b> has quit IRC (Quit: You have been kicked for being idle)16:00
zeddiiI'm trying a build after cleanall on linux-yocto and vboxguest drivers to see if I see it.16:03
RPzeddii: please don't promote cleanall, that should never be needed16:05
zeddiiin my case, I need the new download, since I have fetched before with a local mirror of linux-yocto, and I don't want it to go into downloads for it.16:07
*** Vonter <Vonter!~Vonter@user/vonter> has joined #yocto16:08
zeddiiahah. khem. yes, I see it now. I'll send a fix.16:09
khemzeddii: perf fails with binutils 2.39 see https://lore.kernel.org/bpf/20220622231624.t63bkmkzphqvh3kx@alap3.anarazel.de/T/16:09
zeddiiI can cherry pick that into the various linux-yocto trees, I'll check the thread and see if the final has merged.16:10
*** goliath <goliath!~goliath@user/goliath> has joined #yocto16:21
zeddiikhem: vboxguestdrivers fixed. sending patch. Looking at perf now.16:26
zeddiithere's about 7 patches in a block for the pull request for 6.0, at least grabbing this as another might be wise;  tools bpf_jit_disasm: Fix compilation error with new binutils16:27
zeddiiit'll be interesting to see what makes -stable out of them.16:27
*** brazuca <brazuca!~brazuca@2804:7f4:3590:6971:8c94:68da:503b:9e7f> has quit IRC (Quit: Client closed)16:35
wyreqschulz, sure it doesn't fix it because when I modify the .bbappend recipe I have it again and have again to rerun bitbake, but for some strange reason always I have the issue I just have it for a first time, the successive times I run bitbake it compiles properly. I'll try what you suggest and use the devtool to regenerate the patch 🤔16:37
*** frieder <frieder!~frieder@200116b8241433810000000000002000.dip.versatel-1u1.de> has quit IRC (Remote host closed the connection)16:39
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 268 seconds)16:39
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto16:39
wyreqschulz, so should I run 'devtool modify linux-engicam'?16:41
wyreqschulz, not sure why apparently the devtool doesn't work https://bpa.st/PM4A16:44
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 252 seconds)16:44
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto16:44
wyreit maps virtual/kernel to linux-engicam16:47
wyrewhich looks like the proper one, but not sure why standard.py throws that TypeError exception16:48
*** zpfvo <zpfvo!~fvo@i59F5CFC9.versanet.de> has quit IRC (Quit: Leaving.)16:54
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 268 seconds)16:59
khemzeddii:  I also wonder if we should stop using libbfd in perf as default. Not only we have such API changes with major versions we also have GPL-2 and GPL-3 mixing there, we should perhaps start building perf with NO_LIBBFD=1 set.17:00
khemor make it a packageconfig where libbfd is disabled by default17:01
khemsomeone can still enable it if they need to.17:01
*** argonautx <argonautx!~argonautx@muedsl-82-207-240-114.citykom.de> has quit IRC (Quit: Leaving)17:04
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto17:04
zeddiia packageconfig makes sense to me. I don't use libbfd myself, so having it off wouldn't break me (and that's all that matters! ;) )17:06
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto17:07
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has quit IRC (Quit: Client closed)17:10
*** wkawka <wkawka!~wkawka@84-10-27-202.static.chello.pl> has quit IRC (Quit: Client closed)17:11
*** prabhakarlad <prabhakarlad!~prabhakar@pc.renesas.eu> has joined #yocto17:14
khemyes bubbles are nice and safe I agree 🙂17:14
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Ping timeout: 268 seconds)17:24
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Remote host closed the connection)17:35
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has joined #yocto17:37
*** leon-anavi <leon-anavi!~Leon@46.55.231.62> has quit IRC (Remote host closed the connection)17:38
*** seninha <seninha!~seninha@user/seninha> has joined #yocto17:43
*** astlep <astlep!~thelounge@107-136-136-210.lightspeed.nsvltn.sbcglobal.net> has quit IRC (Quit: The Lounge - https://thelounge.chat)18:13
*** brazuca <brazuca!~brazuca@2804:7f4:3590:6971:8c94:68da:503b:9e7f> has joined #yocto18:17
*** GregWilson <GregWilson!~GregWilso@12.26.104.3> has joined #yocto18:25
GregWilsonI have a problem with the configuration of the display on a RPi4, we have been running without a problem on versions up to zeus with a display of 1024x600. We are trying to upgrade to hardknot and the display is not accepting the configuration. Is there anybody here that understands RPi4 display configuration and could help me understand what is18:30
GregWilsongoing on?18:30
*** manuel1985 <manuel1985!~manuel198@mobiledyn-62-240-134-86.mrsn.at> has joined #yocto18:34
*** manuel1985 <manuel1985!~manuel198@mobiledyn-62-240-134-86.mrsn.at> has quit IRC (Ping timeout: 268 seconds)18:51
*** Circuitsoft <Circuitsoft!uid393878@id-393878.lymington.irccloud.com> has joined #yocto19:04
zeddiikhem: what's the right branch to build against the new binutils ?19:11
RPzeddii: it is in abelloni's test branch19:14
RPzeddii: ah. he dropped those19:15
*** florian_kc <florian_kc!~florian@dynamic-093-131-157-095.93.131.pool.telefonica.de> has joined #yocto19:17
RPabelloni: btw, rerunning  build for a warning doesn't work. It will pull from sstate the second time and mask it :(19:18
RPabelloni: we'll have to report that perf issue against the setuptools change I suspect19:18
*** GregWilson <GregWilson!~GregWilso@12.26.104.3> has quit IRC (Quit: Client closed)19:24
*** florian_kc <florian_kc!~florian@dynamic-093-131-157-095.93.131.pool.telefonica.de> has quit IRC (Ping timeout: 252 seconds)19:27
*** florian_kc <florian_kc!~florian@dynamic-093-131-157-095.93.131.pool.telefonica.de> has joined #yocto19:29
*** brazuca <brazuca!~brazuca@2804:7f4:3590:6971:8c94:68da:503b:9e7f> has quit IRC (Quit: Client closed)19:43
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)19:49
*** gsalazar <gsalazar!~gsalazar@132.120.90.149.rev.vodafone.pt> has quit IRC (Ping timeout: 252 seconds)19:53
*** ptsneves <ptsneves!~Thunderbi@031011128120.dynamic-3-poz-k-0-2-0.vectranet.pl> has joined #yocto20:04
*** Adrian_ <Adrian_!~e@dynamic-002-243-003-109.2.243.pool.telefonica.de> has quit IRC (Ping timeout: 268 seconds)20:12
*** GNUmoon2 <GNUmoon2!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection)20:15
*** GNUmoon2 <GNUmoon2!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto20:16
*** pbsds <pbsds!~pbsds@84.20.102.91> has quit IRC (Quit: The Lounge - https://thelounge.chat)20:30
*** mrnuke <mrnuke!~mrnuke@c-98-197-59-62.hsd1.tx.comcast.net> has quit IRC (Ping timeout: 268 seconds)20:31
*** GregWilson <GregWilson!~GregWilso@12.26.104.3> has joined #yocto20:32
*** pbsds <pbsds!~pbsds@84.20.102.91> has joined #yocto20:33
abelloniRP: sure, I was not rerunning for the warning20:35
abelloniI tested my branch with a single build first20:35
abelloniand then started a-full20:35
abellonizeddii: if needed, I can quickly push my previous branch20:36
*** brazuca <brazuca!~brazuca@2804:7f4:3590:6971:8c94:68da:503b:9e7f> has joined #yocto20:37
*** mvlad <mvlad!~mvlad@2a02:2f08:4a10:7900:24d7:51ff:fed6:906d> has quit IRC (Remote host closed the connection)20:42
RPabelloni: fair enough, it just caught my eye and looked different :)20:43
*** agupta1 <agupta1!~agupta1@207.107.110.122> has quit IRC (Ping timeout: 268 seconds)21:00
*** nemik <nemik!~nemik@207.237.248.190> has quit IRC (Ping timeout: 268 seconds)21:13
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has joined #yocto21:14
*** nemik <nemik!~nemik@162-245-20-117.PUBLIC.monkeybrains.net> has quit IRC (Ping timeout: 268 seconds)21:18
*** nemik <nemik!~nemik@207.237.248.190> has joined #yocto21:19
*** florian_kc <florian_kc!~florian@dynamic-093-131-157-095.93.131.pool.telefonica.de> has quit IRC (Ping timeout: 252 seconds)21:51
*** adrian_ <adrian_!~F_Adrian@147.161.235.21> has joined #yocto22:15
*** F_Adrian <F_Adrian!~F_Adrian@62.32.0.69> has quit IRC (Ping timeout: 268 seconds)22:18
*** Circuitsoft <Circuitsoft!uid393878@id-393878.lymington.irccloud.com> has quit IRC (Quit: Connection closed for inactivity)22:24
*** GNUmoon2 <GNUmoon2!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Write error: Connection reset by peer)22:25
*** GNUmoon2 <GNUmoon2!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto22:28
*** pbsds <pbsds!~pbsds@84.20.102.91> has quit IRC (Ping timeout: 268 seconds)22:33
*** vmeson <vmeson!~rmacleod@23-233-86-175.cpe.pppoe.ca> has quit IRC (Remote host closed the connection)22:37
*** vmeson <vmeson!~rmacleod@23-233-86-175.cpe.pppoe.ca> has joined #yocto22:41
*** adrian_ <adrian_!~F_Adrian@147.161.235.21> has quit IRC (Ping timeout: 252 seconds)22:42
*** brazuca <brazuca!~brazuca@2804:7f4:3590:6971:8c94:68da:503b:9e7f> has quit IRC (Quit: Client closed)22:45
*** brazuca <brazuca!~brazuca@2804:7f4:3590:6971:8c94:68da:503b:9e7f> has joined #yocto22:55
*** GNUmoon2 <GNUmoon2!~GNUmoon@gateway/tor-sasl/gnumoon> has quit IRC (Remote host closed the connection)23:07
*** GNUmoon2 <GNUmoon2!~GNUmoon@gateway/tor-sasl/gnumoon> has joined #yocto23:08
*** pbsds <pbsds!~pbsds@84.20.102.91> has joined #yocto23:09
*** ardo <ardo!~ardo@host-188-10-58-99.business.telecomitalia.it> has quit IRC (Read error: Connection reset by peer)23:17
*** ardo <ardo!~ardo@host-188-10-58-99.business.telecomitalia.it> has joined #yocto23:17
*** agupta1 <agupta1!~agupta1@207.107.110.122> has joined #yocto23:33
*** brazuca <brazuca!~brazuca@2804:7f4:3590:6971:8c94:68da:503b:9e7f> has quit IRC (Quit: Client closed)23:40

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!