Re: Why does mod_jk require a C++ compiler instead of just C?

2013-09-24 Thread Mladen Turk

On 09/23/2013 10:58 PM, Christopher Schultz wrote:

All,

Someone recently on the users list[1] had some trouble building mod_jk
and it turned out that the problem was a missing c++ compiler.



There is nothing in the code that would require C++.
It's probably an extra (or copy/paste) configure requirement.


Regards
--
^TM

-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



Re: Why does mod_jk require a C++ compiler instead of just C?

2013-09-24 Thread Rainer Jung
On 24.09.2013 11:58, Mladen Turk wrote:
 On 09/23/2013 10:58 PM, Christopher Schultz wrote:
 All,

 Someone recently on the users list[1] had some trouble building mod_jk
 and it turned out that the problem was a missing c++ compiler.

 
 There is nothing in the code that would require C++.
 It's probably an extra (or copy/paste) configure requirement.

I had a quick look, but I find no indication of that in configure.in or
any of our m4 files.

I wonder how that comes into play. Maybe something autoomatically
triggered by the libtool used or by the gcc self-report.

I must admit: Currently no idea.

But Mladen is of course right: no use for gcc during make and we should
be able to remove the need from the configure script, only that I have
no idea how.

Regards,

Rainer


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



RE: Why does mod_jk require a C++ compiler instead of just C?

2013-09-23 Thread Caldarale, Charles R
 From: Christopher Schultz [mailto:ch...@christopherschultz.net] 
 Subject: Why does mod_jk require a C++ compiler instead of just C?

 everything is declared as extern C

Wouldn't such declarations require a C++ compiler?  I don't think C can parse 
that.  Perhaps the fix would be to wrapper those portions of the function 
declarations and definitions with #ifdef __cplusplus/#endif.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



Re: Why does mod_jk require a C++ compiler instead of just C?

2013-09-23 Thread Christopher Schultz
Chuck,

On 9/23/13 5:09 PM, Caldarale, Charles R wrote:
 From: Christopher Schultz [mailto:ch...@christopherschultz.net] 
 Subject: Why does mod_jk require a C++ compiler instead of just C?
 
 everything is declared as extern C
 
 Wouldn't such declarations require a C++ compiler?  I don't think C
 can parse that.  Perhaps the fix would be to wrapper those portions
 of the function declarations and definitions with #ifdef
 __cplusplus/#endif.

I've taken another look and it seems that the places where extern C
is used are all in the PCRE package and already have #ifdef __cplusplus
surrounding them.

-chris



signature.asc
Description: OpenPGP digital signature


Re: Why does mod_jk require a C++ compiler instead of just C?

2013-09-23 Thread Christopher Schultz
All,

On 9/23/13 4:58 PM, Christopher Schultz wrote:
 Someone recently on the users list[1] had some trouble building mod_jk
 and it turned out that the problem was a missing c++ compiler.
 
 I did some quick checking and it doesn't look like mod_jk requires a c++
 compiler for any actual compilation -- that is, everything is declared
 as extern C and no obvious c++ features in use.
 
 httpd advertises requirements for autoconf, libtool, and an ANSI-C
 compiler (not C++). I didn't actually try to build httpd without having
 c++ available.
 
 Is this simply an oversight in the configure script? Are we stupidly
 requiring a C++ compiler, or is there a reason that it is required?

I was just able to build mod_jk on Amazon Linux (roughly RHEL) by:

1. Installing http-devel and gcc-c++ packages

2. Running configure

3. Removing gcc-c++ and gcc46-c++ packages (this removes the C++ compiler)

4. Running make

This resulted in a .so file that I have not actually tried running (in
httpd), but have every reason to believe would work just fine.

I think this is just an erroneous requirement of configure. Can anyone
give me some pointers for how to modify the capabilities-scanning that
configure does?

-chris



signature.asc
Description: OpenPGP digital signature