jaeger changed the topic of #crux-arm to: CRUX-ARM 3.6 Released! - http://crux-arm.nu/Documentation/ReleaseNotes3-6 | Logs: https://libera.irclog.whitequark.org/crux-arm/
<beerman> pitillo: how is building llvm going? :D
<pitillo> with calm beerman xD
<pitillo> finished (probably thisnlast night)
<pitillo> ======> Building '/nfs/rpi3/3.7/pkg/llvm#15.0.6-1.pkg.tar.xz' succeeded.
<beerman> With what now? What's that?
<pitillo> it seems right
<beerman> XD
<pitillo> jaajajajajajaa
<beerman> I have a few more in the pipeline
<beerman> Most are "simpler", so don't worry
<pitillo> around 70h here on the rpi3
<beerman> Hahaha wow
<pitillo> I have a problem with llvm PR, I don't know how to manage it
<beerman> What do you mean?
<pitillo> there are some problems to add it feom github
<beerman> With that one i messed up
<beerman> I opened the pull against master branch and changed that later on
<pitillo> I can sharenmore info this afternoon from home (currently working, and this year's start comes with some changes...I'm still waiting for information from the company)
<pitillo> ummm that's probably the problem then
<beerman> Ah, gotcha. I'm on my way to work too, first day after vacation
<beerman> I can reopen it if you want
<pitillo> the other PR were fine and I was able to sqaush and merge, but with these ones, shpuld be there something to fix
<beerman> Not sure, I'd need to see the error
<pitillo> not sure hownmuch effort must be done from ypur side
<beerman> That i should be able to do when I'm at work
<pitillo> last time was very confortable, I was able to build, tedt and confirm. Then just squash and merge from github eas enought
<beerman> Ok, I'll reopen it
<pitillo> if you can, test at least with llvm which is fine, so if all go right, then you can recreate the rest
<beerman> The rest should be fine? Just llvm, right.
<beerman> ?
<pitillo> I checked another one which had the same issue, but I'm speaking from what I remember (may be I'm wrong)
<pitillo> anyways, we csn focus first on llvm
<beerman> Ok, I'll recreate them as needed
<beerman> Yeah, i agree
<pitillo> this weekend while itnwas building I put hands on pine64 kernel, from time to time, and I wasn't able to build and boot any of my tests
<pitillo> the worse part is that I took armbian kernel and it didn't boot neither (this was my last chance and I had a good feeling about it... but it didn't boot
<beerman> pine64: can i built that on a pi?
<pitillo> sometimes I feel I've lost knowledge and experience... which makes me feel I go backwards
<pitillo> sure, I believe it can be built anywhere
<beerman> Ok, cool
<beerman> I'll want to check that out
<pitillo> I was thinking in rebuild our toolchain repo to start building kernel on cross systems
<beerman> I wanted to try your rootfs on a lxc container and see if that works
<pitillo> which one? do you mean generic aarch64?
<beerman> No the pine64 one
<beerman> On the pi as an lxc host
<pitillo> ummmm good question
<pitillo> we need to be sure they have compat (backwards) instructions, because I don't remember if they have smae instructions
<pitillo> different socs and may be rpi4 overlays pine, but can't confirm
<pitillo> may be you can direcly download pine64 rootfs and try to make a jail... if it succesfully executes bash, shpuldn't be any problem
<beerman> yeah, i will try that as soon as i have time
<beerman> let me see about the pull request
<beerman> pitillo: remade it, lets see if you can merge that better
<pitillo> thanks beerman! I'll check this afternoon from home
<beerman> Sure
<pitillo> beerman: this is what I meant and what it's ahppening after recreating the PR again
<pitillo> not sure why it can't be integrated directly
<beerman> I'm not sure either
<beerman> It says it's fixable
<beerman> I just can't do it because i have no write permissions
<beerman> maybe i need to update my fork? Oo
<beerman> i'll try again, probably
<beerman> pitillo: now it looks better, i think it was my fault
<beerman> i think the problem was that I created the branch against the master branch, because this the default and I might have overlooked that fact
<beerman> i made sure that the other PRs in fact were branched off correctly from the 3.7 branch
<beerman> maybe you can configure the 3.7 branch to be the default?
<pitillo> the aim is to put 3.7 default master when we publish the release....
<pitillo> you are some steps ahead... amazing stress testing
<pitillo> now it is fine :D
<beerman> haha perfect
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ crux-ports-opt-arm64 ]: and again: llvm (#8)
crux-arm-bot has left #crux-arm [#crux-arm]
<beerman> i am ahead? how? ๐Ÿ˜„
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ crux-ports-opt-arm64 ]: llvm: update signature after mergin PR #8
crux-arm-bot has left #crux-arm [#crux-arm]
<pitillo> I mean, as there is no release published, you are working ahead repositories
<pitillo> not sure how I can explain...
<pitillo> we usually put default master on repos just before publishing the release (web adjusts, old flyspray categories, all links to point default to 3.7...)
<pitillo> so at this moment, we are testing far than the release... you made a full system test.... improving
<beerman> heh ๐Ÿ˜„ okok
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ crux-ports-opt-arm64 ]: cbindgen: initial commit (#5)
crux-arm-bot has left #crux-arm [#crux-arm]
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ crux-ports-opt-arm64 ]: cbindgen: update signature after merging PR #5
crux-arm-bot has left #crux-arm [#crux-arm]
<beerman> made you a new one since you liked the last one so much
<beerman> ( อกยฐ อœส– อกยฐ)
<beerman> if you just keep merging i have to open prs faster, i hope you know that
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ crux-ports-opt-arm64 ]: brotli: initial commit (#4)
crux-arm-bot has left #crux-arm [#crux-arm]
<pitillo> yeah, I've saw that you created one just when I closed it xD
<pitillo> on the way, from your side and mine
<beerman> haha perfect ๐Ÿ˜„
<pitillo> I have some time ahead, my parents-in-law pick up the kid
<pitillo> xD
<beerman> freeeedom!
<beerman> ๐Ÿ˜„
<pitillo> yeah|~@|@~|@
<beerman> ๐Ÿพ
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ crux-ports-opt-arm64 ]: brotli: update signature after merging PR #4
crux-arm-bot has left #crux-arm [#crux-arm]
<beerman> well, but then i know that you have time to do rust
<beerman> scnr
crux-arm-bot has joined #crux-arm
crux-arm-bot has left #crux-arm [#crux-arm]
<crux-arm-bot> [ crux-ports-opt-arm64 ]: compiler-rt: initial commit (#2)
<pitillo> rust scares... anytime I deep in the Pkgfile... I shake
<beerman> its not that bad?
<beerman> what makes you shake?
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ crux-ports-opt-arm64 ]: compiler-rt: update signature after merging PR #2
crux-arm-bot has left #crux-arm [#crux-arm]
<pitillo> it's veeeery big... it has a lot of options, patches... a beast (not only for ARM)
<beerman> but its not that bad ๐Ÿ˜„ you barely need to change anything from the default, and there is not too many patches really either
<beerman> those that are there are just to fix a few quirks the way we like it (libexec dir for example)
crux-arm-bot has joined #crux-arm
crux-arm-bot has left #crux-arm [#crux-arm]
<crux-arm-bot> [ crux-ports-opt-arm64 ]: rust: initial commit (#3)
<beerman> you just merged it?
<beerman> haha
<beerman> you are wild
<pitillo> I trust... I can build them and wait for another 70~h for each of them (gcc and rust)
<beerman> 95% of the time it just compiles, its like libreoffice too, in that regard, or llvm
<pitillo> xD
<beerman> don't worry, they work fine ๐Ÿ‘๏ธ i have tested them here
<pitillo> yeah, I know about patches and installed deps check... but it's a beast
<pitillo> yeah, in the same shape as llvm, firefox or chromium....
<beerman> chromium is a whole other story
<beerman> its why i keep this pkgfile to myself
<beerman> that shit is crazy even from my pov ๐Ÿ˜†
<beerman> and electron, for what its worth
<beerman> look at that
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ crux-ports-opt-arm64 ]: rust: update signature after mergin PR #3
crux-arm-bot has left #crux-arm [#crux-arm]
<pitillo> xDDD
<beerman> My Pkgfile is 340 lines long
<pitillo> ungoogled-chromium
<pitillo> xD
<beerman> yeah
<beerman> you can get this flatpakked
<pitillo> I tried to make it work on these devices... I don't remember if we only kept firefox
<beerman> i might default to firefox on the pi
<pitillo> it was a real headache... and builds took too many time (3-4 days)
<beerman> because building chromium takes my desktop over 24 hours without cache
<beerman> with cache its still several hours
<pitillo> nice, never heard about ungoogled xD
<beerman> that hp 19" server i have at home takes ~8-10 hours or so
<beerman> newer machines supposedly cope better, but i don't have any
<pitillo> on my main I can't build it currently, I have a broken dep overthere
<pitillo> but it took some hours
<pitillo> I think it was on 3.6.... then moved to firefox there
<beerman> yeah
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ crux-ports-opt-arm64 ]: gcc-fortran: initial commit (#9)
crux-arm-bot has left #crux-arm [#crux-arm]
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ crux-ports-opt-arm64 ]: gcc-fortran: update signature after mergin PR #9
crux-arm-bot has left #crux-arm [#crux-arm]
<pitillo> on foot, I believe this should be changed to explort CFLAGS and -Wno-error?
<pitillo> I mean line 16 which has hardcoded rpi4 cflags
<beerman> maybe yes
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ crux-ports-opt-arm64 ]: gpgme: initial commit (#11)
crux-arm-bot has left #crux-arm [#crux-arm]
crux-arm-bot has joined #crux-arm
<crux-arm-bot> [ crux-ports-opt-arm64 ]: gpgme: update signature after mergin PR #11
crux-arm-bot has left #crux-arm [#crux-arm]
<pitillo> that one will take a bit more time
<beerman> I can look over it at home
<beerman> But foot is hands down the best terminal emulator there is
<pitillo> wayland... it's everywhere... and here I haven't tested it
<beerman> sorry, been afk for a while ๐Ÿ™‚ it's great, SBCs and wayland is the perfect match, imo
<beerman> if i had the energy i would maintain a wayland only overlay for x86_64, i kind of do, but without the public pressure in my private git instance
<beerman> only one machine that i am toy testing a wayland only build
<beerman> but dropping most of the x dependencies feels good in all regards.
<beerman> dunno, maybe its just me. how did you like your ventures into wayland so far, jaeger ?
<jaeger> For the most part it works fine on the AMD GPUs, not so much nvidia
<jaeger> With that said there are minor things here and there that are not quite perfect, like the black screen from kodi, or applications not switching properly between fullscreen and windowed... small stuff