jean-frederic clere wrote:
Henri Gomez wrote:
jean-frederic clere wrote:
Henri Gomez wrote:
jean-frederic clere wrote:
Henri Gomez wrote:
Günter Knauf wrote:
Hi,
http://jakarta.apache.org/~hgomez/jakarta-tomcat-connectors-jk-1.2.6/
I've just tried to build on Linux, and it breaks in jki_connect.c on two boxes, SuSE 7.2 and SuSE9, on the first because no in_addr_t, on the second because its defined as struct and not ulong;
furthermore I had exactly the same issue with another project, and we killed in_addr_t usage.
If you do a Google for in_addr_t you can directly see that this is a problem on many platforms, seems to me that some have it defined as unsigned long, others as struct, and the rest doesnt have it defined at all...
I will this weekend examine this further, unless someone beats me...
but I think this is a big showstopper, and we should probably hold the release until this is fixed...
Well I didn't have this problem on the 3 differents Liux distros :
- Fedora Core 2
- Suse 9.0 (i386)
- Suse 8.0 (PPC)
I see another problem autom4te.cache should be removed before doing the tarball.
I run the buildconf.sh. May be that's the problem ?
The problem is in buildconf.sh: I have fixed it.
If you leave autom4te.cache in the distribution and someone makes automake using a different automake than the one you have used when preparing the tarball *very* strange things will happend...
And for the portable.h was could we do ?
Adding portable.hnw for netware and portable.hw for windoze and #ifdef for AS400 is the clean way.
The quick way is adding: +++ #if !defined(WIN32) && !defined(AS400) && !defined(NETWARE) #include "portable.h" #endif +++
You understand why I wish a new JK using ONLY APR.
We spend too many times in such dreaded issues ;(
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
