On Mon, 30 Oct 2000, Peter J. Farley III wrote:
> At 02:58 PM 10/30/00 -0800, Peter Prymmer wrote:
> <Snipped>
> >This was with the perl@7483 kit: the build was fine (no need to
> >mess with vms/vms_yfix.pl), but there were two test failures:
> >
> >[.lib]st-lock...........FAILED on test 1
>
> Peter, does VMS have the same lack of functionality for file locking
> that DJGPP/DOS does (i.e., no working versions of flock or lockf or
> fcntl(...,F_SETLK/W,...))? If so, look at the changes I helped put
> into both t/lib/st-lock.t and ext/Storable/Storable.pm for
> DJGPP. Essentially, the changes made the locking versions of
> store/retrieve and the tests for them no-ops if ($^O eq 'dos'). If VMS
> has the same problem, it would be easy to add VMS to those no-op tests.
>
> HTH
Thanks. The real fix would appear to be set d_fcntl='undef' in
VMS's config.sh. While there is an fcntl() routine in the RTL and there
are *LOCK* constants, one cannot use fcntl() for locking. The default
for open files on VMS is that they are not shared. One has to pass
certain non POSIX compliant extensions to fopen() in order to open a file
for sharing on VMS. It's actually a mystery why the fcntl is so unhelpful
in this regard.
Thanks for your tip. If mucking with configure.com does not do it,
I'll take a look at the dos methods.
Peter Prymmer
