<khem>
JaMa: GLIBCXX_3.4.32 will be supported with gcc 13.2+ and its not released yet
lukma has quit [*.net *.split]
perdmann has quit [*.net *.split]
polprog has quit [*.net *.split]
Zappan has quit [*.net *.split]
Net147 has quit [Quit: Quit]
Net147 has joined #yocto
Net147 has joined #yocto
Net147 has quit [Changing host]
<baaash>
Hi there, I'm new to Yocto. I just automated the process to run a Poky build, using Ansible, and wondered roughly how long I can expect the build to take? Currently running this build in a Linux Container with 8 CPU cores and 16GB RAM allocated, on my virtualization server... been an hour so far.
Zappan has joined #yocto
sakoman has quit [Quit: Leaving.]
<khem>
baaash: welcome to community ! hope you will have fun using yocto. Now the time it takes depends on few things. 8CPU + 16GB is an average machine and ok to use to build yocto however, dont know your storage perhaps its SSD, yocto builds can be disk bound
Thorn has quit [Ping timeout: 248 seconds]
<khem>
it also depends on how complex your image it
<khem>
e.g. if you are build core-image-minimal or core-image-sato-sdk times will vary a lot
<khem>
since it has to build a complex stack when buildins Sato image
<khem>
Good thing is we reuse build artifacts so subsequent builds will be faster
<baaash>
Hi Khem, thanks for the reply and the welcome. I can easily apply more resources to this if you think I'm a bit lean on it. Was just curious whether I should wait around for this build to finish or leave it going overnight and come back to it tomorrow. Couldn't find any indication online is all and didn't really want to hang around indefinitely
<khem>
yeah let it go through maybe
<baaash>
i should also mention.. i'm just building the sato image, with no customizations. it's my first run so before i mess with anything I wanted to see what was there
<khem>
and then see if you can adjust resources and improve build times, you might have to do hit and trial
<khem>
yeah sato image is fairly large
<khem>
it might take 2-3 hrs on system like yours
<baaash>
cool.. i can do that. thanks for the feed back. I have another 100 cores I can throw at it, but will see how long this one takes before i start tweaking.
bps has joined #yocto
bps has quit [Changing host]
bps has joined #yocto
<khem>
yeah you need a balance between compute/memory/storage
<khem>
usually 2GB of RAM per core and a fast SSD is a roughly good system
<khem>
e.g. if you have 100core system so perhap 256G of RAM is good
tgamblin has quit [Read error: Connection reset by peer]
tgamblin has joined #yocto
<landgraf>
JaMa: Is 13.1 stable enough in gentoo? /me think about updating
florian__ has joined #yocto
florian__ is now known as florian
florian has quit [Ping timeout: 240 seconds]
xmn has quit [Ping timeout: 240 seconds]
xmn has joined #yocto
camus has quit [Quit: camus]
tenko[m] has quit [Remote host closed the connection]
alessioigor has joined #yocto
florian has joined #yocto
<JaMa>
landgraf: I had few build issues like with qtwebengine, but it all got fixed in portage tree already, so it's reasonably stable for me, but e.g. this new snapshot is a bit annoying and you need to use the updated uninative also for older builds like kirkstone
<JaMa>
landgraf: check the bugzilla tracker to see if there is something you really require and cannot fix yourself