<
r0ni>
everytime i build clang 17.0.2 it makes libs named 17.0.1... something is amiss with that
<
r0ni>
i've cleared ccache and still the same happens
<
beerman>
i'd rather check the distfiles
<
beerman>
llvm pr is not merged yet
<
beerman>
if you try and update clang while llvm is still on another version "you gonna have a bad time mkay"
<
r0ni>
ahh so what youre saying is the clang update is a bit premature
<
beerman>
well, if llvm is at 17.0.1 and you try to build 17.0.2.. yeah?
<
r0ni>
i had not noticed llvm was still at 17.0.1... updates run and i don't watch unless there's failures. I had assumed they were updated already
<
r0ni>
its waiting to merge into traffic I see
<
beerman>
yeah :D the pi3 takes too long compiling that crap
<
r0ni>
i can imagine. I quit using mine a while back, it just didn't seem to be much good at anything lol
crux-arm-bot has joined #crux-arm
<
crux-arm-bot>
[ crux-ports-opt-arm64 ]: llvm: 17.0.1 -> 17.0.2 (#37)
crux-arm-bot has left #crux-arm [#crux-arm]
crux-arm-bot has joined #crux-arm
crux-arm-bot has left #crux-arm [#crux-arm]
<
crux-arm-bot>
[ crux-ports-opt-arm64 ]: llvm: update .signature
<
pitillo>
sorry beerman , I integrated compiler-rt and thought llvm was in the same commit, but itnwasn't
<
pitillo>
now it must be all right
<
beerman>
it was one pr :D i think thats fine
<
pitillo>
not sure if there is pending any other PR
<
pitillo>
chromebook finished
<
pitillo>
=======> Building '/home/pkgmk/pkg/llvm#17.0.1-1.pkg.tar.xz' succeeded.
<
beerman>
pitillo we need a signature update for compiler-rt and then it should be fine
<
beerman>
no other pr that i know of :)
<
pitillo>
let me check
crux-arm-bot has joined #crux-arm
<
crux-arm-bot>
[ crux-ports-opt-arm64 ]: compiler-rt: update .signature
crux-arm-bot has left #crux-arm [#crux-arm]
<
pitillo>
thx beerman! updated compiler-rt... I believe I'm mixing compiler-rt with gcc-fortran... my bad
<
beerman>
ah :D no worries
pitill0 has quit [Quit: leaving]
pitillo_ has joined #crux-arm
pitillo_ is now known as pitill0
sajcho has joined #crux-arm
<
sajcho>
humble question: is anyone running crux on a riscv64 device?
sajcho has quit [Client Quit]
<
jaeger>
Not yet. I've played with the visionfive 2 a tiny bit but not that far
sajcho has joined #crux-arm
<
sajcho>
Thank you for your response. I have a repository so I wanted to share my experience. By the way, I also run Starfive Vision2.
sajcho has quit [Client Quit]
<
beerman>
man, rust 1.73.0, i am really not trying to make pitill0s pi cry but my hands are tied
<
jaeger>
I also have a mango pi thingy but I would not want to do a lot of compiling on that :D