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
nerdboy has quit [Ping timeout: 260 seconds]
nerdboy has joined #yocto
nerdboy has quit [Changing host]
nerdboy has joined #yocto
Thorn has joined #yocto
florian_kc has quit [Ping timeout: 268 seconds]
rber|res has quit [Remote host closed the connection]
rber|res has joined #yocto
qschulz has quit [Read error: Connection reset by peer]
khazakar has quit [Quit: Connection closed for inactivity]
qschulz has joined #yocto
lexano has quit [Ping timeout: 264 seconds]
goliath has quit [Quit: SIGSEGV]
davidinux has quit [Ping timeout: 246 seconds]
davidinux has joined #yocto
nerdboy has quit [Ping timeout: 255 seconds]
nerdboy has joined #yocto
Thorn_ has joined #yocto
Thorn has quit [Ping timeout: 260 seconds]
ablu has quit [Read error: Connection reset by peer]
ablu has joined #yocto
khem has quit [Quit: Connection closed for inactivity]
sakman has quit [Ping timeout: 256 seconds]
jclsn has quit [Ping timeout: 246 seconds]
jclsn has joined #yocto
simonew has quit [Ping timeout: 256 seconds]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
jmiehe has quit [Ping timeout: 255 seconds]
jmiehe1 has joined #yocto
jmiehe1 is now known as jmiehe
jmiehe has quit [Quit: jmiehe]
Ram-Z has quit [Ping timeout: 260 seconds]
alessioigor has quit [Quit: alessioigor]
alessioigor has joined #yocto
Ram-Z has joined #yocto
amitk has joined #yocto
otavio has quit [Ping timeout: 260 seconds]
ecdhe has quit [Read error: Connection reset by peer]
ecdhe has joined #yocto
jmd has joined #yocto
vladest has quit [Quit: vladest]
vladest has joined #yocto
bhstalel has joined #yocto
leon-anavi has joined #yocto
ptsneves has joined #yocto
leon-anavi has quit [Quit: Leaving]
bhstalel has quit [Ping timeout: 256 seconds]
ptsneves has quit [Ping timeout: 264 seconds]
florian_kc has joined #yocto
ak77 has joined #yocto
<Xogium> anyone else ever hit an issue with wic in wks.in format where having a file ending with a digit makes the convertion process from wks.in to .wks crash, claiming it can't find the .wks generated file ?
<Xogium> if I take out the digit and give it a different name with just letters it works fine
<yocton> The new CVE summary by recipe is really nice! But wouldn't it be more useful at the top (like an executive summary)?
florian_kc has quit [Ping timeout: 255 seconds]
goliath has joined #yocto
florian_kc has joined #yocto
<kanavin> RP: it has to be triggered by 'go: update 1.20.12 -> 1.20.13'? note that both local and cdn tests fail, but only for arm, which makes me think it's another hashequiv effect.
kpo has quit [Ping timeout: 268 seconds]
Vonter has quit [Ping timeout: 252 seconds]
Vonter has joined #yocto
florian_kc has quit [Ping timeout: 252 seconds]
Estrella has quit [Read error: Connection reset by peer]
Estrella has joined #yocto
<rber|res> @Xogium: does this file exist? /home/xogium/simplest-yocto-setup/build/tmp-glibc/work/stompduck2-oe-linux-gnueabi/kiss-image/1.0-r0/stompduck2.wks
<Xogium> rber|res: nop
<Xogium> it's like the generation of the .wks explodes
<Xogium> yeah
<rber|res> and I assume that this work
<rber|res> s
<Xogium> which is is why I'm very confused
<Xogium> simplest-yocto-setup thing comes from bootlin
<Xogium> their original repo has stompduck.wks.in
<rber|res> and this works?
<Xogium> which I literally cp over and named stompduck2.wks.in
<Xogium> no tweaks at all and it blew up wic like that
<rber|res> and you changed the machine config or so?
<Xogium> yeah, stompduck.wks-in is absolutely fine
<Xogium> the way bootlin does it is setting wks_file this way
<Xogium> ./conf/machine/include/common.inc:WKS_FILE = "${MACHINE}.wks.in"
<Xogium> I have literally no explanation for why this happens
<rber|res> so you changed the machine to stompduck2?
<Xogium> yeah
<rber|res> Hmm
<rber|res> try to keep the old machine and just to change the WKS_FILE to something hardcoded
<Xogium> well more like made a new one based on stompduck.conf, which used stm32mp157c-dk2 instead of stm32mp157a-dk1, but that's the idea
<Xogium> that was just a basic test run as I wanted to see if this could be made to work
<Xogium> yeah good idea. I'll do that
<rber|res> small steps ;)
<Xogium> yep !
<Xogium> hang on
<Xogium> yep that works
<Xogium> if I hardcode to stompduck2.wks.in
<Xogium> that is super strange
<rber|res> well ;)
<Xogium> well, this is kirkstone, so maybe there's been some kind of fix for this upstream ?
<rber|res> I never noticed anything with wic files ending with a number so far. But I don't have many of those ;)
<Xogium> yeah
<rber|res> Now try the following:
<Xogium> feels like something blows up when trying to expand the machine variable
<rber|res> Use your new machine config and use instead of 2 -> two
<Xogium> alright, trying
<Xogium> works good
<Xogium> it doesn't mind letters
<rber|res> Hmm spooky
<rber|res> I think it's rather the MACHINE variable, which does not like numbers
<rber|res> and not the wks.in filename
<Xogium> right
<Xogium> that would make sense
<Xogium> but wait
<Xogium> no that can't be, the machine for generic x86 is called genericx86
<rber|res> No this should not be a problem, since this works: /meta-raspberrypi/conf/machine/raspberrypi4.conf
<Xogium> and that too
<rber|res> yep
<Xogium> so wks_file blowing up, somehow, when you use the machine variable ?
* Xogium scratches their head
<Xogium> I don't understand why, but it feels like that is exactly what might be going on
<rber|res> you could try to run bitbake with DDD to see lots of debug. Maybe there you can see what happens
<Xogium> good idea
<Xogium> rber|res: https://paste.xogium.me/BT.log if you feel like helping with that giant log
<Xogium> I tried grepping for things but yeah I'm still too new to yocto to know really what to look for, I reckon
OnkelUlla has quit [Remote host closed the connection]
<Xogium> maybe bitbake -e could give a clue, too ?
<rber|res> I don't see any errors except for those at the end.
<Xogium> this is SO weird :D
<Xogium> maybe I should see what wks_file gets expanded to in bktbake -e
<Xogium> *bitbake
<Xogium> hmm no this gets set orpperly apparently
<rber|res> I think it's expanded to /home/xogium/simplest-yocto-setup/build/tmp-glibc/work/stompduck2-oe-linux-gnueabi/kiss-image/1.0-r0/stompduck2.wks
<Xogium> *properly
<Xogium> unless I'm a dummy and I can't read the outout of bitbake -e ;)
<Xogium> seems like everything is fine to me
<rber|res> You could also look into temp/run.do_image_wic
<rber|res> WKS_FILES="stompduck2.wks.in kiss-image.wks"
<Xogium> right, what about it ?
<rber|res> that's from your log
<rber|res> and I think the run.do_image_wic script should do the magic
<rber|res> and fail ;)
<rber|res> So you could try to run the run.do_image_wic script
<rber|res> and see what happens
xmn has joined #yocto
<rber|res> I will be off for some hours - have fun debugging this ;)
<Xogium> yeah... It's got something wrong, but I don't quite know what that might be
<Xogium> aye, thanks for the help so far !
<rber|res> can you execute the run shell script and paste the output?
<Xogium> yep doing that now
<Xogium> erm
<Xogium> https://paste.xogium.me/B_.txt the script itself works fine
<rber|res> yes, but
<rber|res> wks="/home/xogium/simplest-yocto-setup/build/tmp-glibc/work/stompduck-oe-linux-gnueabi/kiss-image/1.0-r0/stompduck.wks"
<rber|res> not stompduck2.wks
<Xogium> whyyy ?
<Xogium> and good point I missed that
<rber|res> cache?
<Xogium> hmm
<Xogium> maybe ?
<rber|res> make sure that you have stompduck2.wks defined in the machine
<rber|res> bitbake -e <your image> | grep ^WKS_FILE=
<rber|res> and
<rber|res> after you are sure the right WKS file is defined try
<Xogium> WKS_FILE="stompduck2.wks.in"
<rber|res> bitbake --no-setscene <your image>
<Xogium> what does that do ? Disables the cache ?
<rber|res> Do not run any setscene tasks. sstate will be ignored and everything needed, built.
<rber|res> inspect the temp/run.do_image_wic script afterwards
<Xogium> I'm rather confused here, why would I need to do that ? I thought that it would do this on its own normally ? But sounds like you're right
<rber|res> WKS_FILE="stompduck2.wks.in" should be in there
<Xogium> I'll run it
<rber|res> Well we are trying to find the problem ;)
<Xogium> right, but what I meant here is I thought bitbake would have done that without me asking for it
<rber|res> At the moment what you tell me is, that in run.do_image_wic we have the wrong WKS file
Thorn has joined #yocto
<Xogium> right
<rber|res> So either your configuration is wrong, or it is from a previous run, where you had the other file.
<Xogium> hmm yeah I reckon the latter is more likely than the former
<rber|res> Assuming your config is right it could come from the cache. Where else?
<Xogium> yeah it's definitely the cache
<Xogium> it's doing way more things
Thorn_ has quit [Ping timeout: 255 seconds]
<rber|res> Now it has to do a lot of things
<Xogium> but now I'm confused
<rber|res> Why?
<rber|res> We told it not to use the cache
<rber|res> There are lots of things which it should normally take from the cache.
<Xogium> I thought that by changing the machine variable, then it would build the system for the new machine or reuse the cahce, for pieces it can reuse and only doing the actual compilation for the new machine if that is required
<Xogium> so I'm not sure how my wsk file got messed up
<Xogium> *wks
<rber|res> yes - in case software bugs would not exist - in a parallel universe ;)
<Xogium> fair point
<Xogium> ^^
<Xogium> well, will let this run and see what happens then
<rber|res> OK
<rber|res> I'll be off for now
<Xogium> the weirdest thing is that if I use another name from stompduck2 like... I don't know, stompducktwo, then there is no issue
<Xogium> rber|res: sure, thanks ! :D we'll keep digging at it when you're back if you feel up to helping
lexano has joined #yocto
<Xogium> rber|res: darn ! This doesn't appear to a state cache related problem. I get exactly the same error
sakman has joined #yocto
florian_kc has joined #yocto
jmiehe has joined #yocto
pabigot has joined #yocto
pabigot has quit [Remote host closed the connection]
pabigot has joined #yocto
vladest has quit [Remote host closed the connection]
florian_kc has quit [Ping timeout: 276 seconds]
xmn has quit [Ping timeout: 264 seconds]
vladest has joined #yocto
simonew has joined #yocto
jmiehe has quit [Quit: jmiehe]
Kubu_work has joined #yocto
florian_kc has joined #yocto
flom84 has joined #yocto
florian_kc has quit [Ping timeout: 240 seconds]
Haxxa has quit [Quit: Haxxa flies away.]
Haxxa has joined #yocto
olani- has joined #yocto
ptsneves has joined #yocto
khazakar has joined #yocto
kpo has joined #yocto
flom84 has quit [Ping timeout: 264 seconds]
<kanavin> RP: I will file a bug, I have some findings that should be recorded there
ptsneves has quit [Ping timeout: 255 seconds]
<RP> kanavin: thanks, I didn't really have time to dive into that one
Kubu_work has quit [Quit: Leaving.]
florian_kc has joined #yocto
jmd has quit [Remote host closed the connection]
amitk has quit [Ping timeout: 264 seconds]
simonew has quit [Quit: Konversation terminated!]
chep has quit [Ping timeout: 264 seconds]
chep` has joined #yocto
chep` is now known as chep
alessioigor has quit [Quit: alessioigor]
Vonter has quit [Ping timeout: 256 seconds]
Vonter has joined #yocto
florian_kc has quit [Ping timeout: 240 seconds]
khazakar has quit [Quit: Connection closed for inactivity]
Vonter has quit [Ping timeout: 256 seconds]
Vonter has joined #yocto
khazakar has joined #yocto
kpo has quit [Remote host closed the connection]
xmn has joined #yocto
sakman1 has joined #yocto
sakman has quit [Ping timeout: 252 seconds]
sakman1 is now known as sakman
florian_kc has joined #yocto
goliath has quit [Quit: SIGSEGV]
dmoseley has joined #yocto
dmoseley_ has quit [Ping timeout: 264 seconds]
dgriego_ has joined #yocto
dgriego has quit [Ping timeout: 264 seconds]
Ad0 has quit [Ping timeout: 260 seconds]
dgriego_ has quit [Quit: Computer going to sleep]
Ad0 has joined #yocto
dgriego has joined #yocto