**** BEGIN LOGGING AT Fri Jul 22 02:59:56 2022
Jul 22 04:13:46 <marex> hey, I ran into a behavior that's not entirely clear to me
Jul 22 04:14:04 <marex> say I have two metalayers, meta-base and meta-board, added into bblayers.conf in that order
Jul 22 04:14:17 <marex> in both, there is a recipe_%.bbappend
Jul 22 04:14:55 <marex> in meta-base, the bbappend contains VAR:remove:distroname = "foo"
Jul 22 04:15:08 <marex> in meta-board, the bbappend contains VAR:append:boardname = " foo"
Jul 22 04:15:38 <marex> what should be the result ? what I see is VAR does not contain foo, even though bitbake -e recipe indicates the :remove is triggered first and :append second
Jul 22 04:15:51 <marex> I would expect the VAR would contain the "foo"
Jul 22 05:56:52 <reichi> hi, i have an qemu-native related issue with our openembedded based distribution when building samba
Jul 22 05:56:55 <reichi> "| qemu-aarch64: Could not open '/lib/ld-linux-aarch64.so.1': No such file or directory"
Jul 22 05:59:40 <reichi> the machine includes arch-arm64.inc, and we do have multilib enable (in case that might somehow influence what qemu)
Jul 22 05:59:47 <reichi> +does
Jul 22 06:04:11 <reichi> It's happening ubuntu bionic @ WSL2
Jul 22 06:17:38 <reichi> ./tmp-glibc/work/aarch64-oe-linux/samba/4.14.13-r0/recipe-sysroot/lib/ld-linux-aarch64.so.1
Jul 22 06:17:46 <reichi> looks like some prefix is empty
Jul 22 06:28:38 <reichi> oh, it's on kirkstone... (totally forgot that)
Jul 22 06:48:15 <RobertBerger> @marex: I would say they VAR should be without "foo" since remove is applied after append.
Jul 22 07:25:32 <marex> RobertBerger: that doesn't seem to agree with the bitbake -e output ordering though , also I cannot find anything in the bitbake docs about :append/:remove ordering
Jul 22 07:27:58 <marex> but assuming that's the case, how is one supposed to re-append variables in layers ?
Jul 22 07:30:16 <RobertBerger> I believe you can not re-append, but only remove ;)
Jul 22 07:31:17 <marex> clearly I need to look into bitbake source, that sounds a bit odd
Jul 22 07:37:45 <RobertBerger> I wrote a little test: https://pastebin.com/QEPTvHxK
Jul 22 07:38:50 <RobertBerger> funny enough bitbake-getvar -r bitbake-trace-var-change VAR_t1 shows append after remove, but that's just searching through the code
Jul 22 07:39:52 <RobertBerger> that's the final result: VAR_t1="val1_t1 (+=)val2_t1 ", meaning remove at the very end
Jul 22 09:21:25 <JaMa> marex: it's true, you cannot undo remove, that's why it's useful to use separate variable for whatever you want to remove and then the next layer can set this variable to empty (to prevent :remove from removing anything)
Jul 22 09:22:03 <JaMa> FOO=foo; VAR:remove = "${FOO}"; and to undo FOO=""
**** ENDING LOGGING AT Sat Jul 23 02:59:56 2022