You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@perl.apache.org by Alessandro Forghieri <al...@orion.it> on 2002/04/17 18:45:31 UTC
Win32 threading
Greetings.
I guess this qualifies as dumb question however:
i) will the interpreter feature work on Win32 AS perl? (-dUSEITHREADS)
[I guess no - the doc says it needs -DUSETHREADS]
ii) if answer to (i) is no, I then will have to rebuild perl to profit
from the interpreter pool - is there a way (directive) to tell modperl
whichinterpreter it should run - other than the one it is found in its "PATH"?
BTW, this feature (sepcifying the interpreter path from within httpd.conf)
would be interesting in its own right, given that modifying the
environment forservices is nowhere close to easy/convenient.
Cheers,
alf
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: Win32 threading
Posted by Doug MacEachern <do...@covalent.net>.
On Wed, 17 Apr 2002, Alessandro Forghieri wrote:
> Greetings.
> I guess this qualifies as dumb question however:
>
> i) will the interpreter feature work on Win32 AS perl? (-dUSEITHREADS)
> [I guess no - the doc says it needs -DUSETHREADS]
yes, AS implemented ithreads and enable it in all their builds. modperl
would not let you build without ithreads on win32.
> ii) if answer to (i) is no, I then will have to rebuild perl to profit
> from the interpreter pool - is there a way (directive) to tell modperl
> whichinterpreter it should run - other than the one it is found in its "PATH"?
>
> BTW, this feature (sepcifying the interpreter path from within httpd.conf)
> would be interesting in its own right, given that modifying the
> environment forservices is nowhere close to easy/convenient.
the interpreter is embedded in the server, so this concept wouldn't apply.
however, one very nice feature of win32 perl is that it relocates itself
at runtime (adjusting @INC paths), you can simply configure
LoadFile c:/fooperl/bin/perl58.dll
and modperl will use that perl installation, provided it is binary
compatible with the perl that was used to build modperl.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org