Following recent changes to the Win32 canned configs and makedef.pl, I
find that after building an out-of-the-box perl (with ithreads et al)
miniperl -V is rather confused:
C:\p5p\bleadperl>.\miniperl -V
Summary of my perl5 (revision 5 version 9 subversion 3) configuration:
Platform:
osname=MSWin32, osvers=5.1, archname=MSWin32-x86-multi-thread
uname=''
config_args='undef'
hint=recommended, useposix=true, d_sigaction=undef
usethreads=define useithreads=define usemultiplicity=define
useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
use64bitint=undef use64bitall=undef uselongdouble=undef
usemymalloc=n, bincompat5005=undef
[...]
Characteristics of this binary (from libperl):
Compile-time options: PERL_DONT_CREATE_GVSV PERL_MALLOC_WRAP
Notice that the "Compile-time options" doesn't include USE_ITHREADS, but
the "Platform" section says "useithreads=define".
The reason is that miniperl was built without ithreads (hence it is
correctly not in "Compile-time options"), but perl was built with
ithreads, so lib/Config_heavy.pl contains useithreads='define', which
miniperl uses too!
I suggested previously that much of the "Platform" section could now be
dropped since it is mostly contained in "Compile-time options" now
anyway
(http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2005-07/msg00624.html).
Another possibility is perhaps for miniperl to not print
Config::myconfig() (if perl.c knows that it is in miniperl).
I guess the output of things like ".\miniperl -V:useithreads" would
still be wrong, though. Sigh...
------------------------------------------------
Radan Computational Ltd.
The information contained in this message and any files transmitted with it are
confidential and intended for the addressee(s) only. If you have received this
message in error or there are any problems, please notify the sender
immediately. The unauthorized use, disclosure, copying or alteration of this
message is strictly forbidden. Note that any views or opinions presented in
this email are solely those of the author and do not necessarily represent
those of Radan Computational Ltd. The recipient(s) of this message should
check it and any attached files for viruses: Radan Computational will accept no
liability for any damage caused by any virus transmitted by this email.
