<r0ni>
compiler-rt keeps failing with a file not found on "SipHash.h" which seems from llvm, i've rebuilt llvm twice now... i dunno why this dep-chain consistently fails for me on arm64, but when i started I thought I should probably pkgrm them all first, cuz i knew this would happen lol
_whitelogger has joined #crux-arm
dlcusa_ has joined #crux-arm
dlcusa has quit [Ping timeout: 256 seconds]
<beerman>
r0ni: third-party llvm package is needed, are you not building from the official port?
<r0ni>
all official ports, in a container no less
<beerman>
if its still not properly solved i'll need to look into it
<beerman>
oh
<beerman>
its my bad
<r0ni>
i was about to run the sysup on my base install, to see if it happens there as well, figured i'm sure i can remove the few pkgs and just rebuild new ones in the end if thats the case
<beerman>
have a look at x86_64 opt and see that you need to add llvms third-party archive and move it to $SRC/third-party
<beerman>
then it will build
<beerman>
i can fix it after work, or pitillo beats me to it
<r0ni>
if I were smart I'd setup distcc or something between all the devices and really be McQueen then
<beerman>
whats keeping you from it
<r0ni>
I'd have to be running them all at once
<r0ni>
the macmini always stays on, but i need to give that poor macbook a rest, built all of qt6, llvm, rust, and whatever else today... the poor boy has no fan! lol
<r0ni>
BUT for packages building I think i'm going to use both just building different things to kinda meet up in the end
<beerman>
hehe yeah
<beerman>
well, they dont need to always be running. if a server is unavailable, it will complain about it, but it wont fail the build
<r0ni>
true, maybe I shall. Would be nice to see how it all performs as a build farm
<beerman>
yeah :)
<beerman>
dont expect ground breaking results
<beerman>
but it certainly helps
<r0ni>
I pushed a PR for compiler-rt
<r0ni>
I can get that far with git now, i'm learning ;)
<beerman>
🚀
<beerman>
it'll have to wait for pitillo or me though
<beerman>
it'll be merged later, thanks :)
<r0ni>
i had to edit the pkgfile anyway, figure i might as well use it as practice pushing things :)
<beerman>
great :) it certainly helps!
<pitillo>
woot woot.... got it on armhf finally|~|@~|@
<pitillo>
Time Taken : 13 hours, 58 minutes, 28.94 seconds
<pitillo>
Build Status : Succeeded
<pitillo>
give me some time and I'll review the PR and squash/merge it :D
<pitillo>
ah! btw, we have an all green on scheduled jobs from last night, that's cool to see for breakfast
<pitillo>
the multiarch stuff only creates different containers beerman, so I doubt it will cover our needs.... those are all specific arch containers, no multi arch containers.... for what I understand on a fast check, it's a wrapper to deploy different arches containers, but not really multi arch containers
<pitillo>
thanks r0ni|~@|~@! PR merged and .signature updated :D
<beerman>
yeah, nice
dlcusa_ is now known as dlcusa
<r0ni>
pitillo: i see you added the xorg-font-bh-ttf, which is great! I know I have a few more xorg ports that need the same treatment, I just have to find my list of them
<pitillo>
if you find it I can check it out and give you a hand.... at the moment, I'm building xfce4 on the Opi5Max so I've found two
<r0ni>
actually might just be 2 of em, but yeah they are found during the xfce install, im' about to go thru my package builds and see which are missing from xorg so I assume I'll find the others then
<r0ni>
xorg-font-cursor-misc
<r0ni>
xorg-font-daewoo-misc
<r0ni>
both need --build flag
<r0ni>
i can do PRs if need be... i'm just looking thru them
<r0ni>
first let me see if i can manage to update the rpi5 kernel without messing up ;)
<r0ni>
learning the bare minimum is working, I'm a git pro now! heh
<cruxbridge>
<pitillo (@pitillo:crux.nu)> If you create the PR I’ll squash them for sure
<cruxbridge>
<pitillo (@pitillo:crux.nu)> I don’t remember if I told you about xfce4…. Amazing job btw&—)/)
<r0ni>
I did PR for the first one... and thank you! It still needs a little fine tuning for wayland but overall I'm pretty happy with it
<cruxbridge>
<pitillo (@pitillo:crux.nu)> Ummmm I tested it on wayland and got it working fine on the RV2 (RiscV)…. Enlightenment wasn’t for example (I didn’t dig too much for it)
<r0ni>
oh yeah it works, but there should be some flags in a port for notifiying users if they dont have wayland installed it won't build the needed stuff
<r0ni>
(looks at clutter port) oh maybe it was added already... well that was 8 months ago... I'm forgetful
<r0ni>
i have notes I need to look at eventually... eventually I'm going to go thru the repos and officially migrate everything off github while cleaning anything up along the way
<pitillo>
great, that sounds like a plan
<r0ni>
debating on installing forgejo on my server so I can learn a little better where I'm in control of my mistakes ;)
<pitillo>
ummm it's like github, gitea?
<pitillo>
both PR are squashed r0ni|~@|#~@
<r0ni>
I see, thx!
<r0ni>
and yes forgejo is a fork of gitea
<pitillo>
so why not use directly gitea? I'm just curious
<r0ni>
seems most of the dev team ended up there and i'm not sure of the drama involved but it looks a little nicer to my eyes lol
<pitillo>
jajajaja
<pitillo>
good to know
<r0ni>
that and I can use gitea on crux.nu so seeing whats diff in forgejo for mostly no reason but why not lol
<r0ni>
forgejo runs on codeberg, I know that
<r0ni>
codeberg may be the drama for all i know
<pitillo>
no way to run it by your own?
<r0ni>
oh no I mean forgejo is the backend for codeberg, yeah you can run the server locally, that's just the company funding it, etc