On Sun 09 Mar 2014 10:24:51 AM CDT, Adam Thompson wrote:
Perhaps my google-fu isn't working today...

Running 5.4-RELEASE.

I've installed (from packages) php-5.3, I *did* follow the pkg
instructions to symlink the various config files, but I now get:

[email protected]:/root# httpd
httpd:/usr/local/lib/php-5.3/libphp5.so: undefined symbol 'unixd_config'
[...chop...]

This is httpd from base, and php straight from packages - how on earth
did I break it?

Update:
1. confirmed this happens on a bare, virgin install with php-5.3.27-ap2.tgz. I don't see any errata on this, am I just blind? 2. recompiled from ports, which did *not* produce the "-ap2" flavour, and the generic package seems to work. 3. confirmed the original non-ap2 binary package *does* work as expected. I'm now confused, because I don't see a -ap2 flavour in the Makefile, where does this come from? What does it do?


Oh, !@#$%^!!!!. I just figured it out, I think - the "-ap2" flavour is for people who are using Apache 2.x from ports, the bare flavour is for people running httpd from base. I keep forgetting OpenBSD's httpd is based on the 1.x stream. I assumed the -ap2 just meant it used the APR v2 libraries, which, of course, implies Apache v2.x, which, of course, is not what I'm trying to run on.

It would, however, be a good thing if it were possible to, in the future, edit the package description for the Apache 2.x version to indicate that... there's no externally-visible evidence (for the easily-confused among us, like me, apparently) to distinguish the two packages other than the -ap2 suffix on the filename. I can't even figure out how the ports infrastructure builds that version, so I'm unable to submit a patch.

I don't know if we've finally removed httpd from base in 5.5, but of course that would obviate the need for the two versions of the package... I guess nginx would either use the -fpm flavour, or run it as a CGI?

-Adam

Reply via email to