I completely understand your point. Some people feel they need those extra
10% for production machines.
But are you actually planning on running Apache 2 on a heavily loaded
production machine? If yes, I think it might still be a bit early to
abandon 1.3.x. If no and you just want to mess
PROTECTED]
Subject: Re: [PHP-DEV] Apache2 and PHP CVS from today
I completely understand your point. Some people feel they need those
extra
10% for production machines.
But are you actually planning on running Apache 2 on a heavily loaded
production machine? If yes, I think it might still be a bit
August wrote:
I have a build framework that I use extremely frequently, and I don't
believe much has changed with it. Has the procedure changed for
statically compiling php with apache? I haven't seen any documentation
of it.
I don't know if httpd-2.0 still supports statically compiled
Jim wrote:
--with-apache is specific to apache1. you have to use --with-apxs2 to
build against apache2.
Apxs normally builds DSO versions of php. Under apache, DSO stands for
Dynamic Shared Object support, and there are some important differences
between dso and static compiles, primarily
Sebastian wrote:
I don't know if httpd-2.0 still supports statically compiled modules or
if PHP's --with-apache option needs tweaking. Why don't you use DSO
anyhow? It's the preferred method.
Why in the world is DSO the preferred method? Is this documented
somewhere?
I find DSO useful for
August wrote:
Sebastian wrote:
I don't know if httpd-2.0 still supports statically compiled modules or
if PHP's --with-apache option needs tweaking. Why don't you use DSO
anyhow? It's the preferred method.
Why in the world is DSO the preferred method? Is this documented
somewhere?
At 09:51 AM 2/26/2002 +0900, Yasuo Ohgaki wrote:
August wrote:
I find DSO useful for testing and development, but for deployment it
makes little sense to be using DSO, the cost of 60 seconds of compile is
negligible when looking at something that will be installed for
timeframes exceeding a day
August [EMAIL PROTECTED] wrote:
As far as I know httpd2 still allows static modules.
yes, but the --with-apache option for php4 tries to compile a static
version of php4 for apache 1.x.
maybe someone will create a --with-apache2 option that allows compiling
a static version of php4 for apache
Hey Yasuo,
Could you give a complete url to the DSO recommendation? Most
instructions on creating a high performance version of php recommend
static compiles.
Thanks...
- AZ
-Original Message-
From: Yasuo Ohgaki [mailto:[EMAIL PROTECTED]]
August wrote:
Sebastian wrote:
if PHP's
Jim wrote:
the fact that --with-apache does not work with apache 2.x is not a bug.
I see the inability to compile a static version of php for apache as the
bug. Not too concerned with the semantics of the command. My experience
may be abnormal, but for production work, static compiles seem a
August wrote:
Please give a complete url. The apache dso docs just describe dso. Most
instructions on creating a high performance version of php recommend
static compiles for good reason.
Info and status are not php. They have very different usage patterns
(used much less frequently).
I have set up dozens of production servers in the past couple of years and
not a single one of them is running the static version. If there are
issues with the DSO, then file a bug report on that so we can fix it.
-Rasmus
On Mon, 25 Feb 2002, August wrote:
Jim wrote:
the fact that
Sebastian,
I've been tracking this reasonably closely.
[php4-200202242100]# ./configure --with-apache=../httpd-2.0.32
Configuring SAPI modules
checking for AOLserver support... no
checking for Apache module support via DSO through APXS... no
checking for Apache module support... no
configure:
At 08:14 AM 2/23/2002 +0100, Sebastian Bergmann wrote:
August wrote:
There's been a bit of traffic on the apache dev list about this as
well, most of it indicating the problem lies on the PHP side of
things... This is something I've been tracking for a while, waiting
for the Apache beta
Chand wrote:
are you sure you've tried compiling it as a built-in module in Apache?
$ cd /usr/src/httpd-2.0
$ ./configure --enable-so --enable-mods-shared=ALL
$ make
$ make install
$ cd /usr/src/php4
$ ./configure --with-apxs2=/usr/local/apache2/bin/apxs
$ make
$
At 05:52 PM 2/23/2002 +0100, Sebastian Bergmann wrote:
Chand wrote:
are you sure you've tried compiling it as a built-in module in Apache?
$ cd /usr/src/httpd-2.0
$ ./configure --enable-so --enable-mods-shared=ALL
$ make
$ make install
$ cd /usr/src/php4
$ ./configure
There's been a bit of traffic on the apache dev list about this as well,
most of it indicating the problem lies on the PHP side of things... This
is something I've been tracking for a while, waiting for the Apache beta
(which is pretty close to their final) before really worrying about the
php
At 01:06 PM 2/22/2002 -0800, August wrote:
There's been a bit of traffic on the apache dev list about this as well,
most of it indicating the problem lies on the PHP side of things... This
is something I've been tracking for a while, waiting for the Apache beta
(which is pretty close to their
August wrote:
There's been a bit of traffic on the apache dev list about this as
well, most of it indicating the problem lies on the PHP side of
things... This is something I've been tracking for a while, waiting
for the Apache beta (which is pretty close to their final) before
really
I got Apache2 2.0.32 beta, compiled, installed, and happy.
I got PHP from CVS last night and this afternoon.
PHP Compiled and installed using the following configure:
configure --with-apxs2=/usr/web/bin/apxs --with-ssl --with-jpeg
--with-png
also
configure --with-apxs2=/usr/web/bin/apxs
no
20 matches
Mail list logo
