What is the stable version of Perl for VMS.

2005-01-31 Thread John E. Malmberg
I notice that a lot of the tests here are on Perl 5.8.4, yet CPAN shows that the current version of Perl is 5.8.6. I am looking at building a version that supports the upcoming symlink support in OpenVMS, and wanted to know which base level of Perl I should start with. Also which baselevel has

Re: What is the stable version of Perl for VMS.

2005-01-31 Thread Craig A. Berry
At 7:07 AM -0500 1/31/05, John E. Malmberg wrote: >I notice that a lot of the tests here are on Perl 5.8.4, yet CPAN shows that >the current version of Perl is 5.8.6. 5.8.6 is current on all platforms. It has a couple of MakeMaker test failures on VMS that are unrelated to MakeMaker itself. Imm

Re: What is the stable version of Perl for VMS.

2005-01-31 Thread John E. Malmberg
On Mon, 31 Jan 2005, Craig A. Berry wrote: > At 7:07 AM -0500 1/31/05, John E. Malmberg wrote: > >> I am looking at building a version that supports the upcoming symlink >> support in OpenVMS, and wanted to know which base level of Perl I >> should start with. > > New development should be done ag

Re: What is the stable version of Perl for VMS.

2005-01-31 Thread Craig Berry
On Monday, January 31, 2005, at 08:39AM, John E. Malmberg <[EMAIL PROTECTED]> wrote: >I Would expect that it should be a reasonable restriction in at least >the short term if not longer, that the CONFIGURE.COM and build scripts for >Perl protect them selves from DECC$ feature logicals that prev

Minor ODS-5 build issue.

2005-01-31 Thread John E. Malmberg
It appears that only a handful of files have multiple dots in them, and as near as I can tell, on OpenVMS, these files are only referenced by the CONFIGURE.COM script. It should not be to hard to change the configure script to be able to automatically on Alpha/I64 if those files like changes5^.8.*

Re: Minor ODS-5 build issue.

2005-01-31 Thread Craig Berry
On Monday, January 31, 2005, at 03:00PM, John E. Malmberg <[EMAIL PROTECTED]> wrote: >It should not be to hard to change the configure script to be able to >automatically on Alpha/I64 if those files like changes5^.8.* are in the >multiple dot format or in an ODS-2 compatable name. Luckily I sel

LARGEFILE configure issue

2005-01-31 Thread John E. Malmberg
The configure tests for largefile support is based on if the integer type is native 64 bits. On VMS, the off_t type becomes 64 bits if the _LARGEFILE macro is defined in the test program. Which means logically the support for largefile on VMS should be based on the presences of off_t being detect

Re: LARGEFILE configure issue

2005-01-31 Thread Craig Berry
On Monday, January 31, 2005, at 04:40PM, John E. Malmberg <[EMAIL PROTECTED]> wrote: >The configure tests for largefile support is based on if the integer type >is native 64 bits. If you're looking at 5.8.6, all of the 64-bit tests were lumped together under 64-bit integers, which is just pla

Configuring socketpair() and statfs()

2005-01-31 Thread John E. Malmberg
It appears that the perl source wants HAS_SOCKETPAIR defined if the host supports SOCKETPAIR, but the configure script only knows how to define it if d_sockpair='define'. A bit inconsistent and confusing. Perl seems to know about the standard C routine fstatvfs() and the non-standard fstatfs().

Re: Configuring socketpair() and statfs()

2005-01-31 Thread Craig A. Berry
At 5:38 PM -0600 1/31/05, John E. Malmberg wrote: >It appears that the perl source wants HAS_SOCKETPAIR defined if the host >supports SOCKETPAIR, but the configure script only knows how to define it >if d_sockpair='define'. A bit inconsistent and confusing. It does seem there's a conflation of wh

Re: Configuring socketpair() and statfs()

2005-01-31 Thread John E. Malmberg
Craig A. Berry wrote: At 5:38 PM -0600 1/31/05, John E. Malmberg wrote: It appears that the perl source wants HAS_SOCKETPAIR defined if the host supports SOCKETPAIR, but the configure script only knows how to define it if d_sockpair='define'. A bit inconsistent and confusing. It does seem there's