Hendrik Van Belleghem schrieb am 2001-05-27, 14:43:
> > That will only work with ActiveStates Perl. ActiveState == Microsoft.
>
> I quote :
> "I am trying to install the MAIL::tools module in windows 2000."
>
> Therefor I can assume he's using ActivePerl...
> Last time I check ActiveState wasn't bought by Microsoft :)
Are you sure???
ActivePerl came with WinNT ResourceKit, maybe earlier...
Everyone who hears 'WinXXX' thinks 'ActiveStatePerl', so it is
defacto M*crosoft.
> Other 'versions' (as in Platforms) of Perl usually come with CPAN.pm, which
> has similar functionality but compiles the modules...
CPAN.pm is included in AStates Perl too.
> > Another Perl comes not with PPM.
> >
There are several other Perl's for Windows like Siemens-Perl,
IndigoPerl, Perl for Cygwin, and some more, there is one with
Apache and mod_perl combined and so on.
I am sick of ActiveState, don't ask me why, everyone always points
you to ActiveState, if you need Perl for Windows, but it is not the
best for everyone.
I like much more Indigo-Perl, which comes with Apache included!
They got their own package system, which is compatible with .ppd
so you can use AStates modules.
If i would use Perl for a Production System i would prefer Siemens-Perl,
there are a lot of helpful modules included. If there is need to include
some more, i'm sure i am able to use my Borland or Microsoft Compiler to
build them.
Now i don't want to flame against ActiveState or someone else, but I want
to point out, that there are much more possibilties to get a perl on windows
running.
Best option is, as i mentioned earlier:
Get a compiler. I used 'Borland 5.02 C++' to build me a native Perl on
Windo*s. If you don't want to BUY a compiler, get Cygwin, there is 'gcc'
and all the other tools.
Then build your own Perl.
What is a programmer without a C compiler???
Only 'using' Perl is boring.
Only using precompiled versions of software is boring.
There are lot of modules at ActiveStates Site, but always the one i want
tto use/test isn't there... Maybe it doesn't fit on Windows, maybe it is
just because they didn't port it, what do you do now???
I was sick of it, now i'm using my own perl:
Siebenschlaefer@LORELEY /usr/cache
$ perl -V
Summary of my perl5 (revision 5.0 version 7 subversion 17) configuration:
Platform:
osname=cygwin, osvers=1.3.2(0.3932), archname=cygwin-multi
uname='cygwin_nt-4.0 loreley 1.3.2(0.3932) 2001-05-20 23:28 i686
unknown '
config_args='-de -Dusedevel -Dusemultiplicity'
hint=recommended, useposix=true, d_sigaction=define
usethreads=undef use5005threads=undef useithreads=undef
usemultiplicity=define
useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
use64bitint=undef use64bitall=undef uselongdouble=undef
Compiler:
cc='gcc', ccflags ='-DPERL_USE_SAFE_PUTENV -fno-strict-aliasing -
I/usr/local/include',
optimize='-O2',
cppflags='-DPERL_USE_SAFE_PUTENV -fno-strict-aliasing -
I/usr/local/include'
ccversion='', gccversion='2.95.3-4 (cygwin special)', gccosandvers=''
intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t',
lseeksize=4
alignbytes=8, usemymalloc=y, prototype=define
Linker and Libraries:
ld='ld2', ldflags =' -L/usr/local/lib'
libpth=/usr/local/lib /usr/lib /lib
libs=-lgdbm -ldb -lcrypt -liconv -lcygipc
perllibs=-lcrypt -liconv -lcygipc
libc=/usr/lib/libc.a, so=dll, useshrplib=true, libperl=libperl5_7_1.a
Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=dll, d_dlsymun=undef, ccdlflags=' '
cccdlflags=' ', lddlflags=' -L/usr/local/lib'
Characteristics of this binary (from libperl):
Compile-time options: MULTIPLICITY USE_LARGE_FILES PERL_IMPLICIT_CONTEXT
Locally applied patches:
DEVEL10175
Built under cygwin
Compiled at May 24 2001 22:05:40
%ENV:
PERLIO="stdio"
@INC:
/usr/local/lib/perl5/5.7.1/cygwin-multi
/usr/local/lib/perl5/5.7.1
/usr/local/lib/perl5/site_perl/5.7.1/cygwin-multi
/usr/local/lib/perl5/site_perl/5.7.1
/usr/local/lib/perl5/site_perl
.
gph
--
=^..^=
