On Wed, Apr 24, 2019 at 06:34:06PM +0200, Stefan Bethke wrote: > > Am 23.04.2019 um 18:01 schrieb Kurt Jaeger <p...@freebsd.org>: > > > > Hi! > > > >> Did you find a solution? Please let me know. > > > > There's a well-known problem in the sequence in which php modules > > are loaded. I don't know if this is the case here as well, > > but that's what we do: > > > > fetch -o fixphpextorder \ > > https://people.freebsd.org/~ohauer/scripts/fixphpextorder.sh > > chmod 755 fixphpextorder > > > > cd /usr/local/etc/php > > cat ext-*ini > extensions.ini > > fixphpextorder > > mv extensions.ini.new extensions.ini > > rm ext-*ini > > > > Please test and report if it fixes the problem. > > Thanks Kurt, it appears to fix (or at least work around) the problem. > > Why is the default load order broken? Why does it not affect everyone? > > I moved all the individual inis into a bak subdir, and now only have an > extensions.ini. > > If I understand correctly, mod_php/PHP reads the individual inis in order. > Why aren’t they in the right order? Can this be fixed in the ports for the > PHP modules?
Could you give the order that works for you, so that we can try to figure out which module is making it break ? Because there is no "right" order, there is an order that can work for most people, and from time to time, two libs have conflicting symbols, but it is not possible to detect that. So I made up an order that should be ok, but some time is not. -- Mathieu Arnold
signature.asc
Description: PGP signature
