I ran the patch in and got

bash-3.00$ patch < proxy_util.patch
  Looks like a unified context diff.
File to patch: modules/proxy/proxy_util.c
Hunk #1 succeeded at 951 (offset 77 lines)
Hunk #2 succeeded at 1879 (offset 117 lines)
Hunk #3 succeeded at 1912 (offset 120 lines)
Hunk #4 failed at line 2097.
Hunk #5 succeeded at 1991 (offset 123 lines)
1 out of 5 hunks failed: saving rejects to modules/proxy/proxy_util.c.rej
done

bash-3.00$ diff -n proxy_util.c proxy_util.c.old
d958 4
a961 1
                if (APR_SUCCESS != apr_bucket_read(e, (const char
**)&response, &len, APR_BLOCK_READ)) {
d1886 1
a1886 1
    if (!conn->hostname || !worker->is_address_reusable ||
d1960 41
d2042 3


Making install in metadata
Making install in proxy
/apps/exlink/SOURCES/httpd-2.2.3/srclib/apr/libtool --silent
--mode=compile gcc   -DSSL_EXPERIMENTAL -DSSL_ENGINE  -DSOLARIS2=10
-D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -D_LARGEFILE64_SOURCE
-I/apps/exlink/SOURCES/httpd-2.2.3/srclib/pcre -I.
-I/apps/exlink/SOURCES/httpd-2.2.3/os/unix
-I/apps/exlink/SOURCES/httpd-2.2.3/server/mpm/prefork
-I/apps/exlink/SOURCES/httpd-2.2.3/modules/http
-I/apps/exlink/SOURCES/httpd-2.2.3/modules/filters
-I/apps/exlink/SOURCES/httpd-2.2.3/modules/proxy
-I/apps/exlink/SOURCES/httpd-2.2.3/include
-I/apps/exlink/SOURCES/httpd-2.2.3/modules/generators
-I/apps/exlink/SOURCES/httpd-2.2.3/modules/mappers
-I/apps/exlink/SOURCES/httpd-2.2.3/modules/database
-I/apps/exlink/SOURCES/httpd-2.2.3/srclib/apr/include
-I/apps/exlink/SOURCES/httpd-2.2.3/srclib/apr-util/include
-I/apps/exlink/SOURCES/httpd-2.2.3/srclib/apr-util/xml/expat/lib
-I/apps/exlink/SOURCES/httpd-2.2.3/modules/proxy/../generators
-I/usr/sfw/include -I/apps/exlink/SOURCES/httpd-2.2.3/modules/ssl
-I/apps/exlink/SOURCES/httpd-2.2.3/modules/dav/main -prefer-non-pic
-static -c proxy_util.c && touch proxy_util.lo
proxy_util.c:1962:1: unterminated #else
*** Error code 1
make: Fatal error: Command failed for target `proxy_util.lo'
Current working directory /apps/exlink/SOURCES/httpd-2.2.3/modules/proxy
*** Error code 1
The following command caused the error:
otarget=`echo install-recursive|sed s/-recursive//`; \
list='  '; \
for i in $list; do \
    if test -d "$i"; then \
        target="$otarget"; \
        echo "Making $target in $i"; \
        if test "$i" = "."; then \
                made_local=yes; \
                target="local-$target"; \
        fi; \
        (cd $i && make $target) || exit 1; \
    fi; \
done; \
if test "$otarget" = "all" && test -z 'libmod_proxy.la
libmod_proxy_connect.la libmod_proxy_ftp.la libmod_proxy_http.la
libmod_proxy_ajp.la libmod_proxy_balancer.la'; then \
    made_local=yes; \





Ruediger Pluem <[EMAIL PROTECTED]>
12/20/2006 09:28 PM
Please respond to
[email protected]


To
[email protected]
cc

Subject
Re: Apache BUG: 36495  : ajp_proxy_connect_backend failure








On 12/20/2006 08:45 PM, Sander Temme wrote:
>
> On Dec 20, 2006, at 9:52 AM, Benjamin Cuthbert wrote:
>
>> Do you need to checkout head for apr and apr-util ?

You only need to do this if you are working with httpd code you
checked out from svn. Once you are hacking on a released source
tarball this is not needed. Especially you do not need the
head of apr / apr-util for this patch.

Instead of copying around complete files I guess it should work much
better if you apply the following patch to your 2.2.3 (or even better
wait for 2.2.4 which is hopefully out soon) tarball:

http://svn.apache.org/viewvc/httpd/httpd/trunk/modules/proxy/proxy_util.c?r1=451575&r2=473278&view=patch


It contains one unrelated patch (r470076,
http://svn.apache.org/viewvc?view=rev&revision=470076),
but applying this small patch also does not hurt.


>
> I'll be happy to push the above into a page under httpd.apache.org/ dev
> as "here's how to build HEAD for testing" if folks think it  useful. Or

+1

> I may put it on my blog.

Or http://wiki.apache.org/httpd/?


Regards

RĂ¼diger




---

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.

Reply via email to