<jaeger>
Would kinda like to give cross-compiling from scratch a try again, it's been a long time since I looked at that. I remember always running into challenges with cross-compiled stuff finding libs and includes during cross-compiling, as well as funk with rpaths, etc... from what I understand now, with modern toolchains the sysroot is supposed to take care of those issues. Is that a correct understanding?
<jaeger>
For example, linux kernel doesn't have dependencies on libs, that's easy to cross compile... but then pkgutils needs libarchive, so that would be cross-compiled into the sysroot?
<pitillo>
yes jaeger you are right. Those problems were the reason to let it in a side from my part. Cross-building was a pain because checking binaries, they always had host systems leafovers/trash...
<pitillo>
Cross gives another system understanding, but for me, it's only usefull for little/small/nopowerfull devices and/or for learning
<pitillo>
building a cross core system isn't a very big pain, doing it with bigger ports with more dependencies it is
pitillo has quit [Ping timeout: 255 seconds]
pitillo has joined #crux-arm
<beerman>
did anyone update ffmpeg on aarch64 yet? I am currently on my way and test if my changes to the opt version compiles on the pi4
<beerman>
sweet, worked fine 🙂 didn't took as long as i expected it to, too
<pitillo>
not here beerman
<pitillo>
if you want to create a PR I canbit here too on the rpi3
<beerman>
pitillo: which PR? It worked fine for me without modifications 🙂
<pitillo>
beerman: understood, sorry xD
<pitillo>
re-reading helps
<beerman>
no worries 🙂
<beerman>
i am currently rewriting the zsh completion file for prt-get, after writing a Pkgfile vim syntax file 😄
<beerman>
the zsh completion file had several problems, i have them almost all fixed
<beerman>
the vim syntax isn't perfect yet either, but its better than nothing 😄