(OT) apache and modperl and cygwin

nop has asked for the wisdom of the Perl Monks concerning the following question:

Hi -- Sorry for a slighly non-perl question but I am quite stuck and am wondering if any Monks can offer advice.

Disclaimer: I am quite new to Apache and mod_perl.

I'm trying to develop code on a windows box to later run unchanged on a linux apache production server. I first tried the native win apache binaries with indigo mod-perl. The problem is that that system (I believe) doesn't support libapreq, so I can't use Apache::Cookie or Apache::Logfile. I don't a windows C++ compiler so I couldn't / didn't want to try compiling Apache on windows.

So next I opted to install Cygwin and try to run Apache thru it. I used the Cygwin setup.exe program and asked for 'install everything', which it did, and which (I think) should have included Apache. Cygwin seems to have installed OK; I can run the shell and emacs and the windowing system and such. However, while the apache docs are there, and apachectl and httpd.exe are there, I can not start apache, either from w/in Cygwin or from outside. Here's an example

AAA@sam /usr/sbin
$ ls ap*
apachectl  apxs

AAA@sam /usr/sbin
$ apachectl
bash: apachectl: command not found
[download]

Here's another

AAA@sam ~
$ httpd
bash: httpd: command not found
[download]

I am quite confused.
Can someone suggest the how I can run apache on a win box and use Apache::Cookie and Apache::Logfile?

Many thanks

nop

Comment on (OT) apache and modperl and cygwin Select or Download Code

Replies are listed 'Best First'.
Re: (OT) apache and modperl and cygwin by steves (Curate) on Feb 15, 2003 at 11:21 UTC
What version of Apache? I tried 2.0 a month or two ago and there was no libapreq generally available that worked. There was one posted somewhere that some said they got working but the Apache guys on the libapreq mailing list said it would be best to stick with the 1.3 path for a while if I needed a stable, working libapreq. The disclaimer here is that I haven't gotten back to that for a few months so a lot may have changed.	[reply]
Re: (OT) apache and modperl and cygwin by Enlil (Parson) on Feb 15, 2003 at 11:41 UTC
I am just guessing but is `/usr/sbin/` in your path? is `.` in your path? I am going to guess neither is, so you have to either go to the /usr/sbin directory and type: `./apachectl start` [download] or from any prompt the command: `/usr/sbin/apachectl start` [download] For more info look here -enlil	[reply] [d/l] [select]
Re: (OT) apache and modperl and cygwin by tachyon (Chancellor) on Feb 15, 2003 at 11:19 UTC
Why not use vmware or similar to create a virtual nux machine on your Windows box. You set up the virtual machine and then install nix on it plus Apache etc. The main advantage of this is that this machine can be IDENTICAL to your production box (almost down to the last detail) so the transfer will almost inevitably work or a the very least be pretty painless. Although this will work the cheapest option would be to buy and old 586/686 for less than $100 and put up a *nix development server. Now as to your problem. The first error shows that neither . or /usr/sbin/ are in you path (command not found) so try calling apachectl with the full path (or as ./apachectl if you are in /usr/sbin). If you can't find a working Apache on your cygwin install just build it from source from the tarball. It is usually fairly painless. You will have gcc...... cheers tachyon s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print	[reply]


more useful options
	PerlMonks