Craig A. Berry wrote:
At 8:55 AM -0500 9/26/07, John E. Malmberg wrote:
With the upgrade, I am getting two failures in blead on OpenVMS Alpha.
Built with Non threaded build, large files, and experimental symbolic link
support on an ODS-5 volume.
None of the tests you report failing failed
At 8:55 AM -0500 9/26/07, John E. Malmberg wrote:
>With the upgrade, I am getting two failures in blead on OpenVMS Alpha.
>
>Built with Non threaded build, large files, and experimental symbolic link
>support on an ODS-5 volume.
None of the tests you report failing failed for me. My configuratio
Paul Marquess wrote:
From: John E. Malmberg [mailto:[EMAIL PROTECTED]
With the upgrade, I am getting two failures in blead on OpenVMS Alpha.
Built with Non threaded build, large files, and experimental symbolic
link support on an ODS-5 volume.
ODS-5 volume means that the traditional name ma
From: John E. Malmberg [mailto:[EMAIL PROTECTED]
> With the upgrade, I am getting two failures in blead on OpenVMS Alpha.
>
> Built with Non threaded build, large files, and experimental symbolic
> link support on an ODS-5 volume.
>
> ODS-5 volume means that the traditional name mangling of ext
With the upgrade, I am getting two failures in blead on OpenVMS Alpha.
Built with Non threaded build, large files, and experimental symbolic
link support on an ODS-5 volume.
ODS-5 volume means that the traditional name mangling of extra dots in
the filename on disk to be C<_> is not always be
Craig A. Berry wrote:
At 8:10 PM -0500 9/25/07, John E. Malmberg wrote:
Craig A. Berry wrote:
As far as I can tell, every other platform that has _LARGEFILE
support now makes it the default. It seems to me we should too. Any
reason not to?
I vote yes on the versions of VMS that support it
