fitrh has quit [Remote host closed the connection]
jslick has joined #kisslinux
claudia02 has quit [Excess Flood]
ioraff has joined #kisslinux
stjohn has joined #kisslinux
eyepatchOwl has quit [Quit: Connection closed for inactivity]
illiliti has quit [Quit: leaving]
illiliti has joined #kisslinux
progenyx has quit [Quit: progenyx]
illiliti_ has joined #kisslinux
illiliti has quit [Read error: Connection reset by peer]
illiliti has joined #kisslinux
<stjohn>
I'm having a bit of trouble installing KISS on a new laptop and wondered if anyone might recognise the problem. I'm at the step where I rebuild the packages in the chroot and everything goes fine until it rebuilds musl. Then every binary that's dynamically linked suddenly stops working (e.g. cc, perl, openssl) with the following vague message: "I/O error". Static binaries like busybox seem to be fine. I've tried
<stjohn>
d -march=native, -march=goldmont-plus (it's a Pentium Silver N5030 processor), and -march=x86-64. The result is always the same.
<stjohn>
I'm a bit stuck. I haven't had this same problem on other CPUs. It's clearly something to do with musl but I just don't have enough expertise to dig any further. I was hoping someone here might know? Or have suggestions for what I could try next?
<illiliti>
which rootfs do you use?
<stjohn>
I used v2021.7-9 from github.com/kisslinux/repo. Then when rebuilding I tried using both kisslinux/repo and kiss-community/repo as repositories, but both produced the same error at the same stage --- right after rebuilding musl.
<stjohn>
The error comes as soon as the rebuild process moves on to the next package, pigz: "/var/db/kiss/repo/core/pigz/build: line 9: cc: I/O error"
<illiliti>
rebuild musl first and then gcc, then everything else.