installing php4 and php5 on one machine
Hi there, I am using FreeBSD 7.0-RELEASE-p1. The machine has PHP 5.2.6 with Suhosin-Patch 0.9.6.2 (cli). We're going to host one of our sites which currently is hosted by our ISP. This site requires php4 to work before it gets rewritten or dumped. Anyway, my current BSD machine is a dedicated one so I can do with it what I like but I am not really sure how to go about installing two versions of php. php5 has been installed from ports and works well. How would you advise me to go about installing php4? I do not think I will be able to do it from ports (it will require an ancient version of php 4.10). Also I do not want to mix dependencies and such. Another issue is how to host the site. Use a different port for it (*:8080)? Use jails (never been in jail so no experience with it so far ;)? I do have several IPs to play with so I can use them if that helps. I'd appreciate your opinion about it. Many thanks to you all in advance! -- Zbigniew Szalbot www.lc-words.com smime.p7s Description: S/MIME Cryptographic Signature
Re: installing php4 and php5 on one machine
On Mon, May 12, 2008 at 5:54 PM, Zbigniew Szalbot [EMAIL PROTECTED] wrote: Hi there, I am using FreeBSD 7.0-RELEASE-p1. The machine has PHP 5.2.6 with Suhosin-Patch 0.9.6.2 (cli). We're going to host one of our sites which currently is hosted by our ISP. This site requires php4 to work before it gets rewritten or dumped. Anyway, my current BSD machine is a dedicated one so I can do with it what I like but I am not really sure how to go about installing two versions of php. php5 has been installed from ports and works well. The main issue here is: Which php would you want Apache to refer to, and at what time? Honestly, I don't have an answer for this!. Perhaps you have to run a whole different system within a jail:-( There may be an easier way, but when I read this, that is where my /etc (end of thinking capacity) got me for now. How would you advise me to go about installing php4? I do not think I will be able to do it from ports (it will require an ancient version of php 4.10). Also I do not want to mix dependencies and such. Another issue is how to host the site. Use a different port for it (*:8080)? Use jails (never been in jail so no experience with it so far ;)? Why not just use the final version of php-4.x.x? Even this breaks your site? I do have several IPs to play with so I can use them if that helps. Use a jail. I'd appreciate your opinion about it. Many thanks to you all in advance! I am not even sure my opinion helps, but well, the whole world reads this list!:-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Oh My God! They killed init! You Bastards! --from a /. post ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: installing php4 and php5 on one machine
On Monday 12 May 2008 16:54:37 Zbigniew Szalbot wrote: How would you advise me to go about installing php4? I do not think I will be able to do it from ports (it will require an ancient version of php 4.10). Also I do not want to mix dependencies and such. Jail for sure. Another issue is how to host the site. Use a different port for it (*:8080)? Use jails (never been in jail so no experience with it so far ;)? I do have several IPs to play with so I can use them if that helps. Yep, add an IP alias to the external interface, build the jail on that and you're pretty much done (DNS of course being the missing link). There's tools like ezjail in ports, but imo that's more for people who build jails on a regular basis. Also, it is a good idea to do it by hand at least once, so you get a feel for the process and know what's going on underneath the ezjail magic. Believe it or not, the manpage for jail(8) contains a section with the commands to setup a jail from scratch and touches on all the variables required to have it started upon boot. There's more then one reason to do this in a jail. First of all, you can seperate the php versions, something that's not supported by the ports system. Secondly, you can add a second jail where you're going to work the migration on. Once satisfied, you bring them both down, change ip of the new version and wait for bug reports. If it looks like there's too many bugs, you still have the old version available and you can switch the ip's back. You can do this as often as you want, till everything looks good. Thirdly, the cost in memory usage for a jail is negligable compared to the above gains, especially since it will primarily run apache (cron and sshd being the most common other programs). -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: installing php4 and php5 on one machine
Hello, Mel pisze: On Monday 12 May 2008 16:54:37 Zbigniew Szalbot wrote: How would you advise me to go about installing php4? I do not think I will be able to do it from ports (it will require an ancient version of php 4.10). Also I do not want to mix dependencies and such. Jail for sure. Thanks! There's more then one reason to do this in a jail. First of all, you can seperate the php versions, something that's not supported by the ports system. And here comes my question. Can the php5 installation be left intact and php4 be built in a jail? And finally, would I also need to build another instance of apache in jail? Thank you again! -- Zbigniew Szalbot www.lc-words.com smime.p7s Description: S/MIME Cryptographic Signature
Re: installing php4 and php5 on one machine
On Monday 12 May 2008 22:46:41 Zbigniew Szalbot wrote: Hello, Mel pisze: On Monday 12 May 2008 16:54:37 Zbigniew Szalbot wrote: How would you advise me to go about installing php4? I do not think I will be able to do it from ports (it will require an ancient version of php 4.10). Also I do not want to mix dependencies and such. Jail for sure. Thanks! There's more then one reason to do this in a jail. First of all, you can seperate the php versions, something that's not supported by the ports system. And here comes my question. Can the php5 installation be left intact and php4 be built in a jail? Yes. I build ports for 6.x machines, on a 7.x machine in a jail. So you can seperate it perfectly. And finally, would I also need to build another instance of apache in jail? Yes. You basically create a seperate FreeBSD installation, without the kernel. Complete with devfs and seperate user accounts. It is better to start this way and if you get paranoid about all the things running, it is easy to remove things one by one till it stops working ;) -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Help with installing php4 and upgrading mysql323 for Apache 1.36
Hi, I'm having trouble figuring out what and how to install and upgrade some programs/modules. This was very simple when I last did it, but I haven't been around doing this since version 4.7 was new and now some things have changed. Server is now 4.11 STABLE (or will be on monday). I have the latest Apache-mod_ssl installed and I need to have the latest mod_php4 for Apache aswell as upgrading mysql to the latest of the 323 version. (Perhaps I'll go for mysql 4.1, but I need to verify this with some software running on my system first.) What port/modul should I install to get php4 working under apache? I used to install mod_php4, but from my /usr/ports tree this seems deprecated to me. It's also important that I can make the php4 module work together with mysql 323. Any help very much appreciated! Thanks a lot. Best regards, Andreas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help with installing php4 and upgrading mysql323 for Apache 1.36
Hi, I'm having trouble figuring out what and how to install and upgrade some programs/modules. This was very simple when I last did it, but I haven't been around doing this since version 4.7 was new and now some things have changed. Server is now 4.11 STABLE (or will be on monday). I have the latest Apache-mod_ssl installed and I need to have the latest mod_php4 for Apache aswell as upgrading mysql to the latest of the 323 version. (Perhaps I'll go for mysql 4.1, but I need to verify this with some software running on my system first.) What port/modul should I install to get php4 working under apache? I used to install mod_php4, but from my /usr/ports tree this seems deprecated to me. It's also important that I can make the php4 module work together with mysql 323. Any help very much appreciated! Thanks a lot. Best regards, Andreas Andreas, As 6.x is out, 4.11 etc will soon be no longer supported. You should consider updating to 5.x at least if possible. I'm running 6.1 with no problems. mod_php has been deprecated as you found out. Use the php4 port instead which has the functionality of the mod_php4 port. Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help with installing php4 and upgrading mysql323 for Apache 1.36
On 6/24/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: As 6.x is out, 4.11 etc will soon be no longer supported. You should consider updating to 5.x at least if possible. I'm running 6.1 with no problems. mod_php has been deprecated as you found out. Use the php4 port instead which has the functionality of the mod_php4 port. Rob Thanks Rob, The server will be erased and installed with the latest version for FreeBSD in a few months, but untill then I feel I need to stick to 4.X since there are too much on the machine built under this branch. The server that will replace this one will have the latest 6.X version for sure. I'll try with the php4 port, but I think there are a lot of build options there. What is the minimal I need in order to get php4 working together with Apache 1.36 and Mysql? /Andreas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Ports won't finish installing PHP4
I tried to use portupgrade to install PHP4.4.1 this afternoon because portaudit complained about a security issue and all went fine except PEAR broke: pear-Archive_Tar-1.3.1 pear-Cache_Lite-1.5.1,1 pear-Console_Getopt-1.2 pear-HTTP_Request-1.2.4 pear-Net_CheckIP-1.1 pear-Net_DNSBL-1.0.0 pear-Net_Socket-1.0.6 pear-Net_URL-1.0.14 pear-PEAR-1.3.5_1 pear-XML_RPC-1.4.0 [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 196 packages found (-1 +0) (...) done] --- Installing the new version via the port === Installing for php4-pear-4.4.1 === php4-pear-4.4.1 depends on file: /usr/local/include/php/main/php.h - found === php4-pear-4.4.1 depends on file: /usr/local/lib/php/20020429/pcre.so - found === php4-pear-4.4.1 depends on file: /usr/local/lib/php/20020429/xml.so - found === php4-pear-4.4.1 depends on shared library: expat.5 - found === Generating temporary packing list === Checking if devel/php4-pear already installed Installing PEAR environment: /usr/local/share/pear/ tar: Error opening archive: Failed to open '/usr/ports/devel/php4-pear/work/php-4.4.1/pear/packages/XML_RPC-1.3.1.tar': No such file or directory *** Error code 1 Stop in /usr/ports/devel/php4-pear/work/php-4.4.1. *** Error code 1 Stop in /usr/ports/devel/php4-pear. *** Error code 1 Stop in /usr/ports/devel/php4-pear. But here's what's in that directory: # ls -lh /usr/ports/devel/php4-pear/work/php-4.4.1/pear/packages/ total 268 -rw-r--r-- 1 root wheel 100K Mar 28 2005 HTML_Template_IT-1.1.tar -rw-r--r-- 1 root wheel41K Mar 28 2005 Net_UserAgent_Detect-2.0.1.tar -rw-r--r-- 1 root wheel 126K Aug 22 22:13 XML_RPC-1.4.0.tar Anyone have an idea as to what I missed? -- for every complex problem there is a simple solution and it's wrong. - unknown ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Properly installing PHP4 extensions under Apache 1.3.x
Hi, A while ago the topic was raised about how to properly install PHP 4.3.8+ versions with their required extensions, under Apache 1.3.x. I'm doing so just now, but I seem to be missing one step, as the extensions do not seem to get picked up. Here's what I did: 1) Update the ports tree using CVSup 2) Build the /usr/ports/lang/php4 port (= 4.3.10 - make install) 3) Build the /usr/ports/lang/php4-extensions port 4) Build several extensions I need (GD, MySQL, session), again, I did do a make install 5) Restart Apache Double checking the installation shows: pkg_info | grep php php4-4.3.10 PHP Scripting Language (Apache Module and CLI) php4-gd-4.3.10 The gd shared extension for php php4-mysql-4.3.10 The mysql shared extension for php php4-session-4.3.10 The session shared extension for php O.k., so that goes alright. Yet, I do not see any of these extensions getting picked up, and I wonder on the one hand what I am missing exactly, and on the other hand what the easiest (or best) way is to fix this. Can anyone tell me something more about the following: 1) How do I get these extensions to be picked up (using the configure tool in the php4 ports? adding entries to Apache's httpd.conf file? something else?) 2) Is this really the easiest way to go? It seems to be somewhat cumbersome to have to install all extensions this way. When building the php4-extensions port I was prompted for which extensions I wanted to install. I was hoping some form of master Makefile would result from that, allowing me to install the previously selected extensions all in one go, rather than having to install each one of them manually. Thanks a lot in advance, and cheers! Olafo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Properly installing PHP4 extensions under Apache 1.3.x
Hi again, Alright, I just found the missing step: I used to have an existing php.ini file in which the extension_dir directive was not disabled. Commenting that directive does the trick. :) So the correct procedure should then be: 1) Update the ports tree using CVSup 2) Build the /usr/ports/lang/php4 port (= 4.3.10 - make install) 3) Build the /usr/ports/lang/php4-extensions port 4) Build several extensions I need (GD, MySQL, session), again, I did do a make install 5) Comment out the extension_dir directive in php.ini 6) Restart Apache Cheers! Olafo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing php4
On Sun, July 25, 2004 0:29, Matthew Seaman said:
On Sat, Jul 24, 2004 at 08:58:15PM +0100, Drew Marshall wrote:
I understand the logic but I would have thought a line somewhere in
Makefile or the README just to give poor stupid people like me a clue as
to where to start looking. Ons further question that has come from my
compilation of the php4-extension is that once you have made your
selection the first time these options seem to be saved somewhere (The
build process states found previous configuration or similar) where is
this? I missed an option in my hurry this morning and now can't get back
to the menu options (No matter how many make cleans, pkg_deletes etc I
do) to re-set or add the options.
the lang/php?-extensions ports just use the standard OPTIONS mechanism
that a large number of other ports use.
To modify a previously setup configuration, just do:
# make reconfig
The configuration data is stored as a file /var/db/ports/{foo}/options
where {foo} is the LATEST_LINK name for the port -- ie the same name
as the package installed by the port, but with any version numbers
split off. It can be different though.
In order to return any particular port to the pristene never
configured state, simply delete the appropriate {foo} directory from
/var/db/ports. you can do that by:
# make rmconfig
In order to prevent the options dialog ever coming up (eg. when you've
supplied your own settings via portupgrade's MAKE_ARGS array), add
BATCH=yes either in the environment or to the make argument list (the
MAKE_ARGS array is probably the handiest way of doing that). All of
these things are discussed in the ports(7) man page.
Cheers,
Matthew
Thank you so much for your help, that's one of the things I love about
Open Source, you never stop learning!
Kind regards
Drew
--
In line with our policy, this message has
been scanned for viruses and dangerous
content by MailScanner, and is believed to be clean.
www.themarshalls.co.uk/policy
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Installing php4
Hi all I have been trying to install php4 (On FreeBSD 5.2.1, cvsuped ports tree, php4-4.3.8_1, I have tried both the mod_php4 and lang/php4) and the full menu options seem to have disappeared. When I run make install I get a 3 line menu offering to allow me to install for apache2 instead of apache 1.3.x, to enable debugging and use IPv6. I have no options to configure the build process. If I allow the build to continue Apache grumbles that it can't find variable session( ), which would suggest PHP is not compiled with session support. What am I doing wrong? What has changed? Thanks for your help Drew -- In line with our policy, this message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. www.themarshalls.co.uk/policy ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing php4
Drew Marshall wrote: Hi all I have been trying to install php4 (On FreeBSD 5.2.1, cvsuped ports tree, php4-4.3.8_1, I have tried both the mod_php4 and lang/php4) and the full menu options seem to have disappeared. When I run make install I get a 3 line menu offering to allow me to install for apache2 instead of apache 1.3.x, to enable debugging and use IPv6. I have no options to configure the build process. If I allow the build to continue Apache grumbles that it can't find variable session( ), which would suggest PHP is not compiled with session support. What am I doing wrong? What has changed? Major revision to the port, for reasons that I don't find very obvious. However, you need lang/php4-extensions or the mod_php equivalent. Peter. Thanks for your help Drew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing php4
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 tree, php4-4.3.8_1, I have tried both the mod_php4 and lang/php4) and the full menu options seem to have disappeared. When I run make install I get a 3 line menu offering to allow me to install for apache2 instead of apache 1.3.x, to enable debugging and use IPv6. I have no options to configure the build process. If I allow the build to continue Apache grumbles that it can't find variable session( ), which would suggest PHP is not compiled with session support. What am I doing wrong? What has changed? Major revision to the port, for reasons that I don't find very obvious. 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. 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 -- 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 pgpDMYixTvITk.pgp Description: PGP signature
Re: Installing php4
Matthew Seaman wrote: snipped 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. 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 I understand the logic but I would have thought a line somewhere in Makefile or the README just to give poor stupid people like me a clue as to where to start looking. Ons further question that has come from my compilation of the php4-extension is that once you have made your selection the first time these options seem to be saved somewhere (The build process states found previous configuration or similar) where is this? I missed an option in my hurry this morning and now can't get back to the menu options (No matter how many make cleans, pkg_deletes etc I do) to re-set or add the options. Many thanks for being so helpful Drew -- In line with our policy, this message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. www.themarshalls.co.uk/policy ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing php4
Matthew Seaman wrote: snipped 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. 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 I understand the logic but I would have thought a line somewhere in Makefile or the README just to give poor stupid people like me a clue as to where to start looking. Ons further question that has come from my compilation of the php4-extension is that once you have made your selection the first time these options seem to be saved somewhere (The build process states found previous configuration or similar) where is this? I missed an option in my hurry this morning and now can't get back to the menu options (No matter how many make cleans, pkg_deletes etc I do) to re-set or add the options. Many thanks for being so helpful Drew -- In line with our policy, this message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. www.themarshalls.co.uk/policy ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing php4
On Saturday 24 July 2004 21.58, Drew Marshall wrote: Matthew Seaman wrote: snipped 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. 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 I understand the logic but I would have thought a line somewhere in Makefile or the README just to give poor stupid people like me a clue as to where to start looking. Ons further question that has come from my compilation of the php4-extension is that once you have made your selection the first time these options seem to be saved somewhere (The build process states found previous configuration or similar) where is this? I missed an option in my hurry this morning and now can't get back to the menu options (No matter how many make cleans, pkg_deletes etc I do) to re-set or add the options. Many thanks for being so helpful Drew --- Hi. I had a hard time after a upgrade too. Had to comment out 'extension_dir' directive in /usr/local/etc/php.ini just to get it to work at all. ( Running a PhpNuke site :-) What I understand, from the mailinglist, the 'extension_dir' are allready hardcoded in the php-source. So if you override it in php.ini, you have to give it the correct location. I also had to deinstall the allready installed packages from my previous attempt. ( I made a bad choice ) pkg_delete -r php4\* You might try looking for the options in /var/db/ports/php4-extensions/options Hope this helped. /Hasse. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing php4
- Original Message - From: Drew Marshall [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, July 24, 2004 3:16 PM Subject: Re: Installing php4 Matthew Seaman wrote: snipped 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. 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 I understand the logic but I would have thought a line somewhere in Makefile or the README just to give poor stupid people like me a clue as to where to start looking. Ons further question that has come from my compilation of the php4-extension is that once you have made your selection the first time these options seem to be saved somewhere (The build process states found previous configuration or similar) where is this? I missed an option in my hurry this morning and now can't get back to the menu options (No matter how many make cleans, pkg_deletes etc I do) to re-set or add the options. Many thanks for being so helpful Drew Look at /var/db/ports/* and then delete any option files that pertain to php4. That will allow the menu to come up again on a fresh make. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing php4
antenneX wrote: - Original Message - From: Drew Marshall [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, July 24, 2004 3:16 PM Subject: Re: Installing php4 Matthew Seaman wrote: snipped 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. 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 I understand the logic but I would have thought a line somewhere in Makefile or the README just to give poor stupid people like me a clue as to where to start looking. Ons further question that has come from my compilation of the php4-extension is that once you have made your selection the first time these options seem to be saved somewhere (The build process states found previous configuration or similar) where is this? I missed an option in my hurry this morning and now can't get back to the menu options (No matter how many make cleans, pkg_deletes etc I do) to re-set or add the options. Many thanks for being so helpful Drew Look at /var/db/ports/* and then delete any option files that pertain to php4. That will allow the menu to come up again on a fresh make. Smart. That works, as does make config that Grant posted. Very happy bunny :-) Thanks all!! Drew -- In line with our policy, this message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. www.themarshalls.co.uk/policy ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Installing PHP4 from ports fail
Hello all, I am trying to install mysql323, apache13 and php4 on 4.4 Release. So far I have successfully installed mysql and apache, with php it is a different story. I have two issues. I have a question about apache, and I would like some help getting php installed on my machine. I installed apache13-server. Will this installation allow me to use ssl? When I try to install php the installation fail repeatedly at this point. -Wl,-rpath -Wl,/usr/local/lib ../lib/libbison.a Making all in doc makeinfo --no-split -I . `test -f 'bison.texinfo' || echo './'`bison.texinfo -o bison.info bison.texinfo:37: Unknown command `copying'. bison.texinfo:58: Unmatched [EMAIL PROTECTED]'. bison.texinfo:93: Unknown command `insertcopying'. makeinfo: Removing output file `bison.info' due to errors; use --force to preserve. *** Error code 2 Stop in /usr/ports/devel/bison/work/bison-1.75/doc. *** Error code 1 Stop in /usr/ports/devel/bison/work/bison-1.75. *** Error code 1 Stop in /usr/ports/devel/bison/work/bison-1.75. *** Error code 1 Stop in /usr/ports/devel/bison. After the installation failed I did the following: make clean /usr/ports/lang/php4 cd /usr/ports/devel/bison make clean make The bison installation fails repeatedly at the same place and with the same error messages as the php installation. If someone could help me, offer any suggestions or pointers I would appreciate it. Gregory Norman ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
re: Installing PHP4 from ports fail
From: Gregory Norman [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, August 02, 2003 9:49 AM Subject: Installing PHP4 from ports fail I installed apache13-server. Will this installation allow me to use ssl? Not AFAIK. You probably need apache+mod_ssl or apache-ssl (? - the English one ... Greg Laurie, IIRC)... When I try to install php the installation fail repeatedly at this point. -Wl,-rpath -Wl,/usr/local/lib ../lib/libbison.a Making all in doc makeinfo --no-split -I . `test -f 'bison.texinfo' || echo './'`bison.texinfo -o bison.info bison.texinfo:37: Unknown command `copying'. bison.texinfo:58: Unmatched [EMAIL PROTECTED]'. bison.texinfo:93: Unknown command `insertcopying'. makeinfo: Removing output file `bison.info' due to errors; use --force to preserve. *** Error code 2 Stop in /usr/ports/devel/bison/work/bison-1.75/doc. *** Error code 1 Stop in /usr/ports/devel/bison/work/bison-1.75. *** Error code 1 Stop in /usr/ports/devel/bison/work/bison-1.75. *** Error code 1 Stop in /usr/ports/devel/bison. After the installation failed I did the following: make clean /usr/ports/lang/php4 cd /usr/ports/devel/bison make clean make The bison installation fails repeatedly at the same place and with the same error messages as the php installation. If someone could help me, offer any suggestions or pointers I would appreciate it. Gregory Norman I've basically given up on building anything that's not just about the latest source. Probably a good idea from a security standpoint. The issues focus around compatibility in code. If you're running 4.4-release, you've got a codebase that's almost two years old. If you've updated /usr/ports, you have a much newer version of PHP. IIRC, bison is part of /usr/src/gnu, so it's probably outdated as well, unless you've installed a newer version yourself. Sorry I'm of little help. My solution (I rebuilt mod_php4 yesterday) is to run -STABLE, and cvsup /usr/ports before compiling anything ... Kevin Kinsey ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
