Craig quoted me:

> At 7:37 PM -0700 8/20/02, Alan Winston - SSRL Central Computing wrote:

> >Jordan, are you building on an ODS-5 disk?  I haven't tried this iwth PERL
> >5.8.0, but I've found that MMS uses some jive directory handling of its own
> >which makes file extensions case sensitive; don't know if MMK does as well.
> >
> >(My solution was $ RENAME *.c *.C)

and wrote:

> Unless you are running on 7.3-1, the first OS release where case
> sensitivity (over and above case preservation) is possible with
> filenames, I can't think of how this rename would help.  On 7.3 and
> earlier, even on ODS-5 with parse style extended, I don't think the
> compiler will refuse to compile foo.c because it doesn't look like
> foo.C.  Unless the processing of dependency rules is done in a case
> sensitive fashion.  Perhaps MMS added ODS-5 support half-heartedly?
> I haven't kept up with MMS releases and don't know if 3.3-4 (what I
> have) is the latest.  I do remember having built Perl 5.6.1 under
> OVMS Alpha v7.2-1 on an ODS-5 disk with no problems, though that
> would have been with MMK.

7.2-1 and 7.2-2 with 

%MMS-I-IDENT, MMS V3.4-3 � Compaq Computer Corporation 2000. � Electronic Data
Systems Limited 1995, 2000

My actual experience was with building ANALOG and WEBALIZER from Rick Dyson's 
website.  His ZIP files are built from ODS-2 disks; ZIP restored everything on
ODS-5 with lowercase names; MMS's dependency rules required a .C to build a
.OBJ, and it failed to recognize them.

I presume MMS is doing a CRTL readdir and direct name comparison rather than
the equivalent of an F$SEARCH.  When I did RENAME *.c *.C it fixed the
problem.  I didn't know whether I was more pleased or more disgusted.

-- Alan

===============================================================================
 Alan Winston --- [EMAIL PROTECTED]
 Disclaimer: I speak only for myself, not SLAC or SSRL   Phone:  650/926-3056
 Paper mail to: SSRL -- SLAC BIN 99, 2575 Sand Hill Rd, Menlo Park CA   94025
===============================================================================


Reply via email to