Apache 2.2.4 with mod_ssl start up problem
Hi I am running 6.0 on i386 and have updated apache22 with the latest and greatest from my cvsup'ed ports tree (I also think openssl was updated to the latest beta 0.9.8e, which might be connected or maybe not...) All went fine until I have come to restart Apache when I get this error: httpd: Syntax error on line 83 of /usr/local/etc/apache22/httpd.conf: Cannot load /usr/local/libexec/apache22/mod_ssl.so into server: /usr/ local/libexec/apache22/mod_ssl.so: Undefined symbol SSL_CTX_set_info_callback Well line 83 is the module load line in httpd.conf and has always been there, so I think that's a red herring. I have done a large amount of Googleing and come across similar people with similar problems, one of which was not answered, one of which was fixed by a re-install from port (Which I have done twice now so I don't think that's it) and one that was in German. Now my German is embarrassingly bad and you can't get a decent translation when it comes to problem fixing so I am not much wiser except it was suggesting something about a linked library, ldd and something in a *. 4.so version of a library but that's about all I could grasp :-( Can any one shed any light as to which FM I need to R so I can RTFM or what I can do to fix this. Many thanks Drew -- In line with our policy, this message has been scanned for viruses and dangerous content by the Technology Tiger MailScanner. Further information can be found at www.technologytiger.net/policy Technology Tiger Limited is registered in Scotland with registration number: 310997 Registered Office 55-57 West High Street Inverurie AB51 3QQ ___ 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
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
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]
