jean-frederic clere wrote:
That needs a little more, because the *.lo files are in common are build before using LIBTOOL instead apxs.
When using the actual make in apache-2.0 the common/*.c are compiled and left in apache-2.0 but apxs looks for the *.lo in common: (that is with 2.0.40)
+++
gcc: ../common/jk_ajp14_worker.lo: No such file or directory
gcc: ../common/jk_md5.lo: No such file or directory
gcc: ../common/jk_ajp_common.lo: No such file or directory
gcc: ../common/jk_context.lo: No such file or directory
make: *** [mod_jk.la] Error 1
[EMAIL PROTECTED]:~/jakarta-tomcat-connectors/jk/native/apache-2.0 >
+++
Using VPATH=.:../common in Makefile and JK="" solves the problem but force to use gnu make.
hmm... straight configure and GNU make (native make won't work with mod_jk* on AIX) and it works
any chance that it worked with GNU make without any additional changes? (not saying that is good, just wondering if that is why I didn't see this issue)
gmake in jakarta-tomcat-connectors/jk/native builds correctly.
It fails only if "apxs -q LIBTOOLS" does not work and Apache-2.0 libtools is incompatible with the system one.
or maybe there is some path-related configure option I didn't test with?
cd jakarta-tomcat-connectors/jk/native gmake clean cd apache-2.0; gmake That should fail.
did you hit the problem on any of {Linux, AIX, FreeBSD, Tru64, Solaris, HP-UX}?
vtxclere is a Linux box.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
