RE: apache 1.319 + modssl 2.8.1 on windows
I'm having the same problem - the build process stops on mod_ssl.c showing lots of syntax errors in wincrypt.h (eg: "syntax error : identifier HRESULT") anyone know the solution to this? thanks, Eric --- At 07:33 AM 3/9/01 , you wrote: > > How far did you make it through INSTALL.Win32 before it failed? > > >Up to the build process, it crashed on mod_ssl.c. I downloaded >the 2.8.1 distribution and fetched the files you listed from CVSweb, >replaced them and started the build process. Perhaps you can >send me the files you used to compile? That would be great. What was the message when it crashed in mod_ssl.c? It could be having trouble finding the openssl include files. In addition to the two files listed earlier, I interpreted: >Install OpenSSL into $INSTALLTOP. You have do this by hand: > ... >$ copy /b inc32\* p:\openssl\include\openssl > ... To mean that the "p:\openssl\include\openssl" directory should contain the *.h files, not another directory named openssl that contains those files. Dave _ Get your FREE download of MSN Explorer at http://explorer.msn.com __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED]
RE: apache 1.319 + modssl 2.8.1 on windows
At 02:06 PM 03/22/2001 , you wrote: >I'm currently having the same problem: mod_ssl.c can't compile because it >finds lots of syntax errors in wincrypt.h (which obviously SHOULD compile >without errors, but it's having problems finding defns for HRESULT, DWORD, >etc.) > >Any idea how to fix this? >Thanks, >Eric Eric, Its probably better to write directly to the openssl group because then others can see the traffic and respond. The problem described in the email that you referenced was more specific and not as general as DWORD, I haven't seen that error compiling Apache. DWORD, and probably HRESULT are from windows, and unless Apache is changing them, then the problem is likely in the configuration of the your compiler, more specifically how it finds its own include files. That is my guess from what the little I have heard. Some checklist items to consider: (0) Have you tested the compiler installation with other code? (1) Are you compiling from the command line, or the VC GUI? I compiled mod_ssl from the command line, I don't know about compiling it from the GUI. (2) If you used the command line, then either the vcvars32.bat file needs to run first, or the equivalent configuration needs to occur, possibly when the compiler was installed. (3) I have been compiling pache with VC++ v6.0, it may work with earlier versions, but I don't know (4) What are the first few errors? It would be good to know if they are related to finding include files, and if so, which ones. Dave __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED]
Re: apache 1.319 + modssl 2.8.1 on windows
Jonathon, > forgot to say the reason i asked this is because > when i used the patched configure.bat from cvs to build > it comes back with file not found everytime i try to run it I think it is a reference to os\win32\MakeModuleMak.mak which should be to .cpp instead of .mak. You can run the configure.bat file with the option -v to make it output more details. peo <[EMAIL PROTECTED]> - Original Message - From: "Jonathon Douglas" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, March 08, 2001 11:13 AM Subject: Re: apache 1.319 + modssl 2.8.1 on windows > forgot to say the reason i asked this is because > when i used the patched configure.bat from cvs to build > it comes back with file not found everytime i try to run it > > - Original Message - > From: "Jan Dries" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, March 07, 2001 11:45 PM > Subject: Re: apache 1.319 + modssl 2.8.1 on windows > > > > Jonathon Douglas wrote: > > > > > > has anyone managed to get this comination to compile yet > > > (i havent atm) > > > > I have, using the patches that were posted on this newsgroup (and that > > have in the mean time been checked into CVS). Worked fine for me. > > The only surprise was that it builds dynamic modules with a different > > name and extension than in 1.3.14 (my previous version), i.e. it now > > creates a "mod_ssl.so" instead of an "ApacheModuleSSL.dll". > > > > Regards, > > Jan > > __ > > Apache Interface to OpenSSL (mod_ssl) www.modssl.org > > User Support Mailing List [EMAIL PROTECTED] > > Automated List Manager[EMAIL PROTECTED] > __ > Apache Interface to OpenSSL (mod_ssl) www.modssl.org > User Support Mailing List [EMAIL PROTECTED] > Automated List Manager[EMAIL PROTECTED] > __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED]
Re: apache 1.319 + modssl 2.8.1 on windows
forgot to say the reason i asked this is because when i used the patched configure.bat from cvs to build it comes back with file not found everytime i try to run it - Original Message - From: "Jan Dries" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 07, 2001 11:45 PM Subject: Re: apache 1.319 + modssl 2.8.1 on windows > Jonathon Douglas wrote: > > > > has anyone managed to get this comination to compile yet > > (i havent atm) > > I have, using the patches that were posted on this newsgroup (and that > have in the mean time been checked into CVS). Worked fine for me. > The only surprise was that it builds dynamic modules with a different > name and extension than in 1.3.14 (my previous version), i.e. it now > creates a "mod_ssl.so" instead of an "ApacheModuleSSL.dll". > > Regards, > Jan > __ > Apache Interface to OpenSSL (mod_ssl) www.modssl.org > User Support Mailing List [EMAIL PROTECTED] > Automated List Manager[EMAIL PROTECTED] __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED]
Re: apache 1.319 + modssl 2.8.1 on windows
jan is there any chance you could post the compiled files to the contrib area on modssl.org tia - Original Message - From: "Jan Dries" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, March 07, 2001 11:45 PM Subject: Re: apache 1.319 + modssl 2.8.1 on windows > Jonathon Douglas wrote: > > > > has anyone managed to get this comination to compile yet > > (i havent atm) > > I have, using the patches that were posted on this newsgroup (and that > have in the mean time been checked into CVS). Worked fine for me. > The only surprise was that it builds dynamic modules with a different > name and extension than in 1.3.14 (my previous version), i.e. it now > creates a "mod_ssl.so" instead of an "ApacheModuleSSL.dll". > > Regards, > Jan > __ > Apache Interface to OpenSSL (mod_ssl) www.modssl.org > User Support Mailing List [EMAIL PROTECTED] > Automated List Manager[EMAIL PROTECTED] __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED]
RE: apache 1.319 + modssl 2.8.1 on windows
> It could be having trouble finding the openssl include files. > > In addition to the two files listed earlier, I interpreted: > > >Install OpenSSL into $INSTALLTOP. You have do this by hand: > > ... > >$ copy /b inc32\* p:\openssl\include\openssl > > ... YES, it was this one... SSL_INC and SSL_LIB were wrong: SSL_INC =p:\openssl-0.9.6\include SSL_LIB =p:\openssl-0.9.6\lib They should be: SSL_INC =p:\openssl-0.9.6\inc32 SSL_LIB =p:\openssl-0.9.6\out32dll __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED]
RE: apache 1.319 + modssl 2.8.1 on windows
At 07:33 AM 3/9/01 , you wrote: > > How far did you make it through INSTALL.Win32 before it failed? > > >Up to the build process, it crashed on mod_ssl.c. I downloaded >the 2.8.1 distribution and fetched the files you listed from CVSweb, >replaced them and started the build process. Perhaps you can >send me the files you used to compile? That would be great. What was the message when it crashed in mod_ssl.c? It could be having trouble finding the openssl include files. In addition to the two files listed earlier, I interpreted: >Install OpenSSL into $INSTALLTOP. You have do this by hand: > ... >$ copy /b inc32\* p:\openssl\include\openssl > ... To mean that the "p:\openssl\include\openssl" directory should contain the *.h files, not another directory named openssl that contains those files. Dave __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED]
RE: apache 1.319 + modssl 2.8.1 on windows
> How far did you make it through INSTALL.Win32 before it failed? > Up to the build process, it crashed on mod_ssl.c. I downloaded the 2.8.1 distribution and fetched the files you listed from CVSweb, replaced them and started the build process. Perhaps you can send me the files you used to compile? That would be great. Daniel __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED]
RE: apache 1.319 + modssl 2.8.1 on windows
At 06:18 AM 3/9/01 , you wrote: > > Oops! I had the name for file (2) wrong, I think this is correct: > > > > The Apache_1.3.19 and modssl_2.8.1 source file from March 3 > > needs the following from the CVSWeb: > > (1) [modssl] / mod_ssl / pkg.mod_ssl / configure.bat > > (2) [modssl] / mod_ssl / pkg.mod_ssl / pkg.sslmod / Makefile.win32 >I'm trying to compile it on Win2k without success. Can you tell me >exactly, which files you used to get it compiled. Were you able to find these files and figure out where they go? How far did you make it through INSTALL.Win32 before it failed? After I found these two files, it still didn't work, so I deleted all the build directories, reinstalled all the source files, and started over. After that it was just a matter of typing. Dave __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED]
RE: apache 1.319 + modssl 2.8.1 on windows
> Oops! I had the name for file (2) wrong, I think this is correct: > > The Apache_1.3.19 and modssl_2.8.1 source file from March 3 > needs the following from the CVSWeb: > (1) [modssl] / mod_ssl / pkg.mod_ssl / configure.bat > (2) [modssl] / mod_ssl / pkg.mod_ssl / pkg.sslmod / Makefile.win32 I'm trying to compile it on Win2k without success. Can you tell me exactly, which files you used to get it compiled. Thx, Daniel __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED]
Re: apache 1.319 + modssl 2.8.1 on windows
Jonathon Douglas wrote: > > can someone put a precompiled version of apache1.3.19/modssl 2.81 > in the modssl contrib as i still cant get it to even after downloading from > cvs > configure.bat comes back with "file not found" for some reason I just uploaded a file called "apache-modssl-1.3.19-2.8.1-win32.zip" in the contrib section. It's the zipped result of: nmake /f Makefile.win installr INSTDIR="C:/Apache" Regards, Jan __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED]
Re: apache 1.319 + modssl 2.8.1 on windows
Oops! I had the name for file (2) wrong, I think this is correct: The Apache_1.3.19 and modssl_2.8.1 source file from March 3 needs the following from the CVSWeb: (1) [modssl] / mod_ssl / pkg.mod_ssl / configure.bat (2) [modssl] / mod_ssl / pkg.mod_ssl / pkg.sslmod / Makefile.win32 At 03:36 PM 03/08/2001 , you wrote: >can someone put a precompiled version of apache1.3.19/modssl 2.81 >in the modssl contrib as i still cant get it to even after downloading from >cvs >configure.bat comes back with "file not found" for some reason > >tia >- Original Message - >From: "Cliff Woolley" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Thursday, March 08, 2001 1:21 AM >Subject: Re: apache 1.319 + modssl 2.8.1 on windows > > > > On Thu, 8 Mar 2001, Jan Dries wrote: > > > > > The only surprise was that it builds dynamic modules with a different > > > name and extension than in 1.3.14 (my previous version), i.e. it now > > > creates a "mod_ssl.so" instead of an "ApacheModuleSSL.dll". > > > > FYI, that's a change in Apache as a whole, not just mod_ssl. (1.3.17 used > > .so, too, IIRC.) There were several reasons for the change: to > > standardize names with those used by Unix builds of Apache, to avoid the > > default Windows behavior of hiding all .DLL files, and to avoid the > > possibility of confusing shared objects from other programs (eg IIS) with > > those for Apache. There were probably other reasons as well. =-) > > > > --Cliff > > > > -- > >Cliff Woolley > >[EMAIL PROTECTED] > >Charlottesville, VA > > > > > > __ > > Apache Interface to OpenSSL (mod_ssl) www.modssl.org > > User Support Mailing List [EMAIL PROTECTED] > > Automated List Manager[EMAIL PROTECTED] > >__ >Apache Interface to OpenSSL (mod_ssl) www.modssl.org >User Support Mailing List [EMAIL PROTECTED] >Automated List Manager[EMAIL PROTECTED] __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED]
Re: apache 1.319 + modssl 2.8.1 on windows
The Apache_1.3.19 and modssl_2.8.1 source file from March 3 needs the following from the CVSWeb: (1) [modssl] / mod_ssl / pkg.mod_ssl / configure.bat (2) [modssl] / mod_ssl / pkg.mod_ssl / pkg.sslmod / Makefile.w32 At 03:36 PM 03/08/2001 , you wrote: >can someone put a precompiled version of apache1.3.19/modssl 2.81 >in the modssl contrib as i still cant get it to even after downloading from >cvs >configure.bat comes back with "file not found" for some reason > >tia >- Original Message - >From: "Cliff Woolley" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Thursday, March 08, 2001 1:21 AM >Subject: Re: apache 1.319 + modssl 2.8.1 on windows > > > > On Thu, 8 Mar 2001, Jan Dries wrote: > > > > > The only surprise was that it builds dynamic modules with a different > > > name and extension than in 1.3.14 (my previous version), i.e. it now > > > creates a "mod_ssl.so" instead of an "ApacheModuleSSL.dll". > > > > FYI, that's a change in Apache as a whole, not just mod_ssl. (1.3.17 used > > .so, too, IIRC.) There were several reasons for the change: to > > standardize names with those used by Unix builds of Apache, to avoid the > > default Windows behavior of hiding all .DLL files, and to avoid the > > possibility of confusing shared objects from other programs (eg IIS) with > > those for Apache. There were probably other reasons as well. =-) > > > > --Cliff > > > > -- > >Cliff Woolley > >[EMAIL PROTECTED] > >Charlottesville, VA > > > > > > __ > > Apache Interface to OpenSSL (mod_ssl) www.modssl.org > > User Support Mailing List [EMAIL PROTECTED] > > Automated List Manager[EMAIL PROTECTED] > >__ >Apache Interface to OpenSSL (mod_ssl) www.modssl.org >User Support Mailing List [EMAIL PROTECTED] >Automated List Manager[EMAIL PROTECTED] __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED]
Re: apache 1.319 + modssl 2.8.1 on windows
can someone put a precompiled version of apache1.3.19/modssl 2.81 in the modssl contrib as i still cant get it to even after downloading from cvs configure.bat comes back with "file not found" for some reason tia - Original Message - From: "Cliff Woolley" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, March 08, 2001 1:21 AM Subject: Re: apache 1.319 + modssl 2.8.1 on windows > On Thu, 8 Mar 2001, Jan Dries wrote: > > > The only surprise was that it builds dynamic modules with a different > > name and extension than in 1.3.14 (my previous version), i.e. it now > > creates a "mod_ssl.so" instead of an "ApacheModuleSSL.dll". > > FYI, that's a change in Apache as a whole, not just mod_ssl. (1.3.17 used > .so, too, IIRC.) There were several reasons for the change: to > standardize names with those used by Unix builds of Apache, to avoid the > default Windows behavior of hiding all .DLL files, and to avoid the > possibility of confusing shared objects from other programs (eg IIS) with > those for Apache. There were probably other reasons as well. =-) > > --Cliff > > -- >Cliff Woolley >[EMAIL PROTECTED] >Charlottesville, VA > > > __ > Apache Interface to OpenSSL (mod_ssl) www.modssl.org > User Support Mailing List [EMAIL PROTECTED] > Automated List Manager[EMAIL PROTECTED] __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED]
Re: apache 1.319 + modssl 2.8.1 on windows
On Thu, 8 Mar 2001, Jan Dries wrote: > The only surprise was that it builds dynamic modules with a different > name and extension than in 1.3.14 (my previous version), i.e. it now > creates a "mod_ssl.so" instead of an "ApacheModuleSSL.dll". FYI, that's a change in Apache as a whole, not just mod_ssl. (1.3.17 used .so, too, IIRC.) There were several reasons for the change: to standardize names with those used by Unix builds of Apache, to avoid the default Windows behavior of hiding all .DLL files, and to avoid the possibility of confusing shared objects from other programs (eg IIS) with those for Apache. There were probably other reasons as well. =-) --Cliff -- Cliff Woolley [EMAIL PROTECTED] Charlottesville, VA __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED]
Re: apache 1.319 + modssl 2.8.1 on windows
Jonathon Douglas wrote: > > has anyone managed to get this comination to compile yet > (i havent atm) I have, using the patches that were posted on this newsgroup (and that have in the mean time been checked into CVS). Worked fine for me. The only surprise was that it builds dynamic modules with a different name and extension than in 1.3.14 (my previous version), i.e. it now creates a "mod_ssl.so" instead of an "ApacheModuleSSL.dll". Regards, Jan __ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager[EMAIL PROTECTED]
