Sometime since 5.8.0, glob has stopped working in miniperl on VMS:
$ mcr []miniperl -e "glob('foo');"
Can't load module Fcntl, dynamic loading not available in this perl.
(You may need to build a new perl executable which either supports
dynamic loading or has the Fcntl module statically linked into it.)
at /perl_root/lib/File/Temp.pm line 127
Compilation failed in require at /perl_root/lib/File/Temp.pm line 127.
BEGIN failed--compilation aborted at /perl_root/lib/File/Temp.pm line 127.
Compilation failed in require at -e line 1.
BEGIN failed--compilation aborted.
I'm not sure what's changed lately, i.e., whether it's File::Temp that
has started requiring Fcntl or something about glob that has started
using PerlIO_tmpfile, which in turn loads File::Temp. The most pressing
side effect of this is that various MakeMaker utilities depend on using
glob in miniperl.
It seems to me the more general question is whether it's ok for
PerlIO_tmpfile to require dynamic loading. Will other platforms never
need this in miniperl?
If VMS is the only platform that will need PerlIO_tmpfile in miniperl I
can probably cook up an alternative tmpfile routine for VMS; in fact
we've already got a Perl_my_tmpfile in vms.c that may just need to have
its FILE* return value imported to PerlIO*.
A side note: the variable "sv" in PerlIO_tmpfile is checked for truth
before it is ever used, so it will always have its null initialized
value; am I missing something?
