Quoting Alexandre Rossi (2020-06-04 16:08:26) > The problem seems to be that the PHP plugin is compiled against PHP7.4 > and is linked with libphp.so which points to 7.3 in bullseye and 7.4 in sid. > > $ ldd /usr/lib/uwsgi/plugins/php_plugin.so | grep php > libphp7.so => /usr/lib/libphp7.so (0x00007f4b8ca48000) > $ ls -l /usr/lib/libphp7.so > lrwxrwxrwx 1 root root 25 mai 11 19:41 /usr/lib/libphp7.so -> > /etc/alternatives/libphp7 > $ ls -l /etc/alternatives/libphp7 > lrwxrwxrwx 1 root root 21 mai 11 19:41 /etc/alternatives/libphp7 -> > /usr/lib/libphp7.4.so > > The php plugin should explicitly be linked against /usr/lib/libphp7.4.so
It seems uwsgi gets its information for which library to link against from /usr/bin/php-config (see /usr/src/uwsgi/plugins/php/uwsgiplugin.py). And it seems php-dev and php4.7-dev ships php-config* tools that (I guess) both provides that name using the dpkg alternatives systems. Try check if those varying build tools offer different build hints, and if they do then try comeup with a patch for plugins/php/uwsgiplugin.py to use php-config only by default, overridable by an environment variable. If those picking the right build tool doesn't solve this, then try come up with some other patch taking some other more direct environment variable into account (look at other plugins and try mimic upstream style, so that hopefully your patch can be adopted upstream). Then we can have uwsgi-plugin-php pass a suitable environment variable resolved at build time from the package pulled in by its build-dependency on virtual package "php-dev". - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
