On Wed, Apr 18, 2001 at 11:25:23AM -0700, Jeff Kilbride wrote:
> Forgive the expression, but bullshit. :)
> The mod_jk compilation *is* trivial and since they don't list on the website
In the web page:
For Linux:
apxs -o mod_jk.so -I../jk -I/usr/local/jdk/include -I/usr/local/jdk/include/linux -c
*.c ../jk/*.c
Your build may fail because the object files from the ../jk directory have been
compiled to the current directory, rather than their source directory.
Running gcc -shared -o mod_jk.so *.o should finish the build.
Now, this did not work with my system, a RH 6.2 with apache installed from source.
Yes, with DSO enabled.
The exact error is far away from my mind. I don't care anymore :)
> what version of Apache or Linux the binary is compiled for, it's pretty much
> useless. I'd say the number one problem post I have seen since joining this
It worked perfectly in RH 6.2 and RH 7.0. I'm willing to bet that it will work on many
more.
> list relates to the fact that the binary doesn't work on most people's
> systems. If you give somebody with relatively little experience a binary
> that's supposed to work and it doesn't, it only confuses the matter that
> much more.
No.. usually binaries are not a good solution.
> By the way, I'd be interested in hearing what your config is, since it
> worked for you.
I don't think the hardware would be an issue, then:
RH 6.2 (with official upgrades), apache 1.3.14 initially, but it has worked ever
since.
There's nothing more to it! :)
hugs, rms
--
+ No matter how much you do, you never do enough -- unknown
+ Whatever you do will be insignificant,
| but it is very important that you do it -- Ghandi
+ So let's do it...?
