From: "Greg Stein" <[EMAIL PROTECTED]> To: "William A. Rowe, Jr." <[EMAIL PROTECTED]>
> On Wed, Nov 29, 2000 at 11:08:14AM -0800, William A. Rowe, Jr. wrote: > > From: "Greg Stein" <[EMAIL PROTECTED]> > > To: <new-httpd@apache.org> > > > > > > > I just made some changes to mpm/winnt/, but couldn't compile them. Since > > > it > > > was basically just tweaking the types, could you update from CVS and see > > > if > > > it still compiles properly? > > > > Dirtier than ****, but it -does- compile. Lots of emits on misparsing the > > const (non-recursive const behavior.) Ohy vey. > > I'm not sure that I understand the problem. Is it that MSVC doesn't like > seeing two "const" markers in a type? src\lib\apr\misc\unix\getopt.c(65) : warning C4090: 'function' : different 'const' qualifiers src\lib\apr\misc\unix\getopt.c(65) : warning C4022: 'memcpy' : pointer mismatch for actual parameter 1 src\modules\mpm\winnt\service.c(605) : warning C4090: 'function' : different 'const' qualifiers src\modules\mpm\winnt\service.c(605) : warning C4022: 'memcpy' : pointer mismatch for actual parameter 1 and ditto at (609), (706), (709), (713) and (1072) > > Otoh, apr_file_lock broke win32, and I have a few other priorities on the > > plate today. I'll get there as I can > > *nod* ... I had some code in mod_dav 1.0 to do the locking on Windows, but > it used a file descriptor. The apr_file_t structure only had a HANDLE, so I > wasn't sure where to go with that. I guessed as much, and will tackle this asap
