beneth has quit [Read error: Connection reset by peer]
beneth has joined #yocto
mrpelotazo has quit [Read error: Connection reset by peer]
sakoman has quit [Quit: Leaving.]
mrpelotazo has joined #yocto
olani has quit [Ping timeout: 265 seconds]
alessioigor has joined #yocto
pgowda_ has joined #yocto
thomasd13 has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
goliath has joined #yocto
<mcfrisk>
hi, anyone else seen wic image creation regressions after "linux-yocto/5.10: update to v5.10.141" in kirkstone branch? did something change in the upstream stable kernels?
<mcfrisk>
oh false negative in bisection, something else is causing this..
goliath has quit [Quit: SIGSEGV]
frieder has joined #yocto
nemik has quit [Ping timeout: 265 seconds]
nemik has joined #yocto
Payam has joined #yocto
<mckoan>
good morning
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
zpfvo has joined #yocto
s-f- has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
goliath has joined #yocto
<LetoThe2nd>
yo dudX
<s-f->
Hey experts, I've been fighting this for a couple days and hoping someone may have some insight: The tl;dr is that my build keeps failing with ` do_rootfs: The postinstall intercept hook 'update_font_cache' failed` but none of the solutions I've found by googling seem to work.
<s-f->
- This is a build system for Xilinx hardware, and I'm running it on WSL2 with Ubuntu 20.04. A colleague also using nominally the same setup is able to build successfully, but I haven't been able to.
<s-f->
- I've already relocated the repo to / to hopefully avoid any potential path length issues, and set sysctl `vm.mmap_min_addr = 65536`, both suggestions made by various forum posts about similar issues.
Schlumpf has joined #yocto
leon-anavi has joined #yocto
<s-f->
- Digging into log.do_rootfs, I find that it's failing on `qemu-aarch64 -r 3.14 -E LD_LIBRARY_PATH=/yocto-scripts/build/tmp/work/<snip>/rootfs/usr/lib:/yocto-scripts/build/tmp/work/<snip>/rootfs/lib -L /yocto-scripts/build/tmp/work/<snip>/rootfs -E /yocto-scripts/build/tmp/work/<snip>/rootfs/usr/libexec/fc-cache --sysroot=/yocto-scripts/build/tmp/work/<snip>/rootfs --system-only` where it just prints the qemu
<mckoan>
LetoThe2nd: hey!
<s-f->
usage help text. Note that this command is, indeed, malformed -- there's an extra -E before the path to the fc-cache binary
<s-f->
(I don't know why this happens -- in `sources/core/scripts/postinst-intercepts/update_font_cache` the command is constructed with `-E ${fontconfigcacheenv}`, and sources/core/meta/classes/fontcache.bbclass line 27 sets 'fontconfigcacheenv="${FONTCONFIG_CACHE_ENV}"' and lines 13-17 set FONTCONFIG_CACHE_ENV but this apparently all gets missed somehow)
<mcfrisk>
s-f-: you can try to see "bitbake -e" output for the recipe which has this bug, to see how the bad command line is formed.
<s-f->
mcfrisk: Alright, that dumped a whole lotta stuff, I'll dig through this a bit.
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<s-f->
As an additional note, I already did try just removing the `-E ${fontconfigcacheenv}` from update_font_cache, which just resulted in another error because the fc-cache binary isn't actually there -- even though `bitbake fontconfig` succeeds, the binary ends up at /yocto-scripts/build/tmp/work/cortexa72-cortexa53-xilinx-linux/fontconfig/2.13.1-r0/image/usr/libexec/fc-cache rather than
<s-f->
..../work/<snip>/rootfs/usr/libexec/fc-cache where it's expected to be
grma has quit [Ping timeout: 265 seconds]
<qschulz>
DvorkinDmitry: why do you want to have DTSes in different layers?
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
s-f- has left #yocto [brb]
s-f- has joined #yocto
nemik has quit [Ping timeout: 264 seconds]
nemik has joined #yocto
kanavin has quit [Remote host closed the connection]
kanavin has joined #yocto
grma has joined #yocto
zpfvo has quit [Ping timeout: 264 seconds]
zwhale has joined #yocto
<thomasd13>
When I have set the SRC_URI like this: "https://download.foobar.com/file.tar.gz", can I control somehow where this file get stored and extracted?
<thomasd13>
Currently it seems to get extracted automatically at ${WORKDIR}
<zwhale>
What does it mean to have ARM generic kernel support when using yocto? Does that mean the linux/arch directory is not of importance anymore? Can we from now on select ARM-generic for every arm board in existence? Or did I not get the point of this.
<qschulz>
zwhale: is this question in reaction to some announcement? I feel like there's some context missing :)
zpfvo has joined #yocto
<zwhale>
qschulz Sorry, for example: https://www.admin-magazine.com/News/The-Next-Linux-Kernel-Could-Be-a-Big-Deal where it states that this generic ARM kernel has been in the making for about 10 years. I recently found out about this and don't quite understand it. Does it mean we can use this generic ARM kernel for any ARM architecture and thus any ARM
<zwhale>
board?
<RP>
zwhale: that is the idea. It won't work everywhere straight away but the idea is to have one kernel working everywhere
<Saur[m]>
DvorkinDmitry: There is no .confappend support in bitbake. However, it is possible to emulate it. If you have a mymachine.conf file in your other layer, it can take precedence an be read before the original file. Then you can let it do `require meta-original-layer/path/to/original/mymachine.conf` and that way wrap the original .conf file and thus allow you to extend it. There is one caveat here though: the order of the two layers in the
<Saur[m]>
bblayers.conf file must be well defined, and your "upper" layer must come before the "lower" layer in the BBLAYERS variable (this also assumes their layer.conf does the customary and appends to BBPATH). If you cannot guarantee the order in the bblayers.conf file (and thereby the order in BBPATH), then this method will not work for you.
<zwhale>
RP Sounds great, thanks!
* RP
remembers working on that for the zaurus kernel 15 years ago
<zwhale>
RP What differs so much between x86 and ARM that the one was able to have a generic kernel then and ARM couldn
<zwhale>
Is it the architecture? Not much else that I can think of :(
<zwhale>
Or is there some specific thing that prohibited a similar implementation then?
<RP>
zwhale: many different semi vendors make ARM cpus that have many different features. For x86 the cpus look a lot more similar between Intel and AMD
alessioigor has quit [Quit: alessioigor]
<zwhale>
RP got it, thanks!
alessioigor has joined #yocto
alessioigor has quit [Remote host closed the connection]
alessioigor has joined #yocto
florian has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
Haxxa has joined #yocto
alessioigor has quit [Remote host closed the connection]
alessioigor has joined #yocto
<Haxxa>
Hello, I have a embedded RTU running yocto linux which I have root access to. I want to get inotifyd on it or some notification program but I don't have a build setup
<qschulz>
zwhale: aaaah, I guess this is this arch/arm64/configs/defconfig we're talking about?
<qschulz>
that should work for all platforms officially supported?
<qschulz>
Maybe I should look into this since I'm doing the BSPs for our Aarch64 boards
<zwhale>
qschulz Not sure if that is the one but it definitely seems like that should be the one.
<rburton>
zwhale: a well behaved 64-bit arm system should be able to use the standard kernel defconfig. reality isn't always that way.
florian_kc has joined #yocto
<DvorkinDmitry>
qschulz, because it is the layer for private customer on top of common platform layer.
<DvorkinDmitry>
Saur[m], thank you. Is there are any other place where can I do KERNEL_DEVICETREE += "..." except local.conf and mymachine.conf ?
<qschulz>
DvorkinDmitry: your customers should have a different machine configuration file if they have a different HW platform
<Haxxa>
I'm new to yocto if an OEM sells a machine running yocto linux, is there anyway to run custom applications on the platform without having access to the build platform?
<Saur[m]>
DvorkinDmitry: You can do `KERNEL_DEVICETREE:append:mymachine = " ..."` in any configuration file, e.g., your local.conf.
<rburton>
Haxxa: not if they don't give you the build configuration, as they could have done anything.
<rburton>
Haxxa: shout at them
<rburton>
if the machine has compilers and stuff on it then you can build on target, but that's horrible.
<Saur[m]>
Haxxa: If they sell you the machine, the least you should expect is to get an SDK for it...
<DvorkinDmitry>
qschulz, the SoC and machine are the same, they only have different DTS
<DvorkinDmitry>
qschulz, case they are installed they own module
<DvorkinDmitry>
Saur[m], any configuration, butnot in some recipe?
<Saur[m]>
DvorkinDmitry: Well, variables modified in a recipe are only available to that recipe so if you want them to affect more than one recipe, then it has to be in a configuration file.
<qschulz>
DvorkinDmitry: honestly would be much easier to have them create their own machine, which they can base on top of your base one (with require directive)
<qschulz>
DvorkinDmitry: they just need to set MACHINEOVERRIDES properly and have a require, so that they will reuse the overrides of your base machine without additional work
<qschulz>
it is best practice that including your layers in a build do not fundamentally change the build
<qschulz>
obviously bbappends are kind of the exception
<qschulz>
but basically overriding configuration files is confusing and error-prone
ptsneves has joined #yocto
nemik has quit [Ping timeout: 260 seconds]
nemik has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
starblue has quit [Ping timeout: 246 seconds]
starblue has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
<thomasd13>
What is the "yocto-way" to set a env-variable in my target? Are there more generic solutions as doing this by executing some script (which sets those env variables) after boot?
florian has quit [Killed (NickServ (GHOST command used by florian_kc))]
florian_kc is now known as florian
florian_kc has joined #yocto
<thomasd13>
okay, i take my question back :)
s-f- has quit [Ping timeout: 260 seconds]
Schlumpf has quit [Ping timeout: 252 seconds]
goliath has quit [Quit: SIGSEGV]
florian_kc has quit [Ping timeout: 268 seconds]
Schlumpf has joined #yocto
<DvorkinDmitry>
Saur[m], thank you
<DvorkinDmitry>
qschulz, thank you
zpfvo has quit [Ping timeout: 268 seconds]
<DvorkinDmitry>
If I add KERNEL_DEVICETREE += "..." into linux-%.bbappend of the customer - is it OK?
<DvorkinDmitry>
no need to override machine for him then?
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<qschulz>
DvorkinDmitry: that might be enough
<qschulz>
DvorkinDmitry: if KERNEL_DEVICETREE is only used in the kernel recipe
goliath has joined #yocto
zpfvo has joined #yocto
<qschulz>
also, note that this means your KERNEL_DEVICETREE variable is ALWAYS appended when you include this layer
zwhale has quit [Quit: Client closed]
nemik has quit [Ping timeout: 265 seconds]
nemik has joined #yocto
s-f- has joined #yocto
nemik has quit [Ping timeout: 264 seconds]
nemik has joined #yocto
pgowda_ has quit [Quit: Connection closed for inactivity]
nemik has quit [Ping timeout: 265 seconds]
nemik has joined #yocto
zpfvo has quit [Ping timeout: 246 seconds]
<DvorkinDmitry>
qschulz, yes. Thank you. It works like a charm. in what case KERNEL_DEVICETREE may be used in other recipes? Do you know examples?
<qschulz>
DvorkinDmitry: I don't know, could be in some custom handling inside the image recipe for example
<qschulz>
or signing processes, etc..
zpfvo has joined #yocto
zwhale has joined #yocto
<DvorkinDmitry>
qschulz, the last problem... 2 layers (1'st - general, 2'd for the customer). Several images defined in 1'st (with several common include files for every image). 1 image is for customer, it includes general .inc's and I can't move it to customer's layer case include files can't be found. What would you suggest?
tomzy_0 has joined #yocto
<qschulz>
DvorkinDmitry: use a path relative to the root of the 1st layer
<qschulz>
e.g. include recipes-images/images/my-image-base.inc
<DvorkinDmitry>
qschulz, thank you! it works. what is better to write: "require meta-my1stlayer/recipes-core/images/part1.inc" or "require recpes-core/images/part1.inc" ?
Schlumpf has quit [Quit: Client closed]
<qschulz>
DvorkinDmitry: I think the second one only works?
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
<DvorkinDmitry>
qschulz, exactly. big appologise to taking your time!
<qschulz>
DvorkinDmitry: no worries, happy to help :)
<vvn>
hi there -- if I set PACKAGE_EXCLUDE += "kernel-image-*" all the related packages are pulled out indeed, but if I add PACKAGE_EXCLUDE += "kernel-devicetree", all kernel-module-* get pulled out as well, which is not a desired behavior. Any idea why is that?
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
vladest has quit [Ping timeout: 260 seconds]
prabhakarlad has quit [Quit: Client closed]
Schlumpf has joined #yocto
kscherer has joined #yocto
sakoman has joined #yocto
zwhale has quit [Quit: Client closed]
leon-anavi has quit [Quit: Leaving]
prabhakarlad has joined #yocto
tomzy_0 has quit [Quit: Client closed]
paulg has quit [Quit: Leaving]
dmoseley has joined #yocto
zpfvo has quit [Ping timeout: 252 seconds]
RP has quit [Ping timeout: 248 seconds]
zpfvo has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
RP has joined #yocto
thomasd13 has quit [Ping timeout: 265 seconds]
zpfvo has quit [Ping timeout: 252 seconds]
zpfvo has joined #yocto
frieder has quit [Remote host closed the connection]
alimon has quit [Ping timeout: 260 seconds]
florian_kc has joined #yocto
alimon has joined #yocto
mckoan is now known as mckoan|away
paulg has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
<wmills>
Dumb question: have we moved away from the wiki for release planning? I don't see see anything past 3.1 in the planning TOC. The 4.2 stuff is a google doc recorded in the weekly updates:
<RP>
wmills: We don't really have much planning any more as nobody will commit to anything
<RP>
wmills: I'd happily have a planning process but only if people were actually willing to contribute to doing things
<RP>
wmills: otherwise we have a list of plans with me feeling under pressure to somehow make some of them happen :/
<wmills>
Well the 4.2 document looked OK to me but you can only find it by reading all weekly archive. We should at least put a note on the planning page to look at the weekly logs for anything after 3.1
<wmills>
Should I do that? Or you want to defer to Stephen?
<RP>
wmills: please go ahead, but not every weekly report would mention it
<RP>
wmills: the 4.2 document is just the 4.1 one with the number changed :(
<RP>
wmills: Looks good thanks. We could link to the weekly status reports I guess as they often have the information, that page isn't just the planning info as I was expecting
<cmd>
I'm attempting to build an extensible sdk for my image that targets an aarch64 machine, on an x86_64 host, appending "kernel-devsrc". buildtools-tarball do_populate_sdk fails when it invokes dnf to `install kernel-devsrc`, noting that `package kernel-devsrc-1.0-r0.my_image does not have a compatible architecture`, and then lists a number of needs I'd expect it to have like `/bin/sh`, `python3`,
<cmd>
`/bin/bash`, etc. Is there something I've missed that would cause it to need those but not have them provided?
Payam has quit [Quit: Leaving]
<rburton>
cmd: looks like you're mixing target with nativesdk. don't do that.
<rburton>
if you want to add a target package to the sdk, add it to TOOLCHAIN_TARGET_TASK
otavio has quit [Remote host closed the connection]
dmoseley has joined #yocto
alessioigor has quit [Quit: alessioigor]
dmoseley_ has joined #yocto
PhoenixMage has quit [Ping timeout: 252 seconds]
PhoenixMage has joined #yocto
PhoenixMage has quit [Ping timeout: 252 seconds]
nemik has quit [Ping timeout: 265 seconds]
nemik has joined #yocto
PhoenixMage has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
otavio has joined #yocto
alessioigor has joined #yocto
alessioigor has quit [Client Quit]
<vvn>
Any idea why PACKAGE_EXCLUDE += "kernel-devicetree" pulls out all kernel-module-* as well?
<mischief>
for some reason my kernel recipe fails on do_kernel_configme even though i inherit ccache. i can turn it off but it seems odd that it isn't present in the sysroot?
<mischief>
> /bin/sh: 1: ccache: not found
prabhakarlad has quit [Quit: Client closed]
<rburton>
khem: i have a horrible feeling i'm to blame for your ptest thing
<rburton>
sgw: nice! one of the UX designers at intel in london does bike polo, he was out of action for months after a nasty stick/ankle interaction...
<rburton>
khem: well it's annoying that nobody noticed until now!
<rburton>
khem: well, short-term fix is to make -ptest depend on ptest-runner i guess. that's a trivial dependency.
<rburton>
but that doesn't solve the perl depchain
<rburton>
i didn't like that fix anyway
goliath has quit [Quit: SIGSEGV]
nemik has quit [Ping timeout: 260 seconds]
Minvera has quit [Remote host closed the connection]
nemik has joined #yocto
kscherer has quit [Quit: Konversation terminated!]
hays has joined #yocto
DvorkinDmitry has quit [Remote host closed the connection]
goliath has joined #yocto
florian_kc has quit [Ping timeout: 260 seconds]
nemik has quit [Ping timeout: 252 seconds]
nemik has joined #yocto
nemik has quit [Ping timeout: 265 seconds]
nemik has joined #yocto
florian_kc has joined #yocto
nemik has quit [Ping timeout: 268 seconds]
nemik has joined #yocto
prabhakarlad has joined #yocto
nemik has quit [Ping timeout: 246 seconds]
nemik has joined #yocto
seninha has joined #yocto
florian_kc has quit [Ping timeout: 252 seconds]
seninha has quit [Client Quit]
hays has quit [Ping timeout: 248 seconds]
ak77 has quit [Quit: No Ping reply in 180 seconds.]
ak77 has joined #yocto
seninha has joined #yocto
sakoman has quit [Quit: Leaving.]
GNUmoon has quit [Remote host closed the connection]