-
jfqd1
jperkin: php74 with modules are not working after the latest updates in trunk. I get warnings like:
-
jfqd1
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
-
jfqd1
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
-
jfqd1
Do you have any ideas how to fix it?
-
jperkin
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
-
jfqd1
jperkin: Checked this before. Deinstalled everything from php and reinstalled it. So there might be an issue with the latest php74 build?
-
jperkin
yeh, looks like for some reason the symbols have changed at least compared to 2023Q4
-
jfqd1
jperkin: Strange! This issue appeared after the latest trunk update
-
jperkin
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
-
jfqd1
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.
-
jfqd1
jperkin: Will you be able to fix it in the next trunk build? Or should I switch the app to lx branch?
-
jfqd1
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 :-)
-
jperkin
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
-
jfqd1
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?
-
xmerlin
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
-
xmerlin
go version go1.19.4 illumos/amd64
-
xmerlin
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
-
jperkin
xmerlin: go-bin is hardcoded to one specific release, and 2023Q4 doesn't have
NetBSD/pkgsrc 5637289
-
jperkin
(yes, it's a bit janky)
-
xmerlin
fixed thank you
-
xmerlin
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?
-
jperkin
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
-
xmerlin
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
-
xmerlin
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?