Thanks very much for your reply Stas. Pardon my ignorance, but are you saying I need to rebuild Perl with different options. The version of Perl I'm using is the packaged one I installed with the cygwin install utility. If this is the case, could you please a little more information as to the arguments you recommend to build a version of Perl that works fine 'standalone', as well as embedded (which I presume is the case with mod-perl) if that is possible.
Steve -----Original Message----- From: Stas Bekman [mailto:[EMAIL PROTECTED]] Sent: Monday, 17 February 2003 4:03 PM Cc: Steve Baldwin; [EMAIL PROTECTED] Subject: Re: Building mod-perl 2 for cygwin > We can take two approaches, patch all the places in the code where > perl > context is set explicitly to use #ifdef MULTIPLICITY, rather than #ifdef > USE_THREADS. Or we can refuse to build mod_perl if MULTIPLICITY is > enabled without the threads. Of course the first solution is more > favorable for users. I've played a bit with various options and it seems that it's going to be a big trouble to support MULTIPLICITY without USE_THREADS. My suggestion for now is to either rebuild with -Uusemultiplicity or -Dusethreads (less preferred if you don't need threads, but need speed). README.cygwin says: =item * C<-Dusemultiplicity> Multiplicity is required when embedding Perl in a C program and using more than one interpreter instance. This works with the Cygwin port. Though I can't see that this is a required option. __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
