configure.ac:22: error: possibly undefined macro: AM_PROG_LIBTOOL
If this token and others are legitimate, please use
m4_pattern_allow.
See the Autoconf documentation.
run? Any ideas about how to fix this? I'm running FreeBSD 5.3 and all my
tools are from the ports collection. Thanks!
Fenlason, Josh wrote:
I'm running into an issue where Apache 2.2.0 on AIX won't start if there
is more than one Listen directive. According to the documentation, this
should not be so. This is not the case on Solaris. This is causing
problems with regards to configuring ssl. Has anyone
== Please reply above this line ==
Graham Leggett,
Your ticket has been successfully submitted to our Sales department. One of our
staff members will review it and reply accordingly. Listed below are ticket
details that you will need in order to update or check the status of this
It looks like an autobot was fooled into subscribing here.
I have removed it and added it to the deny list.
Roy
Thanks for the tip, but I don't believe that's the problem. I'm working
with an almost out of the box configuration. The problem occurred when
I tried to enable mod_ssl. The only two Listen directives are in
conf/httpd.conf (Listen 80) and conf/extra/httpd-ssl.conf (Listen 443).
,
Josh.
Changing each of the Listen directives to 0.0.0.0:port worked.
This is on AIX 5.1
Thanks again for the help.
,
Josh.
-Original Message-
From: Jeff Trawick [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 28, 2005 5:58 PM
To: dev@httpd.apache.org
Subject: Re: Apache 2.2.0
Even though it seems like a small change, I'm leaning more towards leaving
everything as is, especially if we have enough concensus that 3.2.6 will
be final, not beta. Then we should try to roll-out a 3.3.0 alpha (or
whatever) as soon as possible, and this is where people would begin to
test
On Thu, 29 Dec 2005, Nicolas Lehuen wrote:
I've tested your patch and of course it doesn't break anything in our
unit tests. I can't see how it can break anything, therefore I've
checked it in in the hope that it will make it for 3.2.6 final.
Grisha, tell me if you disagree with that, I'll
Gregory (Grisha) Trubetskoy wrote:
On Thu, 29 Dec 2005, Nicolas Lehuen wrote:
I've tested your patch and of course it doesn't break anything in our
unit tests. I can't see how it can break anything, therefore I've
checked it in in the hope that it will make it for 3.2.6 final.
Grisha, tell
On Thu, 29 Dec 2005, Jim Gallacher wrote:
So are we happy with the state of svn trunk right now? If so I'll roll
the tarball for 3.2.6b.
Does anyone here have any opinion on whether this release should be marked
as beta?
I personally don't know enough to comment, so I'd release it as beta
IMO there will always be bugs, and I think you've all nailed the show
stoppers. Otherwise you'll never get out of beta.
Nick
Gregory (Grisha) Trubetskoy wrote:
On Thu, 29 Dec 2005, Jim Gallacher wrote:
So are we happy with the state of svn trunk right now? If so I'll roll
the tarball for
Gregory (Grisha) Trubetskoy wrote:
On Thu, 29 Dec 2005, Jim Gallacher wrote:
So are we happy with the state of svn trunk right now? If so I'll roll
the tarball for 3.2.6b.
Does anyone here have any opinion on whether this release should be
marked as beta?
I personally don't know enough
Rian Hunter wrote:
cd /var/db/pkg
ls -ld gnu-*
Hmm... you should read the FreeBSD documentation on autotools.
I'll bet you made symlinks in /usr/local/bin from say autoconf to
autoconf259 and similiar.
The other ports (/usr/ports/devel/auto* and /usr/ports/libtool*) are
customized
On Thu, 2005-12-29 at 10:05, Philip M. Gollucci wrote:
Can you do :
cd /var/db/pkg
ls -ld gnu-*
Nothing in there starts with gnu-
and
env | grep -i path
On Thu, 2005-12-29 at 10:05, Philip M. Gollucci wrote:
Can you do :
cd /var/db/pkg
ls -ld gnu-*
nothing in there s
and
Fenlason, Josh wrote:
Thanks for the tip, but I don't believe that's the problem. I'm working
with an almost out of the box configuration. The problem occurred when
I tried to enable mod_ssl. The only two Listen directives are in
conf/httpd.conf (Listen 80) and conf/extra/httpd-ssl.conf
Personally, I think it would be cool to fold the fcgi branch
into httpd-trunk. I have some cycles coming up and it would
be cool to get that puppy official for trunk and maybe
even 2.2
PS: Yeah, I know, I said I'd be offline, but this is something
I broke my promise for :)
--
On 12/29/05, Jim Jagielski [EMAIL PROTECTED] wrote:
Personally, I think it would be cool to fold the fcgi branch
into httpd-trunk. I have some cycles coming up and it would
be cool to get that puppy official for trunk and maybe
even 2.2
No objection to merging it eventually, but I'd really
On 12/29/2005 02:11 AM, Sander Striker wrote:
[..cut..]
First it doesn't seem to be the case that mod_proxy actually
sets r-status in the case of an error (service temporarily
unavailable caused by ProxyTimeout for instance). This may
not matter for a handler, but...
Just for my
Jim Jagielski wrote:
Personally, I think it would be cool to fold the fcgi branch
into httpd-trunk. I have some cycles coming up and it would
be cool to get that puppy official for trunk and maybe
even 2.2
I would prefer to keep it in a development branch for at least until TCP
support is
On Dec 29, 2005, at 2:08 PM, Paul Querna wrote:
I would prefer to keep it in a development branch for at least
until TCP support is good.
Maybe the place to merge is before work is done on local/Process
management. That would mean a minimal feature set to work with
remote FCGI
On 12/29/05, Brian McCallister [EMAIL PROTECTED] wrote:
On Dec 29, 2005, at 2:08 PM, Paul Querna wrote:
As for backport it to 2.2 Right now, I believe this should be
one of the headliner features for a 2.4 release in 8-12 months.
I am not a fan of backportitist. I am not saying I
By next week, I'm going to start another development branch, for
mod_execd. By now though, there seem to be a few different problems
which execd might be able to solve for us, so before code is written,
it's probably useful to share some design ideas.
Here's a list of currect vaguely
Here's a very lightly tested patch to allow mod_proxy_fcgi to deal
with fastcgi records with content length greater than AP_IOBUFSIZE.
If someone could double check the math to make sure it's correct in
all cases I'd appreciate it, I tested it by reducing the buffers to
very small sizes, and it
Ruediger Pluem wrote:
On 12/29/2005 02:11 AM, Sander Striker wrote:
[..cut..]
First it doesn't seem to be the case that mod_proxy actually
sets r-status in the case of an error (service temporarily
unavailable caused by ProxyTimeout for instance). This may
not matter for a handler, but...
[
http://issues.apache.org/jira/browse/MODPYTHON-103?page=comments#action_12361401
]
Graham Dumpleton commented on MODPYTHON-103:
Correspondingly, it should be possible to add a req.add_input_filter() function
as well. This is because
Paul Querna wrote:
Jim Jagielski wrote:
Personally, I think it would be cool to fold the fcgi branch
into httpd-trunk. I have some cycles coming up and it would
be cool to get that puppy official for trunk and maybe
even 2.2
I would prefer to keep it in a development branch for at
Garrett Rooney wrote:
On 12/29/05, Jim Jagielski [EMAIL PROTECTED] wrote:
Personally, I think it would be cool to fold the fcgi branch
into httpd-trunk. I have some cycles coming up and it would
be cool to get that puppy official for trunk and maybe
even 2.2
No objection to merging
On 12/30/2005 01:10 AM, Sander Striker wrote:
Ruediger Pluem wrote:
[..cut..]
Ok, let me tell you why I want it. I want to implement a directive
called CacheErrorServeStale, which, when it hits the CACHE_SAVE filter
say with a 503 Service Temporarily Unavailable, and has a
28 matches
Mail list logo
