jaeger changed the topic of #crux-devel to: CRUX (https://crux.nu/) development channel | Logs: https://libera.irclog.whitequark.org/crux-devel/
farkuhar has quit [Quit: nyaa~]
dlcusa has quit [Read error: Connection reset by peer]
dlcusa__ has joined #crux-devel
dlcusa__ is now known as dlcusa
dlcusa has quit [Read error: Connection reset by peer]
dlcusa has joined #crux-devel
<dlcusa> SiFuh, according to https://cpu-benchmark.org/cpu/amd-fx-9590/
<dlcusa> the 8 cores do not even support hyperthreading. These
<dlcusa> are 8 full SMP cores--SMT should not be even allowed,
<dlcusa> let alone enabled. What I've seen so far is OpenBSD has
<dlcusa> zero SMP issues.
dlcusa has quit [Remote host closed the connection]
dlcusa has joined #crux-devel
<dlcusa_> Oops--sorry, devs.
dlcusa has left #crux-devel [Leaving]
dlcusa has joined #crux-devel
farkuhar has joined #crux-devel
dlcusa has quit [Remote host closed the connection]
aardo has joined #crux-devel
ardo has quit [Ping timeout: 268 seconds]
dlcusa has joined #crux-devel
dlcusa has quit [Remote host closed the connection]
<jaeger> Hrmm, ninja's footprint flaps now between gtest/gmock existing and not
<farkuhar> GazL reported something like that in #crux. Apparently, switching from cmake to configure.py --bootstrap will prevent building any of the gmock/gtest stuff.
<jaeger> Yeah, same issue, just wanted to second it and mention the flapping
<jaeger> Adding "-D BUILD_TESTING=no" seems sufficient in my (limited) testing to work around it
groovy3shoes has joined #crux-devel
groovy2shoes has quit [Ping timeout: 268 seconds]
<beerman> I noticed it yesterday and thought i was just seeing ghosts. I guess either way would be fine