Friday, 2021-09-24

*** grma <grma!~gruberm@> has quit IRC (Ping timeout: 252 seconds)00:05
*** vd <vd!> has quit IRC (Quit: Client closed)00:29
*** vd <vd!> has joined #yocto00:30
berton[m]Hi! I'm working with a recipe that has PN, PN-tools and PN-test. These 3 packages has .debug files and I need to put this .debug file in PN-dbg, PN-tools-dbg ... I can't find a way to do this, the .debug files always goes to the first PN-*-dbg entry in PACKAGES list. Is there a way create more than on -dbg package?00:33
*** berton[m] <berton[m]!~fabiobert@2001:470:69fc:105::ce36> has quit IRC (Quit: Reconnecting)00:52
*** berton[m] <berton[m]!~fabiobert@2001:470:69fc:105::ce36> has joined #yocto00:52
*** berton[m] <berton[m]!~fabiobert@2001:470:69fc:105::ce36> has quit IRC (Client Quit)00:54
*** berton[m] <berton[m]!~berton@2001:470:69fc:105::ce36> has joined #yocto00:54
*** vd <vd!> has quit IRC (Quit: Client closed)01:06
*** camus1 <camus1!~Instantbi@> has joined #yocto01:16
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 265 seconds)01:18
*** camus1 is now known as camus01:18
*** vd <vd!> has joined #yocto01:39
*** vd <vd!> has quit IRC (Quit: Client closed)01:49
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)02:04
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto02:09
*** sakoman <sakoman!> has quit IRC (Quit: Leaving.)02:43
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Quit: jmiehe)02:50
zeddiiRP:  khem: I have the vbox drivers building, I had to re-learn SVN and tease out the patches.02:59
*** camus1 <camus1!~Instantbi@> has joined #yocto03:01
*** camus <camus!~Instantbi@> has quit IRC (Remote host closed the connection)03:01
*** camus1 is now known as camus03:02
*** sakoman <sakoman!> has joined #yocto03:05
zeddiikhem: around ?03:39
*** arlen <arlen!> has quit IRC (Ping timeout: 264 seconds)03:56
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 252 seconds)04:17
*** camus <camus!~Instantbi@> has joined #yocto04:28
*** amitk <amitk!~amit@> has joined #yocto04:30
zeddiihalstead: do you happen to be around ? I'm trying to push updates for the 5.15 kernel and the git.yoctoproject hooks are once again taking issue with names in mainline commits and rejecting the pushes04:33
zeddiiI'll try and grab you tomorrow. I'm calling it a day ..04:38
halsteadzeddii:  Please send me the error message when you get a chance.04:40
*** xmn <xmn!> has quit IRC (Quit: ZZZzzz…)04:44
*** sakoman <sakoman!> has quit IRC (Quit: Leaving.)05:12
*** kiran <kiran!~kiran@2607:fea8:5a80:ea0:d49f:da50:802d:5705> has joined #yocto05:24
*** oobitots <oobitots!> has joined #yocto05:39
*** Sion <Sion!> has joined #yocto05:55
*** ThomasD13 <ThomasD13!> has joined #yocto06:04
*** fbre <fbre!~fbre@> has joined #yocto06:15
*** rob_w <rob_w!> has joined #yocto06:22
*** oobitots <oobitots!> has quit IRC (Quit: Client closed)06:30
*** Guest2944 <Guest2944!> has joined #yocto06:31
*** Guest2944 is now known as oobitots06:31
*** oobitots <oobitots!> has quit IRC (Client Quit)06:32
*** oobitots <oobitots!> has joined #yocto06:32
*** camus1 <camus1!~Instantbi@> has joined #yocto06:37
JosefHolzmayrTheyo dudX06:39
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 265 seconds)06:39
*** camus1 is now known as camus06:39
*** Schlumpf <Schlumpf!~Schlumpf@> has joined #yocto06:42
*** Wouter0100 <Wouter0100!> has quit IRC (Remote host closed the connection)06:46
*** Wouter01008 <Wouter01008!> has joined #yocto06:46
*** mckoan|away is now known as mckoan06:49
mckoangood morning JosefHolzmayrThe, everyone06:50
JosefHolzmayrTheyo mckoan06:54
*** leon-anavi <leon-anavi!~Leon@> has joined #yocto06:57
*** lucaceresoli <lucaceresoli!~lucaceres@> has joined #yocto06:58
*** ant__ <ant__!> has joined #yocto07:06
RPzeddii: great, thanks07:17
*** prabhakarlad <prabhakarlad!> has joined #yocto07:20
*** xmn <xmn!> has joined #yocto07:21
*** grma <grma!~gruberm@> has joined #yocto07:44
*** argonautx <argonautx!> has joined #yocto07:46
*** mihai <mihai!~mihai@user/mihai> has joined #yocto07:49
*** mihai <mihai!~mihai@user/mihai> has quit IRC (Quit: Leaving)08:04
*** tnovotny <tnovotny!> has joined #yocto08:04
*** florian <florian!> has joined #yocto08:18
*** zyga-mbp <zyga-mbp!~zyga@> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)08:32
ThomasD13Good morning: Short question to MACHINEOVERRIDES: machine1 = j7-evm, machine2 = j7-paradise, FOOBAR = "morning", FOOBAR_j7-paradise = "evening", MACHINEOVERRIDES for machine2 = "j7-evm".08:32
ThomasD13When building for machine2, is FOOBAR set to morning or evening?08:32
*** zyga-mbp <zyga-mbp!~zyga@> has joined #yocto08:36
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 265 seconds)08:36
*** camus <camus!~Instantbi@> has joined #yocto08:36
RPThomasD13: I can't quite understand which override is set where but if j7-paradise is in overrides, it will be evening, otherwise morning08:42
ThomasD13OH sorry - MACHINEOVERRIDES in j7-paradise.conf is set to "j7-evm"08:44
*** zyga-mbp <zyga-mbp!~zyga@> has quit IRC (Quit: My MacBook has gone to sleep. ZZZzzz…)08:51
*** zyga-mbp <zyga-mbp!~zyga@> has joined #yocto08:52
ThomasD13Here is a more detailed example:    I wonder why FOOBAR is still set in this case to "morning"08:57
barathRP: we've had more dunfell builds failing with the covered/notcovered issue. I'm gonna try to backport the fix for ourselves and test, unless there is an official dunfell backport in the pipeline?08:58
ThomasD13When I use the exact same config and build for MACHINE=j7-evm, FOOBAR is set to "evening"08:58
*** camus <camus!~Instantbi@> has quit IRC (Read error: Connection reset by peer)09:03
*** camus <camus!~Instantbi@> has joined #yocto09:03
RPbarath: is where it would show up, looks like those aren't there as yet09:07
RPThomasD13: what is the value of OVERRIDES there?09:08
RPThomasD13: missing ":" in the setting of MACHINEOVERRIDES?09:09
barath@RP thanks. what's that -nut naming scheme? is this documented or just "institutional knowledge"  :D09:10
RPbarath: "next-under-test"09:12
barathah okay09:12
RPbarath: I'm just about to merge the patches for that for hardknott fwiw09:12
ThomasD13RP, OVERRIDES="linux:aarch64:pn-nano:aarch64:ti-soc:k3:j7:j7-evmj7-processor:arago:class-target:libc-glibc:forcevariable"09:13
barathRP: thanks, that's nice09:13
ThomasD13Yes, there seems to be a missing :09:13
RPThomasD13: that will be the issue09:13
ThomasD13oh man.... thank you so much - i guess its missing for j7-evm ?09:14
RPThomasD13: yes, I think so09:15
*** xmn <xmn!> has quit IRC (Quit: ZZZzzz…)09:35
*** willo <willo!> has quit IRC (Ping timeout: 260 seconds)09:42
*** xmn <xmn!> has joined #yocto09:43
*** willo <willo!> has joined #yocto09:45
*** xmn <xmn!> has quit IRC (Quit: ZZZzzz…)09:56
*** Schlumpf <Schlumpf!~Schlumpf@> has quit IRC (Quit: Client closed)09:57
*** xmn <xmn!> has joined #yocto10:01
Wouter01008Hey guys! I'm trying to build my first recipe for gocryptfs, but I get a lot of "no non-test Go files" ( As a reference I took the rclone recipe from the recipe index, and here it seems they remove specific folders in do_install_prepend - but I tried doing this, but it doesn't seem to work. My current recipe:10:09
Wouter01008I also tried removing go-mod, but this gave a whole different error. :"D10:09
*** camus1 <camus1!~Instantbi@> has joined #yocto10:13
*** camus <camus!~Instantbi@> has quit IRC (Remote host closed the connection)10:14
*** camus1 is now known as camus10:14
*** goliath <goliath!~goliath@user/goliath> has joined #yocto10:24
*** mckoan is now known as mckoan|away10:24
*** ThomasD13 <ThomasD13!> has quit IRC (Ping timeout: 252 seconds)10:32
*** beneth <beneth!~beneth@2001:41d0:c:a71:1000:25::> has joined #yocto10:42
*** amitk <amitk!~amit@> has quit IRC (Ping timeout: 265 seconds)10:58
*** Sion <Sion!> has quit IRC (Ping timeout: 250 seconds)11:16
*** amitk <amitk!~amit@> has joined #yocto11:21
*** amitk <amitk!~amit@> has quit IRC (Ping timeout: 265 seconds)11:26
*** xmn <xmn!> has quit IRC (Ping timeout: 252 seconds)11:30
*** rob_w <rob_w!> has quit IRC (Remote host closed the connection)11:31
*** zyga-mbp <zyga-mbp!~zyga@> has quit IRC (Quit: Textual IRC Client:
*** zyga-mbp <zyga-mbp!~zyga@> has joined #yocto11:57
*** camus1 <camus1!~Instantbi@> has joined #yocto11:57
*** camus <camus!~Instantbi@> has quit IRC (Ping timeout: 265 seconds)11:59
*** camus1 is now known as camus11:59
*** davidinux <davidinux!~davidinux@> has quit IRC (Ping timeout: 252 seconds)12:10
*** davidinux <davidinux!~davidinux@> has joined #yocto12:34
berton[m]Hi all! I'm looking here and that patches are outdated. Is there other location to get patches?12:35
*** camus1 <camus1!~Instantbi@> has joined #yocto12:48
*** camus <camus!~Instantbi@> has quit IRC (Read error: Connection reset by peer)12:48
*** camus1 is now known as camus12:48
*** camus <camus!~Instantbi@> has quit IRC (Quit: camus)12:57
*** Sion <Sion!> has joined #yocto13:17
*** camus <camus!~Instantbi@2409:8a1e:9118:4360:b8b5:261d:fd85:5b45> has joined #yocto13:33
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto13:36
RPor lists.openembedded.org13:37
*** arlen <arlen!> has joined #yocto13:40
TartarusSo, I figured out the handful of missing packages from the existing oe-core sdk related packagegroups needed to build 5.14's arm64 defconfig.  Should I post those as a patch somewhere?  Or getting a bit task specific rather than general dev?13:42
Tartarus(It's bison, flex, bc and perl-module-integer, the first two are arguably general buildessentials, bc maybe should be default'd on in busybox? and that last one tho..)13:42
*** RP <RP!~richard@2001:8b0:aba:5f3c:96de:80ff:fe6d:2d2b> has quit IRC (Ping timeout: 264 seconds)13:44
*** fbre <fbre!~fbre@> has quit IRC (Quit: fbre)13:44
zeddiiTartarus: see the OE core thread/patch titled "[OE-core][PATCH] nativesdk-packagegroup-sdk-host: add perl integer module "13:44
zeddiifor the perl question, as for the others, we normally collect them in devsrc, but the ones you list are already there.13:45
zeddiibut it might be missing the SDK bbclass extend, since that is mainly tested for on target builds.13:45
Tartaruszeddii: Note that I'm talking about on-device.13:46
zeddiiwhich is what we do with devsrc all the time.13:46
*** RP <RP!~richard@2001:8b0:aba:5f3c:96de:80ff:fe6d:2d2b> has joined #yocto13:46
Tartaruszeddii: I guess I'm missing something then.  Rather than tools-sdk being added to my image features, what should I have done?13:47
zeddiiwe do this in core-image-kernel-dev:13:48
zeddiimeta/recipes-extended/images/ ?= "packagegroup-core-tools-profile packagegroup-core-buildessential kernel-devsrc"13:48
TartarusYeah, that seems a bit wrong-headed frankly.  I want a generic image that I can build on.  Step one was wget'ing stable from kernel.org13:50
* zeddii shrugs13:50
TartarusI admit the perl question is rather sticky13:50
TartarusMaybe looking at it differently, what's the knob for "I want to be able to re-build anything installed on this image" ?  That would be the generic approach since the kernel is just another thing installed on the system13:53
* tlwoerner looks for a knob13:55
*** camus <camus!~Instantbi@2409:8a1e:9118:4360:b8b5:261d:fd85:5b45> has quit IRC (Quit: camus)14:04
*** camus <camus!~Instantbi@2409:8a1e:9118:4360:88ed:2a94:e633:61be> has joined #yocto14:05
RPTartarus: I'm not sure we capture that information anywhere as nobody usually does that14:07
RPYou'd want sources and build dependencies for everything with the build deps being translated to the target14:07
TartarusRP: I'll admit this usecase is a tad odd, I'm trying to make an image that's useful as  a "build stuff natively on it" image14:08
TartarusBut I've gone down another hole now, I can't spot how kernel-devsrc is made14:08
RPTartarus: it has a recipe14:09
*** Sion <Sion!> has quit IRC (Ping timeout: 265 seconds)14:09
RPTartarus: the "build stuff natively" has a packagegroup iirc14:09
TartarusLemme go make that other cup of coffee now14:09
RPTartarus: I'm trying not to laugh :)14:09
TartarusRP: Yeah, there's a buildessential packagegroup, and it's missing flex, bison, bc and then that perl module, for the kernel14:10
TartarusGlad I could brighten your Friday :)14:10
smurrayWould packagegroup-self-hosted be useful, I've used that for build containers?14:10
RPTartarus: patch welcome to add those14:10
smurrayThough I guess self-hosted is for the OE build aspect, vs build-essential being more like Debian's I assume14:11
zeddiiI guess it depends on what is essential :D14:12
zeddiiI've used the self-hosted image/package group to build servers that can rebuild themselves in the past.14:12
TartarusRP: OK, thanks, I'll do that, and I'll put enabling bc in busybox on the list too, and see what the feedback gets to be14:12
RPTartarus: other option is a new group build-essential-kernel14:16
*** sakoman <sakoman!> has joined #yocto14:16
Croftonanyone know how to get a ssh login if I plug my pi into my laptop directly with a network cable14:23
qschulzCrofton: easiest way is to setup a hardcoded IP address for your Pi at boot on the Ethernet interface and manually add an IP address on the Ethernet interface on the laptop14:26
qschulzwith the appropriate netmask, should be good to go14:26
*** argonautx <argonautx!> has quit IRC (Ping timeout: 252 seconds)14:26
TartarusSo long as you remembered to enable ssh as an image feature :)14:26
Croftonwe need an idiot guide to using a pi4 with an oe build :)14:26
*** mihai <mihai!~mihai@user/mihai> has joined #yocto14:27
qschulzTartarus: indeed14:27
Croftonwhich I did not :)14:28
halsteadzeddii: You are all set to push.14:30
smurrayCrofton: if you don't have  serial cable for the pi and know it'll do dhcp, the quick and dirty method is dnsmasq on the laptop14:37
berton[m]rburton:  you mention to see patches in Is there a tool like pwclient to get patches? I wondering how is a smart way to get patches and apply locally14:38
*** yates <yates!> has joined #yocto14:39
rburtonberton[m]: not sure what the state of getting patchwork up and running is again. halstead?14:39
*** tlwoerner <tlwoerner!> has quit IRC (Remote host closed the connection)14:40
*** tlwoerner <tlwoerner!> has joined #yocto14:40
*** whuang0389 <whuang0389!> has joined #yocto14:41
halsteadrburton: we are working on a replacement. We got reliable list collection working yesterday. I think that was the main block so it should be less than a week now.14:42
*** kiran <kiran!~kiran@2607:fea8:5a80:ea0:d49f:da50:802d:5705> has quit IRC (Ping timeout: 260 seconds)14:43
*** kiran <kiran!~kiran@2607:fea8:5a80:ea0:d49f:da50:802d:5705> has joined #yocto14:43
berton[m]Nice :)14:43
zeddiihalstead: thanks! works perfectly.14:45
rburtonhalstead: cool14:46
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Read error: Connection reset by peer)14:53
* tlwoerner always has "quick and dirty" running on my embedded boards subnet14:57
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto14:59
tlwoernerzeddii: what's the best way to start with a completely empty kernel config, to which i then start adding fragments via the BSP layer, yocto-kernel-cache, IMAGE_FEATURES, etc?15:03
tlwoernerzeddii: KBUILD_DEFCONFIG = "" ?15:03
*** cengiz_io <cengiz_io!> has quit IRC (Ping timeout: 240 seconds)15:03
*** paulbarker <paulbarker!> has quit IRC (Ping timeout: 268 seconds)15:03
*** NishanthMenon_ <NishanthMenon_!> has quit IRC (Ping timeout: 268 seconds)15:03
*** awafaa <awafaa!> has quit IRC (Read error: Connection reset by peer)15:04
*** awafaa <awafaa!> has joined #yocto15:04
*** armpit_ <armpit_!> has joined #yocto15:04
*** armpit <armpit!> has quit IRC (Ping timeout: 268 seconds)15:04
*** CosmicPenguin <CosmicPenguin!> has quit IRC (Ping timeout: 268 seconds)15:04
*** armpit_ is now known as armpit15:04
*** paulbarker <paulbarker!> has joined #yocto15:04
*** cengiz_io <cengiz_io!> has joined #yocto15:04
*** CosmicPenguin <CosmicPenguin!> has joined #yocto15:04
*** NishanthMenon_ <NishanthMenon_!> has joined #yocto15:04
*** tnovotny <tnovotny!> has quit IRC (Quit: Leaving)15:06
qschulztlwoerner: or just remove the .config and then run make menuconfig and select the options by hand?15:12
qschulzit's tedious though15:12
zeddiitlwoerner: I was just writing something up for you, I sent my last series to get rid of 5.13 and was going to spend the afternoon fixing up an old script and instructions.15:13
tlwoernerzeddii: sweet! thanks :-D15:14
tlwoernerqschulz: in my opinion, providing .configs is old-skool. we have the ability (thanks to the work by zeddii) to do *SO* much better. users should be able to "build their own" configs, based on:15:15
tlwoerner- what they're including in their images15:15
tlwoerner- choosing features explicitly15:15
tlwoernerthe BSP should provide what's required to get the basics running, user's/configs should select the rest15:16
qschulztlwoerner: I meant "do that for the base defconfig"15:21
qschulzi.e. to start with a completely empty kernel config15:21
tlwoernerqschulz: in other words... create fragments? ;-)15:22
qschulzI'm not sure it makes sense to really have nothing as a base?15:23
qschulzthere sure is something in common on all those boards :)15:23
tlwoernerlike what? support for qcom chips? ;-) (i jest)15:23
tlwoerneri believe yocto-kernel-config already has "base" fragments based on "tiny" "regular" "large" kernels15:24
tlwoernerideally this "build your own" config would happen behind the scenes. the config would get built "magically" based on image options (and users could pick things explicitly on top too)15:27
tlwoernerimage options, distro options, etc...15:27
*** vd <vd!> has joined #yocto15:30
*** lucaceresoli <lucaceresoli!~lucaceres@> has quit IRC (Ping timeout: 252 seconds)15:35
*** dev1990 <dev1990!~dev@> has joined #yocto15:45
*** wooosaiii <wooosaiii!> has quit IRC (Remote host closed the connection)15:52
*** wooosaiii <wooosaiii!> has joined #yocto15:52
yatesi'm having a problem building u-boot for my new architecture. the do_configure is complaining that .config does not exist:
yatesany hints?15:52
*** oobitots <oobitots!> has quit IRC (Quit: Client closed)15:54
tlwoerneryates: Nothing to be done for '/mnt/NVMe2/yocto/build-toolchain-0/tmp/work/qemucsky-poky-linux/u-boot/1_2020.07-r0/git/configs/qemu-csky-defconfig15:54
tlwoernerthat line would have created the .config, if that defconfig had been found15:55
yatestlwoerner: thanks. that line resulted from the following make: make -f /mnt/NVMe2/yocto/build-toolchain-0/tmp/work/qemucsky-poky-linux/u-boot/1_2020.07-r0/git/scripts/ obj=scripts/kconfig configs/qemu-csky-defconfig15:57
yatesoriginally it was this: /mnt/NVMe2/yocto/build-toolchain-0/tmp/work/qemucsky-poky-linux/u-boot/1_2020.07-r0/git/scripts/ obj=scripts/kconfig qemu-csky-defconfig15:58
yatesthere is no qemu-csky-defconfig target in Makefile.build15:58
yates(i had attempted to "correct" the missing target by simply supplying the file)15:59
yatesis generated by either yocto or perhaps automake?15:59
tlwoerneryates: you would need to create a patch adding the defconfig, then you can set it with UBOOT_MACHINE in your configs16:00
yatestlwoerner: if i did that, then wouldn't the end result be that qemu-csky-defconfig would end up in git/configs, and that the build would again fail with no .config found?16:01
tlwoernerthe u-boot build will generate the .config from the specified *_defconfig16:02
tlwoerner(use underscores, by the way)16:02
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Ping timeout: 252 seconds)16:02
yatesshould the patch add that config to git/configs?16:03
yatesto build-toolchain-0/tmp/work/qemucsky-poky-linux/u-boot/1_2020.07-r0/git/configs ?16:04
tlwoerneryates: yes. note that there's a difference between a config and a defconfig16:04
tlwoerneryou'd add a patch to u-boot, which, relative to u-boot, would add that file into configs/16:04
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto16:04
tlwoernerthen yocto will do a "make qemu_csky_defconfig" which causes u-boot's build to generate the .config16:05
yatesok i think i got it16:05
tlwoerneryates: if i were doing it...16:05
tlwoerner1. generate the cross compiler using yocto. install, source16:07
tlwoerner2. checkout u-boot sources (outside of yocto)16:07
tlwoerner3. run "make menuconfig", choose your settings and options16:08
tlwoerner4. run "make savedefconfig"16:08
yatestlwoerner: check/egg problem. you can get the cross compiler built until you can successfully build an image, and a successful image requires a successful u-boot build16:09
tlwoerner5. move/add the defconfig into u-boot's configs/ directory and rename it (qemu_csky_defconfig)16:09
yatess/you can/you can't/16:09
yates...chicken/egg problem...16:09
tlwoerneryates: you can build the cross compiler well before needing to generate an image16:09
tlwoerner"bitbake meta-toolchian"16:09
tlwoernerall you need is a MACHINE config16:10
yatesreally? that's news to me!16:10
yateslet me give that a go16:10
tlwoerneror you can do "-c populate_sdk"16:10
* tlwoerner has been meaning to blog about this workflow for a while16:10
yatestlwoerner: well that's what i'm doing: bitbake -c populate_sdk_ext core-image-minimal16:11
tlwoernerleave off the "core-image-minimal" at the end, switch to "populate_sdk" (leave off the _ext)16:11
tlwoerneror just do "bitbake meta-toolchain"16:11
yatesok lemme give those a try.16:12
tlwoerneroops sorry16:12
yatesthanks man!!! very sorely needed your guidance!16:12
tlwoerneryou wouldn't be able to leave off the core-image-minimal from the end16:12
yatesok well i can try bitbake meta-toolchain ?16:12
tlwoernerbut by adding "-c populate_sdk" you're saying "stop after generating the sdk"16:12
tlwoerneryes, that's what i do16:13
tlwoernerjust like saying "bitbake <recipe> -c configure" stops after the do_configure step of <recipe>16:13
tlwoerner6. with the defconfig in u-boot's configs/ directory, create a u-boot patch adding the defconfig16:14
yatesbut literally what i need to do is just "bitbake meta-toolchain"?16:14
tlwoerneryes, just do "bitbake meta-toolchain" for a basic cross-compiler sdk, that's what i do16:14
yatesdoes that create the install script too?16:14
tlwoernerbut i had to mention that there's a second way to do it (for completeness)16:14
tlwoernerthe sdk install script? yes16:14
yatesyes, ok good16:15
tlwoerner7. import the u-boot patch into your custom csky layer (u-boot_%.bbappend)16:15
*** amitk <amitk!~amit@> has joined #yocto16:16
yatestlwoerner: is 7 the last step?16:18
tlwoerner8. "bitbake u-boot"16:18
yates9. have a glass of wine16:19
tlwoernerby the way, between 3. and 4. you would probably want to run a "make" to see how it goes16:19
yatesdoes "bitbake meta-toolchain" build just the sdk (not the sdk_ext)?16:24
yatesthat's fine, we only need the sdk for now at least, i'm just curious16:25
tlwoerneryou only need an _ext if you need devtool, which you don't in the early stages of board bring-up16:25
yateswhy would devtool need it?16:26
yatesaren't you still building on the host when using devtool?16:26
*** whuang0389 <whuang0389!> has quit IRC (Quit: Client closed)16:27
tlwoerneresdk = sdk + devtool16:27
yatesoh, right16:27
yateshow do you build the native target toolchain?16:28
tlwoernerand devtool is useful for updating recipes, deploying recipes to target, etc16:28
yatestlwoerner: yes, right, i've used it before.16:28
tlwoerner"native target toolchain"? a toolchain to run on the target?16:28
yateslike "gcc" on your standard ubuntu/x86 system16:29
*** florian <florian!> has quit IRC (Quit: Ex-Chat)16:30
yateswe probably won't need that, but it would be good to have in my "back pocket".16:30
tlwoerneronce you have an image running on your target, you can add "tools-sdk" to EXTRA_IMAGE_FEATURES16:30
tlwoerneryates: not it's not ;-) just use yocto and cross-compile ;-)16:31
tlwoernerin order to build on-target you need all the header files and all the dependent libraries installed.... it gets huge quickly16:32
yatesit snot? yah, building on a wee tiny board is probably unbearable16:32
tlwoerneryou need to install all the -dev packages16:32
*** fleg <fleg!64bf4386e9@user/fleg> has quit IRC (Ping timeout: 240 seconds)16:34
tlwoerner9. submit your u-boot patch upstream16:37
jonmasondoes anyone actually use
jonmasonbecause it has hardcoded values for x86, which seem like a bad idea16:39
jonmasonI fixed something similar in meta-zephyr, but seems like a better idea to remove if not actually being used16:40
RPjonmason: don't we need that to test poky-tiny ?16:45
jonmasonRP: that was my guess, but is poky-tiny only ever tested on x86?16:45
RPjonmason: yes :/16:45
jonmasonRP: I would think Arm would like that for them ;-)16:46
RPjonmason: patches very welcome16:46
jonmasonalso, is hosed currently16:46
RPjonmason: given the large number of people we have working on all the QA stuff, I'm not suprised16:47
jonmasonthe child is exiting with sys.exit(0), and now that we care about systeemxit in, boom16:47
RPjonmason: I guess we could catch the 0 case and pass it16:48
RPjonmason: and add another logging test for this :)16:48
jonmasonI thought about that, but thought it was a little hacky16:48
jonmasonbut I'm happy to be hacking on a Friday afternoon16:49
RPTorn on that. You'd think it would just return I guess16:49
RPcan we stop it using sys.exit ?16:49
jonmasonthat is my current hack and it seems happy16:50
RPjonmason: that is easier16:50
jonmasonI see a similar line in, I wonder if that should be removed too16:50
jonmasonline 26816:50
*** dgriego <dgriego!~dgriego@user/dgriego> has quit IRC (Quit: Textual IRC Client:
RPjonmason: looking at that code, here be dragons16:51
RPjonmason: we can't make that a return16:52
jonmasonthis looks super brittle16:52
RPjonmason: I think that should be an os._exit(0)16:52
jonmasonI can see if that makes it smoke.  one sec16:53
RPsince it follows a fork16:53
jonmasonI'll send a patch to meta-zephyr.  did you want me to do one for too?16:55
RPplease, that does need fixing16:55
jonmasonwill do, with testing....after lunch16:55
tlwoernerthe next Yocto Project Summit (yps2021.11) is live:
tlwoernerand the CfP is open17:08
tlwoernerJosefHolzmayrThe: ^^17:08
tlwoernerit will be a 3-day event this time, including beginner presentations, intermediate to advanced hands-on labs, talks/presentations17:10
tlwoernerthe final format of the conference has not been 100% determined yet, but there will be talks and hands-on and i encourage members to think about submitting their proposals17:11
JosefHolzmayrThetlwoerner I'll go wild on Monday!17:13
tlwoernerimplying your not wild on the weekends?17:13
tlwoerneror permanently?17:13
* tlwoerner uses the wrong "your/you're" (grrr)17:14
tlwoernerthe CfP is open for the next ~3 weeks + 3 days17:16
jonmasontlwoerner: It would be nice to give us a little more notice that this is coming.  Something like 3 months, 1 month of heads up, one month of CFP, and one month to get the presentation ready.  Probably much more once travel starts to happen (travel budgets need approval way ahead of time)17:41
jonmasonJosefHolzmayrThe: you can present on gitlab-ci and how awesome it is ;-)17:42
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)17:43
jonmasonRP: if you get free time, this is a cool session from the other day
tlwoernerjonmason: 2 is not enough for a virtual event? ;-)17:48
tlwoernerthe plan, going forward, is to continue having some sort of virtual YPS every 6 months indefinitely (i.e. as long as someone organizes it)17:49
jonmasonI'm on my second in 3 weeks, with another next week.  I'm about conferenced out right now17:49
tlwoernerso May-ish and November-ish17:49
tlwoernerwell yes, that's why we're not doing YPS now, that's exactly why we've planned it for 2 months from now17:50
jonmasonI think adding them again to ELCs would be awesome17:50
tlwoernerfor the time-being, while everything is virtual, YPS grew17:51
jonmasontlwoerner: don't get me wrong, I think you are doing an awesome job17:51
tlwoernerYPS now has: beginner, hands-on, talks, OEDvM, social17:51
jonmasonIt takes me a while to forget how much I hate presenting ;-)17:52
tlwoernerbut when we go back to in-person meetings, YPS will shrink17:52
jonmasonwe need to find a way to continue to do itvirtual17:52
tlwoernerannoyingly, elc is too "unstable". they've been doing elcs all over the map17:52
jonmasonhonestly, they have no excuse for it now being aligned anymore17:53
jonmasonthey've had a full year to reset17:53
tlwoerneryes, that's the plan. even after we go back to in-person events, we still want to have some part of YPS continuing on virtually (training mostly)17:53
jonmasonvirtual would allow for prerecordings and allow for people who do the trainings to attend the developer meetings17:53
tlwoernerin 2 months you'll be jonesing for another conference ;-)17:53
jonmasonbut I do have a concern that it might be the only way some people cang et travel funding approved though17:54
jonmasonthis is all a fun dance, right17:54
tlwoernerso when it comes time to split YPS into virtual and in-person, the in-person parts will align with ELC, the virtual parts... don't know yet17:56
tlwoernerjonmason: we're not running the developer meeting at the same time as the trainings (or the talks)18:01
tlwoerner(this time)18:01
tlwoernerday 1 will be 2 tracks:18:01
tlwoerner- beginner18:02
tlwoerner- hands-on18:02
*** florian <florian!> has joined #yocto18:02
JosefHolzmayrThejonmason good idea, actually.18:03
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Read error: Connection reset by peer)18:03
*** nateglims <nateglims!~nateglims@> has joined #yocto18:08
jonmasonJosefHolzmayrThe: you might like the RH kernel gitlab session at plumbers too.
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto18:11
JosefHolzmayrThejonmason I'll check or or but I guess I have something completely different on my mind.18:12
*** goliath <goliath!~goliath@user/goliath> has joined #yocto18:29
vmesonbluelightning:   layer index error for crmsh: see 3.03 on master but it's 4.x: -- YP BZ or ???18:41
RPJPEW: do I remember you needing to do something to force pseudo to sync it's DB at exit with docker?18:48
*** amitk <amitk!~amit@> has quit IRC (Ping timeout: 252 seconds)18:51
JPEWYes. Look at the cleanup script in pyrex (AFK right now or I would send a link)18:54
*** amitk <amitk!~amit@> has joined #yocto18:56
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has quit IRC (Ping timeout: 250 seconds)18:57
khemRP: meta-openembedded layers are now fixed with master-next19:16
khemthanks zeddii for the vboxdrivers fix19:17
khemJPEW:  how do you do user mapping in pyrex ?19:17
JPEWkhem: very carefully. We make sure the user in pyrex has the same uid/gid as the user running the container19:19
khemhow do you do that though, is it done during env setup ?19:20
khemor do you modify the container somehowo19:20
RPjonmason: it is interesting. We certainly struggle with the patch review dilemma too19:20
RPkhem: thanks! Sorry about the issues, I think they are worth fixing though19:20
khemRP:  yeah I would not have fixed them otherwise :)19:21
jonmasonRP: i liked all the work they did, but the mailing list issue is a major hurdle19:22
JPEWkhem: captures the state and passes it to the container which recreates it inside19:22
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Read error: Connection reset by peer)19:23
JPEWIt means it's basically impossible to correctly invoke just the pyrex container manually, since it needs a bunch of arguments, but we are ok with that19:24
JPEWWe are willing to require the container be invoked to get the transparency we want19:25
RPJPEW: thanks for the pointer. I think someone else ran into it19:29
khemRP:  i think my world builds have improved with latest changes it came down to 7hr12mins for qemumips which use to be around 8hrs19:30
khemI wonder if its just the latest changes or VM also got some lift19:30
RPkhem: it should allow the system not to throw as much IO around19:31
JPEWRP: ya. The "fix" has works really well for so long I don't recall the exact circumstances when it was a problem.... I know it was at least a huge deal when users would Ctrl+c a build... That would almost always corrupt pesudo19:31
RPJPEW: this is someone using docker and seeing what looks like pseudo database corruption19:32
RPJPEW: it isn't making much sense but I'm betting it is that again19:32
RPJPEW: I guess in pyrex you can know which processes to wait for. We're not as lucky in the wider world :/19:34
JPEWProbably. There is an option to make pseudo dump the database more often? Might have them try that to see if it goes away. If so, probably there same issue19:35
RPJPEW: I was able to reproduce the issue so I'm experimenting19:35
JPEWYa, the analogy in the real world would be someone using magic sysrq reboot to stop a build ;)19:36
JPEW"just kill everything, I don't care!"19:37
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto19:39
RPJPEW: I've replied in the bug. Shame you weren't in triage as you might have saved me a day on this :/19:45
JPEWSorry, busy week :(19:47
RPJPEW: np. I guess i'm happy it isn't a "real" pseudo bug19:49
RPI think we need to address the pseudo shutdown issue19:49
khemtlwoerner: do you know 5.11 onwards kernels dont boot on rockpi4b ? latest I can get going is 5.1019:55
abellonikhem: rootfs on emmc ?19:55
khemits on SD card20:03
khemI caan see kernel boots but it falls back into systemd emergency shell20:03
vdkhem: hi! I think you're maintaining meta-browser, right? I'm trying to run wayland/chromium on a beaglebone black, but I get a command failed with Ninja. Do you have a working config for wayland-ozone-chromium on beaglebone?20:06
manuel_Hi all. I'm installing bitbaking a python app into my yocto image and am doing "inherit setuptools3" in my recipe. When I start my app in the image, I get an "ModuleNotFoundError: No module named 'pkg_resources'". What am I missing?20:06
vd(I've seen in the commit messages that the beaglebone is used for testing)20:07
*** goliath <goliath!~goliath@user/goliath> has quit IRC (Quit: SIGSEGV)20:07
manuel_"oe-pkgdata-util  list-pkgs | grep setup" tells me there is no setuptools package available in my recipes20:07
*** florian <florian!> has quit IRC (Ping timeout: 252 seconds)20:11
khemvd:  I build for bunch of 64bit ARM plats e.g. rpi4/rockpi4 but have not done 32bit builds for long20:13
abellonikhem: 98e48cd9283dbac0e1445ee780889f10b3d1db6a upstream breaks emmc and possibly sdcard access20:14
abellonifor some reason it has been baclported to earlier stable kernels...20:15
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Read error: Connection reset by peer)20:15
khemabelloni: I think it is the WIC_CREATE_EXTRA_ARGS ?= "--no-fstab-update" that I need20:16
khemI thought it was already applied but seems not yet20:16
khemabelloni: I think 5.14 will comeout ok once I have the wic issue handled20:16
khemlets see20:16
abellonilet me know, it breaks after a few writes on my helios6420:17
vdkhem: would you expect web browser to run on a beaglebone? what would be the "smaller" setup? wayland/chromium?20:20
khemvd: It works ok on qemux86 with 1G RAM so I think it should work on bbb too20:21
khem512M DRAM might be a bit tight without some opts20:21
khemabelloni:  it booted into weston after adjusting wic as above so 5.14.6 booted ok20:24
tlwoernerkhem: i'll have to setup my ci for systemd builds. i've been booting post 5.10 kernels on my rock-pi-4b every day, in fact i was pleasantly surprised to see zeddii's 5.14 kernel booting on it this morning20:30
tlwoerneri'm using sysvinit20:30
tlwoernerkhem: perhaps after i apply it'll work?20:31
tlwoernermarkus reported the same thing and said it works after this patch20:31
*** Vonter <Vonter!~Vonter@user/vonter> has quit IRC (Ping timeout: 246 seconds)20:34
RPJPEW: wondering about as a way to fix this properly20:36
vdkhem: would you recommend firefox or chromium and x11 or wayland on the bbb?20:40
JPEWRP: Ya, that could do it20:40
*** amitk <amitk!~amit@> has quit IRC (Ping timeout: 252 seconds)20:40
*** dgriego <dgriego!~dgriego@user/dgriego> has joined #yocto20:44
*** florian <florian!> has joined #yocto20:51
tlwoernerhow does one output video from the bbb?20:54
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto20:55
tlwoernerah!! that's a micro hdmi beside the SD card :-) i thought it was a mini usb20:55
tlwoernercool, now i can test to see if/how well the dEQP tests run on the bbb20:56
*** sakoman <sakoman!> has quit IRC (Quit: Leaving.)21:01
*** goliath <goliath!~goliath@user/goliath> has joined #yocto21:04
*** arr <arr!~ar@> has joined #yocto21:21
*** Tokamak <Tokamak!~Tokamak@> has quit IRC (Ping timeout: 252 seconds)21:27
*** nateglims <nateglims!~nateglims@> has quit IRC (Quit: Client closed)21:40
*** jmiehe <jmiehe!~Thunderbi@user/jmiehe> has joined #yocto21:54
*** arr <arr!~ar@> has quit IRC (Remote host closed the connection)21:57
*** Net147 <Net147!~Net147@user/net147> has quit IRC (Ping timeout: 246 seconds)21:58
*** xmn <xmn!> has joined #yocto22:00
*** arlen_ <arlen_!> has joined #yocto22:01
*** arlen <arlen!> has quit IRC (Ping timeout: 252 seconds)22:02
*** Net147 <Net147!> has joined #yocto22:09
*** kiran <kiran!~kiran@2607:fea8:5a80:ea0:d49f:da50:802d:5705> has quit IRC (Ping timeout: 252 seconds)22:09
*** Net147 <Net147!~Net147@user/net147> has quit IRC (Read error: Connection reset by peer)22:13
*** leon-anavi <leon-anavi!~Leon@> has quit IRC (Quit: Leaving)22:13
*** Net147 <Net147!> has joined #yocto22:16
*** Net147 <Net147!~Net147@user/net147> has quit IRC (Read error: Connection reset by peer)22:18
*** sakoman <sakoman!> has joined #yocto22:19
*** Net147 <Net147!> has joined #yocto22:21
*** prabhakarlad <prabhakarlad!> has quit IRC (Ping timeout: 256 seconds)22:28
*** vd <vd!> has quit IRC (Quit: Client closed)22:32
*** vd <vd!> has joined #yocto22:42
*** arr <arr!~ar@> has joined #yocto22:46
*** arr <arr!~ar@> has quit IRC (Ping timeout: 265 seconds)22:51
*** Tokamak <Tokamak!~Tokamak@> has joined #yocto22:55
*** Net147 <Net147!~Net147@user/net147> has quit IRC (Read error: Connection reset by peer)23:03
*** Net147 <Net147!> has joined #yocto23:07
*** Net147 <Net147!~Net147@user/net147> has quit IRC (Read error: Connection reset by peer)23:16
*** ant__ <ant__!> has quit IRC (Ping timeout: 265 seconds)23:17
*** Net147 <Net147!> has joined #yocto23:18
*** florian <florian!> has quit IRC (Ping timeout: 252 seconds)23:22
*** Net147 <Net147!~Net147@user/net147> has quit IRC (Read error: Connection reset by peer)23:24
*** Net147 <Net147!> has joined #yocto23:26
*** Net147 <Net147!~Net147@user/net147> has quit IRC (Read error: Connection reset by peer)23:28
*** Net147 <Net147!> has joined #yocto23:28
*** Net147 <Net147!~Net147@user/net147> has quit IRC (Read error: Connection reset by peer)23:29
*** Net147 <Net147!> has joined #yocto23:30
khemvd: yes it should work23:52

Generated by 2.17.2 by Marius Gedminas - find it at!