<beerman>
i'm trying the next kernel build. for some reason before, i have been missing specific files (*.dtb or something), I guess thats why the boot crashed.
<pitillo>
8h is fine
<pitillo>
last builds took probably 24h on the rpi3
<beerman>
heh, yeah, there was a jump inbetween those two generations
<beerman>
but with all dependencies this is still a beast on arm
<beerman>
it needs llvm with more build targets (x86_64 nowadays builds all targets by default as this is what upstream considers "a correct build" [don't quote me on that, its somewhere on the bugtracker/website/..])
<beerman>
at least web assembly it is, then needed compiler-rt and clang rebuilt (probably only compiler rt, but not sure)
<beerman>
after that, everything progressed fine with no further changes
<beerman>
i think.. not sure 😄
<pitillo>
llvm and clang both need targets if I remember right
<pitillo>
compiler-rt too I believe
<pitillo>
I have some work done on a external disk... all tests on the chromebook
<pitillo>
I think dbus was corrected there and never pushed it
<pitillo>
I had the same question about llvm targets while checking the build for ARM where we tried to cut them all which weren't needed, jut to avoid problems and compile time
<pitillo>
I don't know if has sense to build for other targets on X86 (usefull for something may be?)
<beerman>
i dunno if i'd expect much problems with additional build targets.. i haven't had any so far and i've been building that for a bit longer like that now, just not on the pi
<pitillo>
true about the problems with additional targets, but if they are needed/used, then it could be possible to be interesting to build them
<pitillo>
but that's far from my knowledge
<pitillo>
for ARM like I said, we tried to remove non needed specific targets for those reasons
<beerman>
like i said, at least web assembly, because firefox will pull in wasi-libc and the other wasi-* ports
<beerman>
neat, i think the kernel build is done and ready, looks like it produced the missing files now, no idea what i did wrong earlier
<pitillo>
forgot to build them?
<pitillo>
or how do you build them? here make Image; make dtbs; make modules; make install
<beerman>
i tried to follow the official instructions
<beerman>
well, will see, i will reboot that kernel soon
<pitillo>
great
<beerman>
we will see, eh? 😄 I have been fooled before, I might be fooled again
<pitillo>
bit by bit
<beerman>
first: coffee
<pitillo>
rpi4 has a very good kernel support
<pitillo>
yeah
<beerman>
tim@eloxal ❯ uname -a
<beerman>
Linux eloxal 6.1.1-v8+ #2 SMP PREEMPT Thu Dec 29 14:45:44 CET 2022 aarch64 GNU/Linux
<beerman>
🤓
<beerman>
pitillo: any reason for not using cmake for libarchive?
<pitillo>
yes, we used autotools for libarchive to get the release
<pitillo>
cmake and ninja loop dependencies
<beerman>
ah, ok, shouldn't hurt to switch over once this is done
<pitillo>
that's the point
<beerman>
i need to disable xz module compression for our kmod
<beerman>
after that i can share the kernel, probably, if somebody wants it
<beerman>
i will start to make my own default config and shed most of these modules after that