tammranil has quit [Remote host closed the connection]
tammranil has joined #yocto
frgo has joined #yocto
frgo has quit [Read error: Connection reset by peer]
frgo_ has joined #yocto
frgo_ has quit [Remote host closed the connection]
Vonter has quit [Ping timeout: 276 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 272 seconds]
druppy has joined #yocto
frgo has joined #yocto
goliath has joined #yocto
frgo has quit [Ping timeout: 260 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 265 seconds]
frgo has joined #yocto
frgo has quit [Read error: Connection reset by peer]
frgo has joined #yocto
rob_w has joined #yocto
Vonter has joined #yocto
ptsneves has quit [Ping timeout: 260 seconds]
Vonter has quit [Ping timeout: 272 seconds]
Vonter has joined #yocto
druppy has quit [Ping timeout: 252 seconds]
mckoan|away is now known as mckoan
rfuentess has joined #yocto
Vonter has quit [Ping timeout: 252 seconds]
<LetoThe2nd>
were there changes to wic since scarthgap? just seeing this for the first time: output: sfdisk: /home/mender/mmc-upstreaming/walnascar/meta-mender-community/my-qemuarm64/build/tmp/work/qemuarm64-poky-linux/core-image-minimal/1.0/deploy-core-image-minimal-image-complete/core-image-minimal-qemuarm64-20250731063503-uefiimg/tmp.wic.wg_oe7jz/mender-uefiimg-202507310636-vda.direct: partition 1: failed to set partition type
Vonter has joined #yocto
zeemate has joined #yocto
ptsneves has joined #yocto
vladest has quit [Remote host closed the connection]
florian has joined #yocto
Jones42 has joined #yocto
<KanjiMonster>
Is there a way to collect task logs during a build? E.g. move them to a dedicated directory outside of TMPDIR, to have them available without having to keep the whole work/ directory
leon-anavi has joined #yocto
rob_w has quit [Remote host closed the connection]
vladest has joined #yocto
geoff__ has joined #yocto
ptsneves has quit [Ping timeout: 245 seconds]
geoffhp has quit [Ping timeout: 240 seconds]
rob_w has joined #yocto
mckoan is now known as mckoan|away
alperak has joined #yocto
berton has joined #yocto
mm_x_ has quit [Quit: Konversation terminated!]
LainIwakura has joined #yocto
<rburton>
KanjiMonster: a quick rsync? make it follow symlinks and ignore files that end in numbers
florian has quit [Ping timeout: 248 seconds]
ptsneves has joined #yocto
ptsneves has quit [Read error: Connection reset by peer]
ptsneves has joined #yocto
<LetoThe2nd>
found it, seems that wic/sfdisk require the full GUID as partition type now (C12A7328-F81F-11D2-BA4B-00A0C93EC93B instead of just EF00)
<RP>
rburton: how does it compare to what is in the autobuilder sources?
<rburton>
it was refreshed yesterday, so the ab probably picked up the previous tarball when tested
<chikku_46>
Hello All , I am facing an issue while building a yocto image for stm32MP157-dk2 board. It fails building the core-image-x11 with a weird issue:
Fanfwe has quit [Quit: ZNC 1.8.2+deb2+deb11u1 - https://znc.in]
<chikku_46>
the host machine is a dell r720 with dual CPU 2695 V2
Fanfwe has joined #yocto
LainIwakura has joined #yocto
lexano has joined #yocto
<rburton>
chikku_46: are you sharing sstate between machines or using the public yocto sstate?
<rburton>
the compiler you're using is trying to run instructions that your cpu doesn't support
lexano has quit [Remote host closed the connection]
lexano has joined #yocto
<chikku_46>
thanks rburton forcomming back. I'm not sharing sstate, nor using public sstate
<rburton>
i'd check your dmesg for hardware failures, or a hint as to what instruction was being executed by what component
Chaser has joined #yocto
<chikku_46>
rburton: Hello
<chikku_46>
rburton: Do you have any other suggestion
<rburton>
it _looks_ like for some reason the compiler that yocto build for your machine, on your machine, is using instructions that your machine does not support. that should not be possible as we don't tune the native build for a particular target.
<rburton>
did you isolate what component is actually causing the illegal instruction?
LainIwakura has quit [Quit: Client closed]
LainIwakura has joined #yocto
<chikku_46>
rburton: I havent isolated the issue yet, but the build was successful on my dell xps laptop with intel 10880h but failed again and again on my dell r720 server with dual 2695 V2 cpus. So I was thinking maybe it's related to host hardware/cpu/platform, i don't know. So needs suggestion.
<chikku_46>
I did multiple clean builds on the server and no change. But it builds successfully multiple time on my laptop
<rburton>
ivybridge is missing a lot of "modern" instructions like avx2, so you might have found a bug in gcc or similar where its using instructions it shouldn't be.
<rburton>
you'll need to find out where the bad instruction is coming from
<rburton>
or treat this as a reason to get a build machine with CPUs that are not 12 years old :)
<chikku_46>
rburton: :) I got this server just for playing with AI. But since it builds almost 3 times faster any yocto build than my farely recent laptop. i was deligating the yocto builds to my server. But it seems thats not a good idea maybe. Once I get some details about the root cause, i might seek helpthen, because I've started learning yocto only coupleof months back. But thanks for this info.
jclsn has quit [Quit: WeeChat 4.6.3]
RyanEatmon has quit [Remote host closed the connection]
RyanEatmon has joined #yocto
florian has quit [Ping timeout: 240 seconds]
wmills_ has joined #yocto
LainIwakura has quit [Ping timeout: 272 seconds]
vladest has quit [Remote host closed the connection]
Xagen has quit [Remote host closed the connection]
Xagen has joined #yocto
Chaser has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
Xagen has quit [Ping timeout: 248 seconds]
rob_w has quit [Remote host closed the connection]
litb has joined #yocto
Daanct12 has quit [Quit: WeeChat 4.7.0]
Chaser has joined #yocto
vladest has joined #yocto
goliath has quit [Quit: SIGSEGV]
ptsneves has quit [Ping timeout: 244 seconds]
<khem>
chikku_46: Can you post the log.do_compile of this recipe ?
<khem>
is it using some sort of prebuilt compiler I wonder, because from name it seems like a baremetal recipe
<rburton>
they need to upgrade the binary gcc to 11.3 at least. and ideally just depend on meta-arm and let that provide the toolchain.
<chikku_46>
rburton: Understoot. Will do that. Thanks. But it seems scarthgap uses 14.2? That might solve the issue do you think?
<rburton>
yeah
<rburton>
use the latest branch that is suitable for your needs
<rburton>
of course it might have regressed, none of our CI has hardware that old
<chikku_46>
rburton: Fine, I'll give it a try.
<rburton>
and - iirc - the 'x86-64-v3' baseline is one generation beyond your hardware
<chikku_46>
Maybe I'll give it a try. It's mostly the gcc cross compiler bug pre 11.3. Or do you think yocto might have regressed as your all your CI has newer gen Processors?
<rburton>
chikku_46: its the binary toolchain release, not related to yocto
<chikku_46>
rburton: gotit.
<rburton>
it shouldn't have regressed as the problem was identified and fixed back in 2022
<chikku_46>
Anyway Thanks rburton & khem for your quick support and suggestion in right direction!!. Have a great day! Cheers.
Chaser has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
sgw has joined #yocto
<jonmason>
RP: Please pull in rburton's bash checksum patch as soon as you can
<chikku_46>
ERROR: Logfile of failure stored in: /mnt/DATA-RAID/embedded-linux/yocto/STM32MP1-X11/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/libglu/9.0.3/temp/log.do_configure.4003468
<rburton>
you'll have to scroll up a bit to find the error, that's just saying that libglu failed
Chaser has joined #yocto
<chikku_46>
C compiler for the build machine: gcc (gcc 13.3.0 "gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0") | C linker for the build machine: gcc ld.bfd 2.42 | C++ compiler for the build machine: g++ (gcc 13.3.0 "g++ (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0") | C++ linker for the build machine: g++ ld.bfd 2.42 | Build machine cpu family: x86_64 | Build machine cpu: x86_64 | Host machine cpu family: arm | Host ma
frgo has joined #yocto
<rburton>
that's not an error message :)
<chikku_46>
C compiler for the build machine: gcc (gcc 13.3.0 "gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0") | C linker for the build machine: gcc ld.bfd 2.42 | C++ compiler for the build machine: g++ (gcc 13.3.0 "g++ (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0") | C++ linker for the build machine: g++ ld.bfd 2.42 | Build machine cpu family: x86_64 | Build machine cpu: x86_64 | Host machine cpu family: arm | Host machine cpu: arm | Target machine cpu family: arm | Target mac
<chikku_46>
hine cpu: arm | Found pkg-config: YES (/mnt/DATA-RAID/embedded-linux/yocto/STM32MP1-X11/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/libglu/9.0.3/recipe-sysroot-native/usr/bin/pkg-config) 0.29.2
<chikku_46>
| Run-time dependency gl found: NO (tried pkgconfig and system) | | ../glu-9.0.3/meson.build:21:9: ERROR: Dependency "gl" not found, tried pkgconfig and system | | A full log can be found at /mnt/DATA-RAID/embedded-linux/yocto/STM32MP1-X11/tmp/work/cortexa7t2hf-neon-vfpv4-poky-linux-gnueabi/libglu/9.0.3/build/meson-logs/meson-log.txt | ERROR: meson failed
<rburton>
so your target doesn't support GL but you're building something that wants GL
frgo has quit [Ping timeout: 276 seconds]
<chikku_46>
rburton: So do you mean I need to add libgl libgles2 package for the target, so it can be found by bitbake in the sysroot?
<rburton>
chikku_46: does your target support OpenGL/GLX, or just GLES? i'd try and figure out why its pulling in libglu and stopping that, as it most likely doesn't.
<chikku_46>
rburton: Yes, the Vivante GC320 GPU in stm32mp157, through the Etnaviv open-source driver, supports OpenGL ES 1.0 and 2.0,
<rburton>
but not GLX right?
<chikku_46>
Hmm. you are right
<ak77>
hello!
<rburton>
whatever youre building wants to pull in libglu which is not support
<ak77>
this is probably asked once a week :S ... is there a way to recompile kernel (actually just single .dts file) and not the whole unpack/compile of the kernel
<ak77>
due to small .dts change from kernel recipe's files folder
frgo has joined #yocto
frgo has quit [Ping timeout: 252 seconds]
<khem>
chikku_46: I think you should disable x11 in distro feature
goliath has joined #yocto
zeemate has quit [Ping timeout: 260 seconds]
leon-anavi has quit [Quit: Leaving]
<khem>
ak77: I would suggest to explore using devshell
Chaser has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
frgo has quit [Ping timeout: 248 seconds]
frgo has joined #yocto
<ak77>
tnx
<chikku_46>
khem: but what if I need X11 support ?
frgo has quit [Read error: Connection reset by peer]
frgo has joined #yocto
frgo has quit [Read error: Connection reset by peer]
Chaser has joined #yocto
frgo has joined #yocto
jerrycash has joined #yocto
frgo has quit [Remote host closed the connection]
frgo has joined #yocto
olani has joined #yocto
frgo has quit [Read error: Connection reset by peer]
<khem>
if graphics driver support is there then it could be about fixing the GLX detection
<chikku_46>
the stm32mp157f-dk2 board from st micro comes set by default with weston(Wayland). So maybe some configuration is needed to support X11
frgo has joined #yocto
ptsneves has joined #yocto
frgo has quit [Ping timeout: 252 seconds]
Jones42 has quit [Ping timeout: 252 seconds]
frgo has joined #yocto
berton has quit [Quit: Connection closed for inactivity]
frgo has quit [Ping timeout: 272 seconds]
Jones42 has joined #yocto
mischief has quit [Ping timeout: 276 seconds]
mischief has joined #yocto
frgo has joined #yocto
goliath has quit [Quit: SIGSEGV]
frgo has quit [Ping timeout: 248 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 240 seconds]
Chaser has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
sgw has quit [Quit: Leaving.]
druppy has joined #yocto
<rburton>
chikku_46: you just need to find out why libglu is being pulled in, and stop that. only a few recipes use it but its very much GLX dependent, which you won't have if your drivers dont' do it
<rburton>
or, don't use X11 if you can help it.
<rburton>
mathieudb: lld v3 sent, feel free to leave it out for a day ;)
<rburton>
khem: posted another little cleanups series, and the v3 of lld. incorporated your dependency fixes, so i hope its good.
Chaser has joined #yocto
<joekale>
Is there a scoping that occurs with datastore variables? in a function I create a variable and add flags to it but the flags are not available in subsequent functions. I receive `Exception: TypeError: 'NoneType' object is not iterable` from a loop in a subsequent function.
<rburton>
joekale: the datastore is unique per task. if you're traversing tasks, you can't just put stuff in d and get it later
<joekale>
Ah ok. Is there a way to create variables that can be saved for later functions or is the datastore the only method of variable storage outside of recipes and class files?
<joekale>
do pre/postfuncs and the task share the same datastore?
jmd has quit [Remote host closed the connection]
frgo has joined #yocto
<joekale>
looks like yes. so a prefunc may be my solution here.
frgo has quit [Ping timeout: 248 seconds]
<kergoth>
khem: Thanks, been a while! Was working on Isar-based stuff (Bitbake for Debian-based images) for a year and a half. How've you been?
goliath has joined #yocto
chikku_46 has quit [Remote host closed the connection]
<rburton>
joekale: if its nominally "the same function" then yeah, pre/post funcs are the best idea
<rburton>
joekale: you can throw data into files in WORKDIR, if you really want to pass state around
zeemate has joined #yocto
druppy has quit [Ping timeout: 265 seconds]
<kergoth>
Can be a pain to make sure that works for both sstate and non-sstate builds though, iirc, if you're communicating between tasks.
<joekale>
rburton: That's what I was thinking I would have to do, but really a prefunc actually makes a fair bit of sense the way I'm doing it. It simplified the logic since I didn't have to worry about which task the function came after and set up task dependencies.
frgo has joined #yocto
frgo has quit [Ping timeout: 252 seconds]
<RP>
jonmason: do we know what changed? As soon as I pull that in, all our CI will break as the autobuilder will not overwrite it without intervention manually (by design)
frgo has joined #yocto
frgo has quit [Ping timeout: 240 seconds]
<rburton>
RP: the commit links to a message where the bash maintainer says he regenerated the tarball
<rburton>
i asked him not to do that again
<RP>
rburton: I did just run a diff, the translations have changed, as has the file ordering in the tarball
<RP>
halstead: are you around?
Chaser has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
frgo has joined #yocto
<halstead>
RP, yes.
<halstead>
Did you see the OOMs today?
<RP>
halstead: am I right in thinking that if I change a download, it won't overwrite an existing file without intervention?
<RP>
halstead: it is a good effort to make in general!
alperak has quit [Quit: Connection closed for inactivity]
frgo has quit [Ping timeout: 240 seconds]
florian has joined #yocto
<halstead>
RP: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 bash-5.3.tar.gz is in place on the main site now. Kicking the mirror sync.
<RP>
halstead: thanks. I've updated master with the change so hopefully the autobuilder will be ok now :)
<RP>
halstead: much appreciated
<halstead>
RP: Is there any need to archive the previous bash-5.3.tar.gz?
qschulz has quit [Ping timeout: 248 seconds]
<RP>
halstead: I have a copy locally just in case but we should be ok
<RP>
halstead: calling it xxx.1 and leaving it on the mirror might be ok too
<halstead>
[257575.854755] Out of memory: Killed process 3012565 (cc1plus) total-vm:2262076kB, anon-rss:2186264kB, file-rss:840kB, shmem-rss:0kB, UID:6000 pgtables:4420kB oom_score_adj:0
<RP>
halstead: it might be the high core count numbers on there confusing our more general limits?
<halstead>
RP: 80 cores / 256GiB on arm64 vs 48 core (96 vCPUs)/ 256GiB on amd64.
<khem>
rburton: I am happy with lld patch
<khem>
I have been testing it in my builds
florian has quit [Ping timeout: 248 seconds]
florian has joined #yocto
<khem>
I will send a series of patches to followup to enable clang in SDK
<khem>
kergoth: Isar, yeah :) well
<khem>
rburton: other clang patches in your branch are they on ml too ?
<kergoth>
Nice to see the toolchain switching bits go in, must be nice not having to carry that
<kergoth>
Ugh, Exception: OSError: [Errno 5] Input/output error: '/work/build/tmp/work/core2-64-poky-linux/gmp/6.3.0/sstate-install-recipe_qa/'. tmp is within a docker volume, wonder why that would get I/o errors.
<RP>
halstead: I'll make a note to have a look tomorrow and see if I can work out is there is any difference
JaMa has joined #yocto
<RP>
halstead: I'm not up to it tonight :(
<halstead>
RP: Of course. I just hoped to make you aware and get any info I could.
<RP>
kergoth: the toolchain switching bits had some interesting implications in bitbake. Had to hack some bits in ways I'm not proud of in the end but kind of made it work
frgo has joined #yocto
<kergoth>
Interesting, I'll have to check out the commits
<kergoth>
Assuming we end up building multiple providers intentionally so at a minimum the warnings about that would have to account for it
<RP>
halstead: my theory doesn't add up since the arm machines have less cores than amd64
<RP>
halstead: and I do appreciate the data, thanks! I just can't make any sense of it. The resource limits should apply equally to both, unless the pressure values work differently on arm
<RP>
I think it was only running an oe-selftest at the time :/
<halstead>
I'll keep an eye on it and open a bug if it repeats.
druppy has joined #yocto
frgo has joined #yocto
<RP>
halstead: thanks, I'll have a think
<RP>
jonmason, rburton: any idea how proc pressure numbers compare aarch64 to amd64?
qschulz has joined #yocto
frgo has quit [Ping timeout: 252 seconds]
florian has quit [Ping timeout: 240 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 240 seconds]
cambrian_invader has joined #yocto
druppy has quit [Quit: druppy]
druppy has joined #yocto
frgo has joined #yocto
druppy has quit [Ping timeout: 252 seconds]
frgo has quit [Remote host closed the connection]
khem has quit [Quit: WeeChat 4.7.0]
frgo has joined #yocto
khem has joined #yocto
frgo has quit [Ping timeout: 252 seconds]
frgo has joined #yocto
frgo has quit [Ping timeout: 248 seconds]
vacasion has quit [Quit: Konversation terminated!]