jaeger changed the topic of #crux-arm to: CRUX-ARM 3.6 Released! - http://crux-arm.nu/Documentation/ReleaseNotes3-6 | Logs: https://libera.irclog.whitequark.org/crux-arm/
CrashTestDummy has joined #crux-arm
CrashTestDummy3 has quit [Ping timeout: 252 seconds]
CrashTestDummy2 has joined #crux-arm
CrashTestDummy has quit [Ping timeout: 252 seconds]
rlittl01 has joined #crux-arm
CrashTestDummy3 has joined #crux-arm
CrashTestDummy2 has quit [Ping timeout: 252 seconds]
CrashTestDummy has joined #crux-arm
CrashTestDummy3 has quit [Ping timeout: 252 seconds]
<frinnst> anybody been able to compile latest gcc natively on a rpi (3 in this case)?
<frinnst> locks up at the same place each time I try
<frinnst> glibc also fails to build since a year or so
<frinnst> arm64
<frinnst> hard lockups
<frinnst> tried to point a big fan directly at it yesterday but it had failed this morning :-)
<beerman> frinnst: not me, sorry. I got rid of my pi3 a few weeks ago. What are your errors though?
rlittl01 has quit [Read error: Connection reset by peer]
rlittl01_ has joined #crux-arm
<beerman> oh sorry, was on mobile earlier.. hard lockups.. its what i had with my pi. it would lock up randomly, sometimes after 2 days on 100% cpu utilization...
<frinnst> I even only build using one core
<beerman> i suppose it runs stable otherwise?
<pitill0> frinnst: last gcc and glibc builds here were on december 2020
<pitill0> I'll make a -fr on glibc which will take less than gcc...
<pitill0> on the way.....
<pitill0> $ uptime 18:42:44 up 153 days, 15:40, 1 user, load average: 0.16, 0.04, 0.01
<frinnst> it doesnt really do much, just bridges two physical network with ntp, apcupsd and email alerting
<frinnst> but yeah, stable
<frinnst> that's the last line.. multiple attempts
<pitill0> strange.... it seems to be frozen....
<pitill0> here it's still building...
<pitill0> ummmm 10.3 ?
<pitill0> yeah, it's fine
<pitill0> xD
<pitill0> frinnst: where are you building stuff?
<frinnst> local storage
<frinnst> 32gb microsd