Date: Sat, 24 Jul 2004 11:45:31 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Peter Risdon <peter@circlesquared.com> Cc: freebsd-questions@freebsd.org Subject: Re: Installing php4 Message-ID: <20040724104531.GC91096@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <41022D4E.8040307@circlesquared.com> References: <41022833.6090509@themarshalls.co.uk> <41022D4E.8040307@circlesquared.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--5G06lTa6Jq83wMTw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sat, Jul 24, 2004 at 10:35:10AM +0100, Peter Risdon wrote:
> Drew Marshall wrote:
> >I have been trying to install php4 (On FreeBSD 5.2.1, cvsuped ports=20
> >tree, php4-4.3.8_1, I have tried both the mod_php4 and lang/php4) and=20
> >the full menu options seem to have disappeared. When I run make install=
=20
> >I get a 3 line menu offering to allow me to install for apache2 instead=
=20
> >of apache 1.3.x, to enable debugging and use IPv6. I have no options to=
=20
> >configure the build process. If I allow the build to continue Apache=20
> >grumbles that it can't find variable session( ), which would suggest PHP=
=20
> >is not compiled with session support. What am I doing wrong? What has=20
> >changed?
>=20
> Major revision to the port, for reasons that I don't find very obvious.
>=20
> However, you need lang/php4-extensions or the mod_php equivalent.
Actually, php4-extensions works with any of the 'main' PHP ports --
lang/php4, lang/php4-cli, www/php4-cgi or www/mod_php4. The fact that
there are 4 different variations on a plain 'php4' port in the tree is
the reason why all of the module support was moved out into a separate
extensions port. =20
While this move to specifying all of the PHP modules as loadable
extensions makes a great deal of sense from one point of view -- ports
that use PHP can now explicitly list all of the extensions they
require to operate, rather than having to have their own private PHP
slave ports -- the implementation has run into a number of problems.
For php4 there are some extensions where the same functionality is not
available when used as a loadable module as when compiled in. The
security/php4-openssl extension is a case in point: unless OpenSSL
support is compiled-in, the fsockopen() function won't let you open
'tls://' or 'ssl://' style URLs. (As a practical result, that means
that eg. Squirrelmail can't communicate with a secure IMAP server on
port 993. The only alternative in that case is to communicate to an
unencrypted IMAP server on port 143, which quite probably involves
sending passwords over the net in plaintext.)
Beyond that, not all of the PHP consuming ports have yet been updated
to depend on the appropriate PHP extensions, so installing those ports
de novo doesn't immediately get you a workable system. A common
symptom of this is a run-time error where one of the perl compatible
regular expression (pcre_*()) functions doesn't work. The answer
pretty much is just to install the required extension modules by hand,
and tweak the value of the 'extension_dir' directive in
/usr/local/etc/php.ini
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
--5G06lTa6Jq83wMTw
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFBAj3LiD657aJF7eIRAtZLAJ0YSqep7OozOoCX1pktSPeywWOrVACfTUh5
oXos40JG9Dx4/jMn3yJVero=
=Hk0p
-----END PGP SIGNATURE-----
--5G06lTa6Jq83wMTw--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040724104531.GC91096>