I cannot believe what I have done to myself, cuz I remember this from the
HOWTO very well. It seemed for me that this would be a problem in case the
../jk directory wasn't in the right place. But I admit (and right now feel
that I waisted my time... ) when I read it now, I certainly see what is meant.
Well, thanks for the efoort anyway.
Benoit Jacquemont wrote:
> Really happy that worked for you.
>
> But, anyway and just for information (;-) ), this solution comes directly
> from the mod_jk-howto.html file from the Jakarta project documentation...
>
> Yes it's written in small characters, but it is written... ;-)
>
> Extract from the mod_jk-howto.html:
> "
> 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.
> "
>
> Benoît
>
> > It worked for me too!
> >
> > Thanks a lot, unbelievable simple solution for what I thought already was
> > impossible.
> >
> > Thanks again,
> >
> > Klaas-Pieter
> >
> > Benoit Jacquemont wrote:
> > > I had the same problem some months ago.
> > >
> > > In fact, all the object files have been compiled, now you just need to
> > > build the mod_jk.so from them:
> > > Just go to the directory where the objects files are located and try:
> > >
> > > gcc -shared -o mod_jk.so *.o
> > >
> > > You will get a mod_jk.so file.
> > >
> > > It worked for me very fine, so I hope it will be the same for you.
> > >
> > > Benoît
