12:26 <cruxbot> [opt/3.7]: firefox-bin: updated to version 127.0.2

12:26 <cruxbot> [opt/3.7]: btrfs-progs: updated to version 6.9.1

12:26 <cruxbot> [opt/3.7]: fakeroot: updated to version 1.35.1

12:26 <cruxbot> [opt/3.7]: imagemagick: upated to version 7.1.1-34

12:26 <cruxbot> [opt/3.7]: dialog: upated to version 1.3-20240619

12:26 <cruxbot> [core/3.7]: python3-setuptools: updated to version 70.1.1

12:26 <cruxbot> [core/3.7]: linux-pam: added pam_lastlog2 to common-session

18:07 <jaeger> Can anyone compile qtwebengine or qt6-webengine on their hardware without disabling cores? Genuinely curious. Even on my laptop with 8GB RAM and 4c/8t I can't build it without disabling half of them.

19:31 <serpente> true jaeger, i usually limit my jobs to 4 or 5 to compile browser engines, let it be webkit qtwebengine or even firefox, i got so bored of this that i only compile webkitgtk and use firefox-bin, librewolf actually

20:06 <jaeger> Does that actually work with qtwebengine/qt6-webengine? It's been a little while since I looked but it seems to ignore JOBS/MAKEFLAGS -j settings entirely, hence the need to disable cores/threads using chcpu

20:14 <r0ni> i let qt6-webengine go with everything i can throw at it and it uses every bit of cpu/ram in the process... i've never been able to get it to build limiting things

20:15 <r0ni> that said, i'm building on arm64 anyway

20:15 <jaeger> The problem seems to be it using more RAM than is available based on the number of CPU cores. It gets oomkilled

20:15 <r0ni> yep, zram has helped me out there

20:17 <r0ni> i've got 12gb ram / 8gb zram / 8gb swap setup and during final build time it uses almost every bit of it all. its a punishing build

20:18 <r0ni> this is a vm tho, so limits, etc apply so i'm working in constraints

20:20 <ppetrov^> jaeger, so the issue is running out of RAM, the more cores you have? I have 8 cores and 64GB of RAM, so I'll give it a try next time I update

20:20 <jaeger> yes, exactly

20:21 <jaeger> I have 3 configurations I've tested recently: 1) laptop with 8GB/8T, 2) desktop with 32GB/16T, 3) threadripper with 32GB/32T

20:21 <jaeger> I have to disable 4, 8, and 24 cores/threads respectively to build with those specs

20:22 <jaeger> So I guess 32GB is roughly enough for 8 cores (this is not very scientific, obviously)

20:25 <ppetrov^> will let you know how it hoes

20:25 <ppetrov^> *goes

20:25 <jaeger> sounds good

20:26 <jaeger> I should do some more thorough testing, maybe, and watch memory usage during the builds

20:27 <ppetrov^> hmm,... actually I have a port for qt6-pdfwidgets which provides just a tiny subset of what qt6-webengine includes (which was all I needed). I remember building qt6-webengine taking forever on all 8 cores, but I did not run out of RAM

21:54 <jaeger> Some related anecdata, a build on the laptop just failed qt6-webengine with 4C, 8GB RAM, 2GB swap

21:54 <jaeger> Maybe for grins I'll try adding swap until it succeeds, heh

21:54 <cruxbot> [contrib/3.7]: pandoc-bin: 3.2 -> 3.2.1

21:54 <cruxbot> [contrib/3.7]: parallel: 20240522 -> 20240622

21:54 <cruxbot> [contrib/3.7]: python3-pydantic-core: 2.19.0 -> 2.20.0

21:54 <cruxbot> [contrib/3.7]: qutebrowser: 3.2.0 -> 3.2.1

21:56 <cruxbot> [opt/3.7]: lua: 5.4.6 -> 5.4.7

21:56 <cruxbot> [opt/3.7]: libassuan: 3.0.0 -> 3.0.1

22:00 <jaeger> I have some 1U servers with more RAM in them that aren't used currently, I wonder what it would look like against 64G/96G as well

22:16 <cruxbot> [contrib/3.7]: grafana: 11.0.0 -> 11.1.0

22:25 <cruxbridge> <tim> fwiw, I used to build it on the pi4 (until it stopped building for another error) and I can build it on at least 3 workstations (desktops and notebooks) + inside my lxc container

22:25 <cruxbridge> <tim> all cores and more, thanks to distcc :P

22:42 <jaeger> What's the ratio of RAM to cores?