16:45 <crux-arm-bot> [ core-arm64/3.8 ]: Adapt information to gitea server instead of github

16:47 <crux-arm-bot> [ opt-arm64/3.8 ]: Adapt information to gitea server instead of github

16:49 <crux-arm-bot> [ xorg-arm64/3.8 ]: Adapt information to gitea server instead of github

16:51 <crux-arm-bot> [ raspberrypi3-arm64/3.8 ]: Adapt information to gitea server instead of github

16:54 <crux-arm-bot> [ raspberrypi4-arm64/3.8 ]: Adapt information to gitea server instead of github

16:57 <crux-arm-bot> [ raspberrypi5-arm64/3.8 ]: Adapt information to gitea server instead of github

17:00 <crux-arm-bot> [ pine64-arm64/3.8 ]: Adapt information to gitea server instead of github

17:05 <crux-arm-bot> [ orangepi3b-arm64/3.8 ]: Adapt information to gitea server instead of github

19:14 <hermit_crab> Hello. How to cross-compile on CRUX-arm 3.8?

19:16 <cruxbridge> <pitillo (@pitillo:crux.nu)> Hey! We are not cross compiling anymore….. probably since 3.0…. I think sepen had on his GitHub repositories some cross stuff

19:18 <hermit_crab> Well. How to compile gcc more faster? - it demand many time for me.

19:18 <cruxbridge> <pitillo (@pitillo:crux.nu)> It takes a lot of time….

19:18 <cruxbridge> <pitillo (@pitillo:crux.nu)> Which device?

19:19 <hermit_crab> My device is a raspi 5 16G.

19:19 <cruxbridge> <pitillo (@pitillo:crux.nu)> Gcc probably shouldn’t be a problem, as it’s part of core and there are pre built updated packages at got.crux.nu/system/crux-rootfs

19:20 <cruxbridge> <pitillo (@pitillo:crux.nu)> Wow…. And it demands many time?!? How much time does it take for you?

19:21 <beerman> hermit_crab: did you configure pkgmk.conf to set an apropriate number for jobs?=

19:21 <hermit_crab> Someone has precompiled for me:m #crux-arm well. 3 hours already much time for me :_|

19:21 <cruxbridge> <pitillo (@pitillo:crux.nu)> LOL

19:21 <hermit_crab> lol

19:21 <beerman> https://git.crux.nu/system/crux-rootfs/releases/tag/3.8-updated there is updated arm64 packages here

19:22 <beerman> but frankly, compiling just takes time. it goes faster if you dont look ;)

19:23 <cruxbridge> <pitillo (@pitillo:crux.nu)> And it goes faster on binary distros 😂

19:23 <beerman> well

19:24 <beerman> it does but where is the fun in not looking then?

19:24 <cruxbridge> <pitillo (@pitillo:crux.nu)> Jaajajajajaa

19:24 <cruxbridge> <pitillo (@pitillo:crux.nu)> 3h…. I’d sign to get that timing on many devices….

19:24 <hermit_crab> :m #crux-arm lol

19:25 <cruxbridge> <pitillo (@pitillo:crux.nu)> Do you get that time on the rpi5 beerman?

19:25 <cruxbridge> <pitillo (@pitillo:crux.nu)> 😂😂😂

19:25 <beerman> not sure really

19:25 <beerman> never looked too closely xD

19:25 <cruxbridge> <pitillo (@pitillo:crux.nu)> Jajajajajaja

19:25 <beerman> i mean, i feel bad when people are disappointed but thats literally the game here

19:25 <cruxbridge> <pitillo (@pitillo:crux.nu)> On the M4 is just a kick….

19:26 <cruxbridge> <pitillo (@pitillo:crux.nu)> Nah, there are many options

19:26 <beerman> but i think the pi5 is faster than that, and the user did in fact not set jobs

19:26 <cruxbridge> <pitillo (@pitillo:crux.nu)> For him, any binary distro will be fine

19:26 <beerman> i think the full bootstrap of the rootfs repo takes ~4-5h tops

19:27 <cruxbridge> <pitillo (@pitillo:crux.nu)> Yeah, this is what I thought… so 3h on the pi5 didn’t sound reasonable for me

19:27 <beerman> maybe he is also transcoding a 4k video stream on it

19:27 <beerman> :D

19:28 <beerman> and compiling gcc, then i can see it sweat

19:28 <cruxbridge> <pitillo (@pitillo:crux.nu)> Anyways…. This is another option for anyone who wants to use it…. No one is forced to use it

19:28 <cruxbridge> <pitillo (@pitillo:crux.nu)> Jaajajajajaaja

19:28 <cruxbridge> <pitillo (@pitillo:crux.nu)> True…. We don’t know the background….

19:30 <cruxbridge> <pitillo (@pitillo:crux.nu)> Btw, good vibes for everyone, and peace/&/&:):)

19:31 <r0ni> oh he's gone... i'm working on a solution for some arm64 builds for 3.8... i need to do more stuff yet, but i aim to at least provide prebuilt things based on core,opt,xorg ... the issue i found is that eleminates wayland entirely from the builds since its in contrib, so any pre-built pkgs will suffer that omission

19:31 <cruxbridge> <pitillo (@pitillo:crux.nu)> That sounds great

19:33 <beerman> yeah wayland in contrib is kinda unfortunate

19:33 <beerman> but does it fit more in xorg or opt? :P

19:35 <cruxbridge> <pitillo (@pitillo:crux.nu)> How many ports related to wayland are over there? Not enough to create a collection for it, no?

19:36 <beerman> i mean, it depends on next to nothing, wayland itself

19:44 <cruxbridge> <pitillo (@pitillo:crux.nu)> So probably opt no? It has nothing to be with xorg….

19:53 <beerman> thats not so true either, e.g. sway as a compositor will still pull xorg stuff in, i think others do too

19:54 <beerman> prt-get depends sway | grep xorg | wc -l <- 26

20:04 <cruxbridge> <pitillo (@pitillo:crux.nu)> Interesting

20:04 <cruxbridge> <pitillo (@pitillo:crux.nu)> So stuff used with wayland uses xorg stuff….

20:05 <r0ni> beerman: personally i'd go xorg but that just cuz it fits the 'theme' lol

20:06 <r0ni> well xwayland is needed for some stuff still even these days, but not entirely required

20:06 <r0ni> tbh more than you'd probably think req x11 libs for things lol

20:07 <r0ni> but big omissions will be all the qt5/6 stuff i make will be x11 only which is a real debby downer

20:07 <cruxbridge> <pitillo (@pitillo:crux.nu)> So a pure wayland install can avoid all that xorg stuff? Or sway is needed to get wayland working? Because it seems to be like extended support

20:07 <r0ni> you can do pure wayland, but lots of stuff ppl expect to work in sway won't work

20:07 <beerman> r0ni: thats exactly what I'm thinking too but then again its just exactly not that

20:08 <beerman> i actually sort of have a wayland overlay where i have gtk and qt and stuff to not depend on x11

20:08 <r0ni> tho I MAY do seperate build repo including wayland support like a opt-contrib or something... I'm not entirely decided yet

20:08 <cruxbridge> <pitillo (@pitillo:crux.nu)> That’s one of the things I don’t understand about the current discussions about xorg and wayland

20:09 <beerman> but i dont pursue it right now

20:09 <beerman> no its just e.g. xkeyboardconfig is a integral part for most de/wms afaik

20:10 <beerman> so there is still stuff from the xorg ecosystem in use and it probably will stay for a fair bit longer too, maybe forever

20:11 <r0ni> yeah, that why i feel xorg ports place would be smartest place for wayland if it were ever moved

20:11 <cruxbridge> <pitillo (@pitillo:crux.nu)> So it will be some kind of mix at the end….