[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug 62228] New: Compiler error in mod_proxy.c:2675


            Bug ID: 62228
           Summary: Compiler error in mod_proxy.c:2675
           Product: Apache httpd-2
           Version: 2.4.33
          Hardware: PC
                OS: FreeBSD
            Status: NEW
          Severity: blocker
          Priority: P2
         Component: Build
          Assignee: bugs@xxxxxxxxxxxxxxxx
          Reporter: nortonwarner@xxxxxxxxx
  Target Milestone: ---

OS: FreeBSD 8.4 p4
C version: gcc version 4.2.1 20070831 patched [FreeBSD]
OpenSSL: 1.0.2o
Last Successful Apache Compile: 2.4.29

Compilation halts with the following problem:

mod_proxy.c && touch mod_proxy.slo
mod_proxy.c:2675: error: expected '=', ',', ';', 'asm' or '__attribute__'
before '*' token
mod_proxy.c: In function 'ap_proxy_ssl_engine':
mod_proxy.c:2709: error: 'proxy_ssl_engine' undeclared (first use in this
mod_proxy.c:2709: error: (Each undeclared identifier is reported only once
mod_proxy.c:2709: error: for each function it appears in.)
mod_proxy.c:2710: warning: implicit declaration of function 'proxy_ssl_engine'
mod_proxy.c: In function 'proxy_post_config':
mod_proxy.c:2760: error: 'proxy_ssl_engine' undeclared (first use in this
mod_proxy.c:2760: error: 'apr_OFN_ssl_engine_set_t' undeclared (first use in
this function)
mod_proxy.c:2760: error: expected expression before ')' token
*** Error code 1

Stop in /usr/src/httpd-2.4.33/modules/proxy.
*** Error code 1

My guess is the first error is causing the rest. It looks like a function
prototype is not matching the header of the actual function. This particular
function (proxy_ssl_engine) is new to 2.4.33. It wasn't in 2.4.29

Do I need a compiler --option to get this to work? or do I need an updated
compiler? and if so, which version?

Thanks for any help!

You are receiving this mail because:
You are the assignee for the bug.
To unsubscribe, e-mail: bugs-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: bugs-help@xxxxxxxxxxxxxxxx