Hi again, Well your patch gets the 2.1 CVS to compile all the way to the bottom, so it is a viable fix/work-around so far.... One question... proxybalancer comes out as proxybalancer.nlm ... is it still a requirement for 8.3 filenames?
Thanks for the reply, Norm ----- Original Message ----- From: "Guenter Knauf" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, August 16, 2004 2:49 PM Subject: Re: Proxy_ajp - build problem - NetWare Hi, since I doubt we get the apr_socket functions to use apr_byte_t instead of char in the near future, attached the patch for the makefile wich makes the compiler as 'tolerant' as others... Guenter. > Get the following while trying a build on a NetWare platform form CVS 2.1 > HEAD: > Generating Release\proxyajp_cc.opt > Compiling proxy_ajp.c > Compiling proxy_util.c > Compiling c:\projects\gccnlm\ajplib/ajp_header.c > Compiling c:\projects\gccnlm\ajplib/ajp_msg.c > Compiling c:\projects\gccnlm\ajplib/ajp_link.c > ### mwccnlm Compiler: > # File: ..\..\..\ajplib\ajp_link.c > # ----------------------------------- > # 101: status = ilink_read(sock, msg->buf, hlen); > # Error: ^ > # illegal implicit conversion from 'unsigned char *' to > # 'char *' > ### mwccnlm Compiler: > # 117: status = ilink_read(sock, msg->buf + hlen, blen); > # Error: ^ > # illegal implicit conversion from 'unsigned char *' to > # 'char *' > Major problem is that apr.h (AprLib 1.0) defines _apr_byte_t as unsigned > char, > whereas the ilink_read() function defines the buffer pointer to be of type > char*... yeah, but whatever we do, I think finally when we come to the socket functions we have to deal again with char instead of apr_byte_t; so for now the only way around is to add a compiler flag -relax_pointers to the XCFGAGS in the Makefile. I've already asked about this problem in [EMAIL PROTECTED], but got no answer: http://marc.theaimsgroup.com/?l=apr-dev&m=109103978113824&w=2 Guenter.
