Date: Tue, 8 Oct 2002 11:00:11 -0700 (PDT) From: Alex <freebsd-reply@akruijff.dds.nl> To: freebsd-bugs@FreeBSD.org Subject: Re[2]: misc/43747: Apache2 port error Message-ID: <200210081800.g98I0BgX065667@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR misc/43747; it has been noted by GNATS. From: Alex <freebsd-reply@akruijff.dds.nl> To: Peter Pentchev <roam@ringlet.net> Cc: Alex <freebsd-reply@akruijff.dds.nl>, bug-followup@FreeBSD.org Subject: Re[2]: misc/43747: Apache2 port error Date: Tue, 8 Oct 2002 19:58:56 +0200 Hello/Beste Peter, Tuesday, October 08, 2002, 1:23:54 PM, you wrote: PP> On Tue, Oct 08, 2002 at 02:40:02AM -0700, Alex wrote: >> The following reply was made to PR misc/43747; it has been noted by GNATS. >> >> Hello/Beste Harry, >> >> Monday, October 07, 2002, 10:28:42 AM, you wrote: >> >> HO> After the portupgrade of apache2, I upgraded mod_php4. >> HO> That fixed the problem. So check all modules installed >> HO> separate from apache2. >> >> HO> A portupgrade -r will probabely fix this problem. >> >> Tanks for you help, but i still have the problem. >> I made the following two aliases which i use for updating. >> pv = portversion | grep -v '=' >> pu = potupgrade -Rr >> >> Intranet# pv >> XFree86-Server < >> XFree86-clients < >> cups-base < >> pkg_tarup ? >> samba < >> >> Intranet# apachectl restart >> httpd: module "sapi_apache2.c" is not compatible with this version of Apache (found 20020628, need 20020903). >> Please contact the vendor for the correct version. PP> I think Harry is not saying that your mod_php4 port is out-of-date with PP> respect to the FreeBSD Ports Collection. Its version has not been PP> changed, so portversion would not report it as being out-of-date. PP> What has changed, though, is the Apache 2 code itself. The PHP module PP> uses some functions and library calls from the Apache server source; PP> whenever the Apache code changes, there is a chance that some of the API PP> calls would change - either become invalid, or do something else, with PP> bad, unintended consequences either way. Thus, there is a version check PP> at module loading time: the Apache binary queries the module, obtains PP> the Apache API version for which it was built, and compares it with its PP> own. PP> Apparently, the Apache developers considered that the changes made PP> between those two versions were significant enough that they may impact PP> third-party modules using the Apache API. Thus, your PHP module, built PP> for the old version of Apache, is not really safe to run with the new PP> one. Remove the PHP module, rebuild it, and it will pick up the PP> currently installed Apache version and work just fine. PP> G'luck, PP> Peter Tanks, that did the trick. -- Best regards/Met vriendelijke groet, Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200210081800.g98I0BgX065667>