15:53:14 out of curiosity, what is the pain with building mattermost on illumos? Is it illumos support in go? or is it the dependencies that mm relies on not having illumos support? 15:54:32 Well for started the current commit build.sh does not produce a build for me 15:54:59 for the current version it is set to or a newer version? 15:55:06 There also a bunch of patches do not apply to newer version and I couldn't get even mmctrl to build outside of the build system 15:55:21 The patches apply to the current version 15:55:38 But I wasn't able to produce a copy of the package that is currently in extra with it 15:57:15 I think it's some dependencies in the chain that just don't have illumos support. 15:57:26 and patching things to work is getting harder and harder 15:57:28 hadfl mentioned that the deps have some issues, and it just made me wonder exactly the issue is. Like is it Linux-isms in the deps? 15:57:35 I don't know why the existing one doesn't build, it certainly did recently 15:57:54 but they might have removed some tags or releases in github or something like that. 15:58:03 IIRC the newer go it uses does not like the current build.sh 15:58:10 It says no can do, this is deprecated 15:58:18 I tried hacking around it but didn't get far 15:58:43 You can always add `set_gover ` near the top of the script 15:59:06 sjorge: yea I tried building it while waiting for some other stuff, but with an updated mm version. I saw that error. But looking at mm release notes they claim to build with an older go (for the version I set it to), so I switched to that and it got further. 16:00:07 anyway to check what go ver the current one was build with ? 16:02:37 @rzezeski https://github.com/omniosorg/illumos-omnios/pull/1381 16:02:57 I dunno, but if you look at the release notes they build 7.8.11 with Go 1.18.1. So I imagine the official mm build used something older than that. But you could try building it with the go-118 package by using `set_gover 1.18`. 16:03:42 I might give that a go (ha) somewhere this week when I got a bit more time 16:05:11 Yea, looking again at mm release notes, they claim to build 7.5.x with Go 1.18.1. 16:09:35 silly phone 16:09:46 Why would the touch and old default to the bad action 16:32:23 set_gover 1.18 16:32:30 Does at least seem to have the current build.sh work 16:32:46 Once it finished that I'll at least do a PR just for that so the current build is not broken 16:35:41 it's a while since i had a look at mm. but iirc the main issue was a new dependency they pulled in. there is an open issue but it has stalled since... 16:35:49 https://gitlab.com/cznic/libc/-/issues/26 16:41:07 Hmm yeah I that would probably also indeed be a rather big issue 16:41:49 But with the gover set to 1.18 the current build.sh at least produce a package om bloody 16:41:54 Which is further than I got last time 16:51:00 A quick glance makes me think this libc library is a "write libc in go" type project? If that's the case the better solution would be to patch mm to sidestep it completely. An alternate libc, in any language, is probably not a great idea on illumos. 17:25:03 again iirc since it's been a while but it just gets pulled in because of sqlite support. they switched to a module from the same family that relies on this libc implementation. so patching out sqlite support would be an option 17:26:04 however, it still boils down to someone interested and willing to keep support for a native mm. 18:14:40 ooh it got merged! once it hits bloody, i'll just move my mattermost zone over to lx 18:14:54 that way plugins will probably also work 😅