jaeger changed the topic of #crux-devel to: CRUX (https://crux.nu/) development channel | Logs: https://libera.irclog.whitequark.org/crux-devel/
ivandi has quit [Quit: WeeChat 3.8]
ivandi has joined #crux-devel
chrcav has joined #crux-devel
Romster has quit [Ping timeout: 265 seconds]
Romster has joined #crux-devel
SiFuh has joined #crux-devel
SiFuh_ has quit [Ping timeout: 248 seconds]
<beerman> Romster what exactly are you updating? cani help with something particular?
<Romster> i've remade my buildroot but something is messed up still... https://gist.github.com/therealromster/24fd1311a799fdc8a00691006d2cdab1
<Romster> never seen this before
<Romster> everything else in core built fine
<beerman> no idea
<beerman> jue libffcall has a race condition with too many cores, make -j 1 works around that for me on those xeons
pitillo has quit [Quit: leaving]
pitillo has joined #crux-devel
<jue> beerman: will add -j1
<beerman> cheers
groovy2shoes has quit [Quit: Leaving]
chrcav has quit [Ping timeout: 276 seconds]
chrcav has joined #crux-devel
<jaeger> What do you folks think about the recent ML post about ninja not respecting MAKEFLAGS? Generally I'd prefer to keep the number of vars introduced to pkgmk.conf minimal but if this sorts out all ports that use ninja it might be worth considering
<jaeger> This is what was causing annoyance with qtwebengine, too. I need to test the change with that
groovy2shoes has joined #crux-devel
<beerman> jaeger makes you wonder if it makes sense "to hide it" so it doesn't bother anybody. It could be the same value as MAKEFLAGS always. then again, it wouldn't bother me, but for some reason i don't have the same problem with qtwebengine (what else is affected?)
mnkydeth has quit [Remote host closed the connection]