LetoThe2nd changed the topic of #yocto to: Welcome to the Yocto Project | Learn more: https://www.yoctoproject.org | Community: https://www.yoctoproject.org/community | IRC logs: http://irc.yoctoproject.org/irc/ | Having difficulty on the list, with someone on the list or on IRC, contact Yocto Project Community Manager Letothe2nd | CoC: https://www.yoctoproject.org/community/code-of-conduct
khazakar has quit [Quit: Connection closed for inactivity]
florian_kc has quit [Ping timeout: 255 seconds]
dmoseley_ has joined #yocto
dmoseley has quit [Ping timeout: 260 seconds]
dmoseley_ has quit [Quit: ZNC 1.8.2 - https://znc.in]
dmoseley has joined #yocto
tokamak has quit [Quit: ZNC 1.8.2+deb2build5 - https://znc.in]
tokamak has joined #yocto
Vonter has quit [Ping timeout: 260 seconds]
Vonter has joined #yocto
davidinux has quit [Ping timeout: 252 seconds]
davidinux has joined #yocto
dmoseley has quit [Ping timeout: 255 seconds]
camus has joined #yocto
dmoseley has joined #yocto
dmoseley has quit [Ping timeout: 256 seconds]
dmoseley has joined #yocto
dmoseley has quit [Ping timeout: 268 seconds]
dmoseley has joined #yocto
dmoseley has quit [Ping timeout: 255 seconds]
dmoseley has joined #yocto
dmoseley has quit [Ping timeout: 252 seconds]
dmoseley has joined #yocto
ablu has quit [Read error: Connection reset by peer]
ablu has joined #yocto
dmoseley has quit [Ping timeout: 276 seconds]
dmoseley has joined #yocto
dmoseley has quit [Ping timeout: 252 seconds]
dmoseley has joined #yocto
jclsn has quit [Ping timeout: 255 seconds]
jclsn has joined #yocto
Thorn_ has joined #yocto
Thorn has quit [Ping timeout: 256 seconds]
dmoseley has quit [Ping timeout: 252 seconds]
dmoseley has joined #yocto
amitk has joined #yocto
dmoseley has quit [Ping timeout: 255 seconds]
dmoseley has joined #yocto
OnkelUlla has joined #yocto
dmoseley has quit [Ping timeout: 260 seconds]
dmoseley has joined #yocto
ctraven has quit [Ping timeout: 260 seconds]
jmd has joined #yocto
ctraven has joined #yocto
dmoseley has quit [Ping timeout: 260 seconds]
dmoseley has joined #yocto
sng has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
sng has joined #yocto
olani- has quit [Ping timeout: 246 seconds]
alessioigor has joined #yocto
JaMa has quit [Ping timeout: 256 seconds]
JaMa has joined #yocto
chep` has joined #yocto
chep has quit [Ping timeout: 252 seconds]
chep` is now known as chep
chep` has joined #yocto
dmoseley has quit [Ping timeout: 264 seconds]
chep has quit [Ping timeout: 256 seconds]
chep` is now known as chep
khazakar has joined #yocto
dmoseley has joined #yocto
sakman has quit [Ping timeout: 260 seconds]
jmd has quit [Remote host closed the connection]
rob_w has joined #yocto
dmoseley has quit [Ping timeout: 256 seconds]
goliath has joined #yocto
khem has joined #yocto
wooosaiiii has quit [Quit: wooosaiiii]
amitk_ has joined #yocto
wooosaiiii has joined #yocto
linfax has joined #yocto
amitk has quit [Ping timeout: 255 seconds]
xmn has quit [Ping timeout: 246 seconds]
xmn has joined #yocto
dmoseley has joined #yocto
mckoan|away is now known as mckoan
Kubu_work has joined #yocto
frieder has joined #yocto
zpfvo has joined #yocto
prabhakarlad has joined #yocto
vladest has quit [Read error: Connection reset by peer]
vladest has joined #yocto
vladest has quit [Client Quit]
vladest has joined #yocto
vladest has quit [Ping timeout: 260 seconds]
ptsneves has joined #yocto
ykrons has joined #yocto
zpfvo has quit [Ping timeout: 264 seconds]
dmoseley has quit [Ping timeout: 256 seconds]
dmoseley has joined #yocto
ptsneves has quit [Ping timeout: 240 seconds]
khazakar has quit [Quit: Connection closed for inactivity]
zpfvo has joined #yocto
vladest has joined #yocto
florian has joined #yocto
xmn has quit [Ping timeout: 240 seconds]
khem has quit [Quit: Connection closed for inactivity]
dmoseley has quit [Ping timeout: 256 seconds]
dmoseley has joined #yocto
jumpinJack has joined #yocto
leon-anavi has joined #yocto
khazakar has joined #yocto
amitk_ has quit [Ping timeout: 252 seconds]
amitk has joined #yocto
schtobia has quit [Quit: Bye!]
schtobia has joined #yocto
dmoseley has quit [Ping timeout: 255 seconds]
dmoseley has joined #yocto
zkrx has quit [Ping timeout: 256 seconds]
mvlad has joined #yocto
zkrx has joined #yocto
dmoseley has quit [Ping timeout: 268 seconds]
dmoseley has joined #yocto
pvogelaar has joined #yocto
dmoseley has quit [Ping timeout: 268 seconds]
mbulut has joined #yocto
dmoseley has joined #yocto
mbulut has quit [Client Quit]
dmoseley has quit [Ping timeout: 264 seconds]
dmoseley has joined #yocto
otavio has joined #yocto
vladest has quit [Ping timeout: 246 seconds]
dmoseley has quit [Ping timeout: 276 seconds]
dmoseley has joined #yocto
* LetoThe2nd stupid question: when using python-pip in-target, what is the trick to have the built-in packages recognised?
<rburton> hm they should be automatically
<rburton> unless pip is being terrible, as is usual
<LetoThe2nd> rburton: hrhr that would have been my guessed summary of the situation too.
dmoseley has quit [Ping timeout: 246 seconds]
<rburton> LetoThe2nd: does it just not recognise the system ones at all?
<LetoThe2nd> rburton: I'll try to find out. /me is in relay mode here, not much of a python guy.
<LetoThe2nd> rburton: *sigh* life is complicated. python-dbus from meta-python2 is involved, and the questionable image gone. Thanks for the pointer that at least on python3-pip it is supposed to work.
<LetoThe2nd> rburton: I'll give you a beer and a glitter sticker in return ;-)
<rburton> just firing a build now to test
<rburton> this is something we should validate...
<rburton> easy enough to throw pip into the SDK images and check it does the right thing
vladest has joined #yocto
vladest has quit [Remote host closed the connection]
dmoseley has joined #yocto
vladest has joined #yocto
<LetoThe2nd> rburton: k thanks!
<jumpinJack> python -m build
<jumpinJack> python -m installer dist/*.whl
<jumpinJack> puts them in /usu/local
Ad0 has quit [Ping timeout: 264 seconds]
Ad0 has joined #yocto
<jumpinJack> Hi guys, is it possible to create a big image (around 5GB) that will all run in ram
<rburton> presumably its being loaded from somewhere, so why not use that somewhere as a read-only rootfs?
<jumpinJack> thanks, i'll try that
<rburton> a kernel initramdisk is implemented as a CPIO archive you glue to the end of the kernel, and then kernel unpacks it entirely into a tmpfs on boot. It's intended to be small and switch to a proper filesystem quickly. If you've 5GB of filesystem, just mount it.
dmoseley has quit [Ping timeout: 264 seconds]
<LetoThe2nd> rburton: can I has 7.8GB kernel+initramfs pleez?
<rburton> no go away
<LetoThe2nd> rburton: boring.
<landgraf> rburton: you can use such approach to run few Xen domains running without shared block devices/locks/pv driver etc. Don't ask me why...
<rburton> landgraf: surely in that case the initramfs part is pretty lean (megs not gigs)
<landgraf> yes, it was ~300MB in my case iirc
<landgraf> but maybe you want to put few docker containers inside :-D
* landgraf is running away
<rburton> oh god stop :)
<jumpinJack> I need a full dev machine emulating complex embedded hardware based on intel xeon
<jumpinJack> including nvidia drivers and cuda
zpfvo has quit [Ping timeout: 264 seconds]
zpfvo has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<Xogium> so... back with my issue where using an hardcoded WKS_FILE = "stompduck2.wks.in" works, but using WKS_FILE = "${MACHINE}.wks.in" with a machine called stompduck2 makes the build fail with this error: https://paste.xogium.me/BI.txt
<Xogium> bitbake -e and bitbake -DDD aren't very clear, but the run.do_wic_image script can be ran manually, except that it uses the wrong wks file to create the image, stompduck.wks.in and not stompduck2.wks.in
Guest81 has joined #yocto
<Guest81> Hello, Did someone know how to enable the "timeout" feature from "coreutils" package ?
<Xogium> disabling state cache didn't help, and I still hit the issue
<Xogium> if I rename the machine to something with no digit, like mytestmachine, there is no such issue
<Xogium> or even stompducktwo
dmoseley has joined #yocto
<Xogium> fwiw this is kirkstone
<Xogium> and not poky, using the simplest-yocto-setup repo from bootlin, which is mostly combining oe core with a few other layers to make a distro out of
dmoseley has quit [Client Quit]
<Guest81> I don't understand the ALTERNATIVE_PRIORITY stuff in coreutils package and I don't know if it's the source of my problem or not.
<Guest81> I have coreutils package added to the image
<Guest81> In the recipe I see bindir_progs = " ..... timeout...."
<Guest81> But unfortunately I don't have "timeout" on my image
chep has quit [Quit: ZNC 1.8.2 - https://znc.in]
chep has joined #yocto
davidinux has quit [Ping timeout: 252 seconds]
davidinux has joined #yocto
prabhakarlad has quit [Ping timeout: 250 seconds]
prabhakar has quit [Ping timeout: 264 seconds]
tgamblin has quit [Ping timeout: 260 seconds]
Estrella has quit [Quit: No Ping reply in 180 seconds.]
<Guest81> I don't find any help on google :/
<Guest81> Someone know how to add "/usr/bin/timeout" (provided by "coreutils") in the image ? IMAGE_INSTALL:append = "coreutils" is not enough
Estrella has joined #yocto
pidge has joined #yocto
prabhakarlad has joined #yocto
tgamblin has joined #yocto
jclsn has quit [Ping timeout: 255 seconds]
jclsn has joined #yocto
Minvera has joined #yocto
prabhakarlad has quit [Ping timeout: 250 seconds]
<rburton> LetoThe2nd: well pip on target isn't _totally_ broken, I installed these as packages in the rootfs https://www.irccloud.com/pastebin/gAhIT7R0/
* LetoThe2nd rburton: I'm inclined to interpret that as "works for reasonably recent and maintained python packages." thoughts?
<rburton> proper recipes should do the right thing and just work.
<rburton> i didn't try installing anything else yet
<LetoThe2nd> rburton: thanks, much appreciated!
<rburton> installing works, although it drops stuff into /usr/lib which i'm thinking we should ban, like debian does.
zpfvo has quit [Ping timeout: 256 seconds]
zpfvo has joined #yocto
zpfvo has quit [Ping timeout: 264 seconds]
zpfvo has joined #yocto
<Guest81> Anyone know how to add "timeout" command from coreutils package to yocto image ?
<Guest81> IMAGE_INSTALL:append = "coreutils" is not enough
<rburton> its part of my coreutils package.
<rburton> $ oe-pkgdata-util find-path **/timeout*
<rburton> coreutils: /usr/bin/timeout.coreutils
frieder has quit [Ping timeout: 255 seconds]
jmiehe has joined #yocto
sakman has joined #yocto
dmoseley has joined #yocto
<Ad0> there's no limitation on dashes after do_compile_prepend_ for example=
<Guest81> :/ So you don't have to specificly set something to get it working ?
<Ad0> like do_compile_prepend_blah-blah-blah() {
<yocton> Xogium: just started to build your setup. I always wanted to try this stuff :). Let's see if I can reproduce/find the problem
<Ad0> I can't find the error, I created a copy of a machine but "Exception during build_dependencies for IMAGE_BOOT_FILES" and bb.data_smart.ExpansionError: Failure expanding variable IMAGE_BOOT_FILES, expression was bootfiles/* ${@make_dtb_boot_files(d)} ${@bb.utils.contains('RPI_USE_U_BOOT', '1', 'uImage u-boot.bin;kernel7.img boot.scr', 'uImage;kernel7.img', d)} dt-blob.bin
<Ad0> which triggered exception TypeError: sequence item 30: expected str instance, NoneType found
<Ad0> it has to be some syntax error I can
<Ad0> I can't see or something, sorry for the multiline
<Ad0> I diffed the machine configs and there are no differences
<rburton> Guest81: "it"? you should replicate the oe-pkgdata-util call to verify that your build is the same as mine.
<rburton> Guest81: and remember that :append means adding leading whitespace, " coreutils" not "coreutils"
<Ad0> oh I missed one thing "RPI_KERNEL_DEVICETREE_OVERLAYS" probably has something wrong with it
<Guest81> In my Yocto build I don't have your result
<Guest81> The most likely is bash-completion-extra: /usr/share/bash-completion/completions/timeout
<Guest81>  but nothing provided by coreutils
<rburton> Guest81: dare i ask what release of yocto you're using?
<Guest81> But on another project I have and that's my problem. The project don't have the same bsp, but they have the same yocto version (hardknott)
<rburton> well, its entirely possible one of the BSPs is messing with coreutils and breaking it
<rburton> but also hardknott is EOL
<Guest81> But in the coreutils recipe there are some ALTERNATIVE stuffs
<Guest81> So I'm asking if there is something to set
<rburton> nope
<Guest81> Ok, so I will have to search what is the difference between the two BSP's and find if there is a bbappend or patch that break things.
<Guest81> thanks.
<rburton> oe-pkgdata-util list-pkg-files -r coreutils will list what coreutils built, so you can see what went into it
<Xogium> yocton: try out the thing from bootlin ? You can ;) I've just added a different machine called stompduck2, setup the compatible for it in TF-A build, selected it in local.conf
<Xogium> for the record I'm on ubuntu 22.04
<Xogium> oh yeah and added a defconfig and such for kernel as well of course
<Xogium> I did what I could with the help provided by someone yesterday, but in the end I couldn't figure out why it blows up
xmn has joined #yocto
dmoseley has quit [Ping timeout: 256 seconds]
frieder has joined #yocto
frieder has quit [Ping timeout: 256 seconds]
dmoseley has joined #yocto
jumpinJack has quit [Ping timeout: 250 seconds]
frieder_ has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
jmiehe has quit [Quit: jmiehe]
rob_w has quit [Remote host closed the connection]
goliath has quit [Quit: SIGSEGV]
<yocton> Xogium: I've also copied stompduck2.wks.in in meta-kiss/wic
linfax has quit [Ping timeout: 252 seconds]
ad__ has joined #yocto
ad__ has quit [Changing host]
<Xogium> yocton: let me see
<Xogium> I really don't understand why here it fails
prabhakarlad has joined #yocto
<yocton> can you push what you did somewhere?
prabhakar has joined #yocto
<Xogium> yocton: I can make a pastebin, would that be good enough ?
<yocton> yes
<Xogium> alright, give me a sec
frieder_ has quit [Ping timeout: 260 seconds]
<Xogium> yocton: https://paste.xogium.me/BL.txt I don't think I forgot anything there, the conf/machines/stompduck2.conf, followed by the TF-A fixup, followed by the wic file, then the local.conf
<Xogium> I'm sure it is something dumb
<Xogium> ignore the wks_file I hardcoded in the config, that was a test
<Xogium> I forgot to remove it after checking that if I hardcode it that worked
marka has quit [Quit: ZNC 1.8.2 - https://znc.in]
Guest81 has quit [Quit: Client closed]
marka has joined #yocto
<Xogium> I'm blind btw so I may have missed something either when making my own config or when checking your own try over
frieder_ has joined #yocto
frieder_ has quit [Remote host closed the connection]
<yocton> Xogium: Nope, still works : I've integrated your content in my branch : https://github.com/ycongal-smile/simplest-yocto-setup/tree/stompduck2
<yocton> Maybe something about the name of the copied file instead of their content?
<Xogium> I don't think so... machines/stompduck2.conf and wic/stompduck2.wks.in
vmeson has quit [Read error: Connection reset by peer]
<rburton> whoops I think i just made NIST think I'm DoSing them
vmeson has joined #yocto
florian has quit [Quit: Ex-Chat]
<yocton> rburton: worse, you tell other to send them mail, you are DDoSing them! :p
<yocton> Xogium: Try : bitbake -fc write_wks_template kiss-image; bitbake kiss-image (that should force the creation of the missing file)
<rburton> yocton: i think amazon EFS has broken locking and I just set a cluster of machines all downloading the database at once
<yocton> ouch
<rburton> whoopsie!
<rburton> hm.
<rburton> we can tell the cve fetcher to use a NVD API key by setting NVDCVE_API_KEY. But our CI configuration is public and I'd prefer not to hardcode that into the kas files.
<rburton> I guess I could assign it to @d.getVar("BB_ORIGENV"]).getVar("NVDCVE_API_KEY")
<rburton> yes, NVDCVE_API_KEY = "@{d.getVar("BB_ORIGENV").getVar("NVDCVE_API_KEY") or ""}" works
<rburton> wrong paste. ${@...}
jmd has joined #yocto
mckoan is now known as mckoan|away
Neurobit has joined #yocto
<Neurobit> Has anyone else run into a exception during expansion since the "mage_types: fix multiubi var init" commit was applied. Personally was bumping my kirkstone poky layer to the latest tag 4.0.15 and see it now. It looks like the patch doesn't account for the MULTIUBI_BUILD variable not existing so it returns None which you can't call split() on. I
<Neurobit> think this is an issue but I can currently work around it by setting MULTIUBI_BUILD to an empty string.
zpfvo has quit [Remote host closed the connection]
<mischief> what layer/recipe would be providing lldb?
<rburton> mischief: it would be part of the clang recipe in meta-clang
<mischief> i wonder how many megabytes that's going to be.. :-)
<rburton> $lots
<rburton> mega? hahahaha.
<rburton> (llvm git repo is 2.3gb)
<mischief> i mean, in the image
<mischief> but our global license config seems to block binutils anyway. gotta fix that at some point
<Xogium> yocton: I'll try that
<Xogium> yocton: it works. But why did I have to do that ? I really don't understand
<Xogium> are you also building on ubuntu 22.04 ?
prabhakarlad has quit [Ping timeout: 250 seconds]
simonew has joined #yocto
vladest has quit [Remote host closed the connection]
simonew62 has joined #yocto
kanavin has quit [Read error: Connection reset by peer]
simonew has quit [Ping timeout: 250 seconds]
<yocton> Xogium: I'm on Debian 12 but my hypothesis is that you changed MACHINE and the wks file dependency tracking failed in that case (that sound like a bug). To clear your build, do a "bitbake -ccleansstate kiss-image" and you should be good to go
kanavin has joined #yocto
florian_kc has joined #yocto
simonew62 has quit [Ping timeout: 250 seconds]
simonew has joined #yocto
vladest has joined #yocto
<Xogium> the crazy thing is I can reproduce this every single time
<Xogium> if I use a machine name without digits, like mytestmachine instead of stompduck2, it works
<Xogium> the second I do stompduck2, boom
Haxxa has quit [Quit: Haxxa flies away.]
Haxxa has joined #yocto
<simonew> Xogium, what do you try? I could try to reproduce if that helps
<Xogium> simonew: I tweaked the simplest-yocto-setup stuff from bootlin to make a different machine, basically, called stompduck2
<Xogium> and seemingly every time I try to build the image wic fails to run. It doesn't create the stompduck2.wks based on stompduck2.wks.in
<Xogium> and I had to force bitbake to create the file
<yocton> I'll try to replicate this on poky to create a proper bug report
<Xogium> yeah :/ I don't think it will be easy to reproduce
<Xogium> I'm starting to wonder if it blew up because I built stompduck first, added stompduck2, then tried to build it.
<Xogium> I doubt it
<Xogium> and this only happens when I use the machine variable. Hardcoding the filename makes it work without a problem
<Xogium> which is also super strange
<simonew> you mean MACHINE in local.conf?
<Xogium> yes
<Xogium> if I set WKS_FILE to the machine variable, it blows up. If I set a hardcoded filename it works ok
<Xogium> in both cases, there is a stompduck2.wks.in file
<simonew> Ok, started a build li,ke that, Ill check after dinner
<simonew> On another note, have you checked what changes with and w/o hardcoded file name for the env? Sth like bitbake -e kiss-image > outfile for both situations and then a diff of those files
<Xogium> yeah I did that
Neurobit has quit [Ping timeout: 250 seconds]
<Xogium> I can't spot any difference, but I might have missed this
<Xogium> however the one thing that got me confused is that run.do_wic_image script uses stompduck.wks.in, not stompduck2.wks.in
<Xogium> when ran manually
Neurobit has joined #yocto
Neurobit has quit [Client Quit]
<tlwoerner> i know i've come across this before, but i can't seem to remember the magic required
<tlwoerner> my u-boot build puts stuff into $TMPDIR/deploy/images/$MACHINE/ that are needed for wic
<tlwoerner> but on a fresh build if u-boot comes from sstate, the things in the deploy directory aren't put there
<tlwoerner> how do i make that work?
<simonew> WKS_FILE = "${MACHINE}.wks.in" was fine for me image was build i.o.
<simonew> otherwhise I have just copy pasted the machine conf, the kernel conf, the wks.in, and added the line for COMPATIBLE_MACHINE for the atf
<simonew> And set the MACHINE to stompduck2 in local.conf
<tlwoerner> i bet it revolves around the fact my u-boot bbappend is using ${DEPLOY_DIR_IMAGE} ?
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
<tlwoerner> i seem to vaguely remember there's a better variable name to use in this case
<Xogium> simonew: yeah that is literally what I did as well, and yocton did. I'm the only person hitting this problem
<Xogium> it's just crazy
<simonew> Ok what a bummer
<simonew> some racecondition? no idea atm
<tlwoerner> ahh! DEPLOYDIR instead of DEPLOY_DIR_IMAGE
<Xogium> simonew: yeah I really have no ideas either
Dracos-Carazza has quit [Quit: ZNC 1.8.2 - https://znc.in]
Dracos-Carazza has joined #yocto
jmiehe has joined #yocto
mvlad has quit [Remote host closed the connection]
amitk has quit [Ping timeout: 246 seconds]
Vonter has quit [Ping timeout: 255 seconds]
jatedev has joined #yocto
Vonter has joined #yocto
khem has joined #yocto
<khem> RP: seeing this with devtool after inherit_defer https://snips.sh/f/gfLYkg1CAw
<RP> khem: looks like something we'd need to debug and fix :/
<khem> I am trying to convert inherit native in qemu-native.inc to inherit_defer
<khem> lets see
alessioigor has quit [Ping timeout: 260 seconds]
astlep5504018 has quit [Ping timeout: 240 seconds]
<RP> khem: btw, I did run the glibc upgrade through the autobuilder. qemumips is an issue
* RP sends mail
<khem> oh cool
astlep5504018 has joined #yocto
<khem> AssertionError: 1 != 0 : Xorg does not appear to be running
<khem> perhaps it segfaulted .. are there some more logs siphoned from the qemu run
<khem> and alt images seems to crash in systemd
<khem> systemd[1]: systemd-networkd.service: Failed with result 'core-dump'
<RP> khem: there are earlier errors I think
<khem> which log ?
leon-anavi has quit [Remote host closed the connection]
jmiehe1 has joined #yocto
jmiehe has quit [Ping timeout: 264 seconds]
jmiehe1 is now known as jmiehe
jmiehe has quit [Quit: jmiehe]