We've seen broken mod_jk builds with xlc_r in our environments. cc_r builds
seems to work fine though.
I haven't dug into what the issue is though.
tim
>>> On 6/03/2007 at 8:35 a.m., in message <[EMAIL PROTECTED]>, Eric Wertman
>>> <[EMAIL PROTECTED]> wrote:
Actually I started with xlc_r and it
Actually I started with xlc_r and it wouldn't go. Not mod_jk
specifically, but apr or apache 2.2.4. I stuck with cc_r for consistency.
William A. Rowe, Jr. wrote:
Any reason you didn't choose xlc_r? I'd suggest you retest with that
compile.
Rainer Jung wrote:
Hi Eric,
we won't close the i
Any reason you didn't choose xlc_r? I'd suggest you retest with that
compile.
Rainer Jung wrote:
> Hi Eric,
>
> we won't close the issue immediately with "we don't support cc_r". This
> will be our last option :)
>
> Rainer
>
> Eric Wertman wrote:
>> Hi Rainer... I'll have to re-compile to get
Hi Eric,
we won't close the issue immediately with "we don't support cc_r". This
will be our last option :)
Rainer
Eric Wertman wrote:
Hi Rainer... I'll have to re-compile to get this info for you. I'll
make sure I can re-produce it and submit the details in a bugzilla.
I think the first
Hi Rainer... I'll have to re-compile to get this info for you. I'll
make sure I can re-produce it and submit the details in a bugzilla.
I think the first thing you'll notice, though, is that I'm using the IBM
cc_r compiler and not gcc.
Rainer Jung wrote:
Eric reported very strange mod_jk b
Eric reported very strange mod_jk behaviour using it with Apache
2.0/worker on AIX.
I start a new mail thread, because until now all the discussion is part
of non-specific threads.
Eric: could you please open a bugzilla (issues.apache.org), so that we
can track the issue?
Also: When you compile
