09:17:28 jperkin: php74 with modules are not working after the latest updates in trunk. I get warnings like: 09:17:28 PHP Warning: PHP Startup: xsl: Unable to initialize module\nModule compiled with build ID=API20190902,NTS\nPHP compiled with build ID=API20190902,TS\nThese options need to match\n in Unknown on line 0 09:17:28 PHP Warning: PHP Startup: Unable to load dynamic library 'zip.so' (tried: /opt/local/lib/php/20191128/zip.so (ld.so.1: httpd: fatal: relocation error: file /opt/local/lib/php/20191128/zip.so: symbol executor_globals: referenced symbol not found), /opt/local/lib/php/20191128/zip.so.so (ld.so.1: httpd: fatal: /opt/local/lib/php/20191128/zip.so.so: open failed: No such file or directory)) in Unknown on line 0 09:17:28 Do you have any ideas how to fix it? 09:21:40 google suggests that executor_globals errors are related to mismatches between versions, so I'd double check you don't have either a mix of php versions, or perhaps a module that is older and hasn't been upgraded alongside other php changes 09:32:03 jperkin: Checked this before. Deinstalled everything from php and reinstalled it. So there might be an issue with the latest php74 build? 09:44:17 yeh, looks like for some reason the symbols have changed at least compared to 2023Q4 09:49:09 jperkin: Strange! This issue appeared after the latest trunk update 09:49:10 happy to dig into what's changed, but is there any particular reason you need to still be on 7.4? it was EOL 2 years ago 09:50:18 jperkin: This is the last app with 7.4; They are building a version for 8.x now, but it is not ready jet. I stuck with 7.4. 10:36:40 jperkin: Will you be able to fix it in the next trunk build? Or should I switch the app to lx branch? 10:38:14 If it is not possible to fix it in the near future or if you decide to remove php74 from trunk, it is fine for me. I just want to know what to expect :-) 10:40:03 I've not looked yet, but I'd recommend just provisioning it on 23.4.0 then you aren't affected if we decide to remove 7.4 from trunk 13:46:26 jperkin: Did a pkg_add php-7.4.33nb4.tgz and ap24-php74-7.4.33nb11.tgz from the pkgsrc snapshot of first of june. This is working again. All modules are from latest trunk. Maybe while the build process php itself was not copied? 13:50:52 jperkin, I've just compiled go-bin from trunk and installing it using the generated package pkg_add /data/packages/SmartOS/2023Q4/x86_64/All/go-bin-1.21.5.tgz the result is -> /opt/local/go-bin/bin/go version 13:50:53 go version go1.19.4 illumos/amd64 13:51:52 I've copied go go-bin and so on from trunk to my 2023Q4 tree ...and I cannot understand why a go-bin package create a 1.21.5 package with 1.19.4 inside 13:53:15 xmerlin: go-bin is hardcoded to one specific release, and 2023Q4 doesn't have https://github.com/NetBSD/pkgsrc/commit/5637289f4dc878d5e7fe496cb47ef4cdf181d229 13:53:45 (yes, it's a bit janky) 14:00:59 fixed thank you 16:19:19 jperkin, I need go >= 1.22.4 to compile newer grafana ...but everytime it install fo 1.21.9 even if I've TOOL_DEPENDS+= go122>=1.22<1.23:../../lang/go122 in Makefile ...do you have any hints? 16:22:11 yeh it doesn't quite work like that for go as the deps are handled by lang/go/version.mk, I think you can set GO_VERSION_REQD=122 17:35:49 jperkin, is it possible to compile smartos-live on pkgbuild-lts 23.4.0 ? ...looking to the guide it should be possible but the script configure complains about the lack of py39-expat 18:07:14 jperkin, error "wire: -: This application uses version go1.21 of the source-processing packages but runs version go1.22 of 'go list'. It may fail to process source files that rely on newer language features. If so, rebuild the application using a newer version of Go." ...is it related to go-wire?