Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 8 Oct 2002 04:30:03 -0700 (PDT)
From:      Peter Pentchev <roam@ringlet.net>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: misc/43747: Apache2 port error
Message-ID:  <200210081130.g98BU3Df051579@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: Peter Pentchev <roam@ringlet.net>
To: Alex <freebsd-reply@akruijff.dds.nl>
Cc: bug-followup@FreeBSD.org
Subject: Re: misc/43747: Apache2 port error
Date: Tue, 8 Oct 2002 14:23:54 +0300

 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.
 
 I think Harry is not saying that your mod_php4 port is out-of-date with
 respect to the FreeBSD Ports Collection.  Its version has not been
 changed, so portversion would not report it as being out-of-date.
 
 What has changed, though, is the Apache 2 code itself.  The PHP module
 uses some functions and library calls from the Apache server source;
 whenever the Apache code changes, there is a chance that some of the API
 calls would change - either become invalid, or do something else, with
 bad, unintended consequences either way.  Thus, there is a version check
 at module loading time: the Apache binary queries the module, obtains
 the Apache API version for which it was built, and compares it with its
 own.
 
 Apparently, the Apache developers considered that the changes made
 between those two versions were significant enough that they may impact
 third-party modules using the Apache API.  Thus, your PHP module, built
 for the old version of Apache, is not really safe to run with the new
 one.  Remove the PHP module, rebuild it, and it will pick up the
 currently installed Apache version and work just fine.
 
 G'luck,
 Peter
 
 -- 
 Peter Pentchev	roam@ringlet.net	roam@FreeBSD.org
 PGP key:	http://people.FreeBSD.org/~roam/roam.key.asc
 Key fingerprint	FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
 When you are not looking at it, this sentence is in Spanish.

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?200210081130.g98BU3Df051579>