Yea. If I just install Apache using the MSI installer, it automatically sets up the service, and it works dandy. After I install the mod_perl 1.x PPM package from the uwinnipeg.ca site, the service no longer starts apache. Even if I use apache -k to remove, then re-add the service. I think it may have something to do with the path to Perl not being in the environment, and I don't know where that should get set.
For now, I've been just opening up a new cmd.exe window and running it from the command line, but obviously that isn't the preferred solution. Here's what I've done to get Apache and mod_perl to work under Cygwin: cd /lib/perl5/5.6.1/cygwin-multi/CORE ln -s libperl5_6_1.a libperl.a unzip apache_1.3.24-win32-src.zip tar xvfz mod_perl-1.27.tar.gz cd mod_perl-1.27 vi apaci/mod_perl.config.sh # insert #!/bin/bash as the very first line perl Makefile.PL USE_APACI=1 EVERYTHING=1 DO_HTTPD=1 \ PERL_EXTRA_CFLAGS=-DUSEIMPORTLIB make make install cd ../apache_1.3.24 make install cd /usr/local/apache vi conf/httpd.conf conf/startup.pl bin/apachectl start For some reason, the mod_perl.config.sh wasn't getting executed because it was missing the hash bang line. This caused some Makefiles to get messed up, most notably apache_1.3.24/src/modules/perl/Makefile. Things like CC and AR were not getting defined correctly, so nothing worked. Hopefully your httpd.h problem was caused by that too. Because that link to libperl.a in Cygwin wasn't there, dllwrap couldn't resolve symbols. Eventually found the fix for that (create a link) in the mod_perl archives. An important thing to do is ensure that the whole Makefile.PL/configure stage proceeds without any warnings or errors. If there are any warnings, they probably will cause problems during the compile. If my steps above don't work for you, maybe quickly check that Apache compiles on its own (./configure && make), you never know. By the way, how well does PostgreSQL >= 7.2 work on Win32? I'm been wanting to port an app that's currently using SQL Server 2000 (eek, $$$$, ODBC) to PostgreSQL. Since there are next to no benchmarks comparing the too on the net (darn MS EULA's), I'll probably end up doing some of my own benchmarks to prove to my client that performance will be similiar. southernstar wrote: > Hi Wim, > > Is that the Win32 service, that you can get to in the control panel administrative >tools -> services? So apache starts manually okay but not as a service? Maybe it >needs TCP/IP to start first so it should have dependencies which need to start before >it does. I did this when trying to start postgresql using the win32 control panel. >Had to start ipc-daemon first. (That still doesn't work either - only works with a >manual startup at the cygwin bash shell.) > > I think I will get rid of cygwin's perl and install activeperl, then install a >source code kit from apache like you did (my apache has cygwin patches which may have >buggered things up.) Then I'll try for mod_perl 1.27 and see if that works. If it >does I'll send you mail and let you know what I've done (any changes etc.) In the >mean time if you get yours working be sure to give me a yell. > > Best of luck, > James > > > >>I tried it a couple of weeks ago, and ran into some problems too. I'm >>pretty sure it was a different issue though. At the moment I'm >>reinstalling Cygwin, since I've rebuilt my development system since then. >> >>At the moment, I've installed ActivePerl-5.6.1.631, >>apache_1.3.25-win32-x86-src.msi from apache.org, and mod_perl 1.x using >>the instructions at http://theoryx5.uwinnipeg.ca/win32_apache2.html. >>Works fine for me... except the apache service doesn't start. I haven't >>had a chance to look into that yet though. >> >>Wim >> >
