Date: Mon, 4 Mar 2002 18:51:56 -0500 From: "Mit Rowe" <mitayai@dreamlabs.com> To: "Simon 'corecode' Schubert" <corecode@corecode.ath.cx>, <ports@FreeBSD.ORG>, <dirk@FreeBSD.ORG> Subject: RE: apache+mod_ssl and mod_php complain about EAPI Message-ID: <DBEMKGPNFGOGJHLMDNDJGEEKGEAA.mitayai@dreamlabs.com> In-Reply-To: <20020304192503.37394f74.corecode@corecode.ath.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
(this message assumes you have used the ports collection, otherwise your mileage may vary) in case no one has answered you yet, when you upgrade from apache w/o ssl to apache w/ssl you have to recompile the mod_php* ports(s), and perhaps any other apache modules you have previously installed. during the port compilation process, it should auto-detect the need for EAPI -Mit > -----Original Message----- > From: owner-freebsd-ports@FreeBSD.ORG > [mailto:owner-freebsd-ports@FreeBSD.ORG]On Behalf Of Simon 'corecode' > Schubert > Sent: March 4, 2002 13:25 > To: ports@FreeBSD.ORG; dirk@FreeBSD.ORG > Subject: apache+mod_ssl and mod_php complain about EAPI > > > hello! > > while upgrading apache+mod_ssl and mod_php4 this was anounced: > > corecode@spirit:/usr/ports/www/mod_php4 $ sudo apachectl configtest > Password: > [Mon Mar 4 19:22:14 2002] [warn] Loaded DSO > libexec/apache/libphp4.so uses plain Apache 1.3 API, this module > might crash under EAPI! (please recompile it with -DEAPI) > Syntax OK > > i didn't find any EAPI flag and apache and php are up and running. is > this known behavior and where are the problems/ how do i solve that? > > thanks > corecode > > -- > /"\ http://corecode.ath.cx/ > \ / > \ ASCII Ribbon Campaign > / \ Against HTML Mail and News > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DBEMKGPNFGOGJHLMDNDJGEEKGEAA.mitayai>