On 12/19/13, 2:29 PM, "Hong" wrote:
>I wrote an Apache module that call functions in openssl library to sign
>the
>messages. The module is dynamic linked to openssl library 1.0.1d when I
>built it. It works fine when it is loaded into the Apache that was also
>built with the same version of opens
On 7/24/12 5:51 PM, "Nick Kew" wrote:
>
>Did you fix it?
No, I'm still investigating. So far all I can prove is that it's the
compiler turning on __STDC_VERSION__ itself, not any headers I'm using. I
put a #if up at the top of my source and it reports it's on immediately.
This is, umm, not right
On 7/24/12 2:29 PM, "Nick Kew" wrote:
>
>On 24 Jul 2012, at 18:23, Cantor, Scott wrote:
>
>> I'm still investigating, just wondering if anybody has seen this.
>
>Yes. It's not new: C++ doesn't like those macros.
>
>Simple fix is to enclose the
On 7/24/12 2:29 PM, "Nick Kew" wrote:
>Yes. It's not new: C++ doesn't like those macros.
Weird, never broke on me until now.
>Simple fix is to enclose them in extern "C" { ... }.
>Alternatively, expand them by hand as per C rules.
That was my next step, thanks.
-- Scott
On Jul 24, 2012, at 1:45 PM, "Rainer Jung" wrote:
>
> I can confirm, that I am able to build httpd 2.4 on Solaris using gcc 4.7.1.
> I vaguely remember that I had also done it using 4.6.3. In my case no g++
> involved though. That points in that direction as a possible cause.
To clarify, Apa
I'm seeing a build bug on a Solaris box with a very recent GCC version against
the Apache 2.4 headers, which I'm wondering about.
All my AP_INIT_TAKE1 macros for command handling are failing with:
error: expected primary-expression before '.' token
Looking at the macros, it's doing some kind of
