Front page | perl.vmsperl |
Postings from June 2012
On Wed, May 16, 2012 at 10:36:54AM -0600, Mark Berryman wrote: > Some answers: > > 6: How do I deal with filenames with ^. (etc) in them from DCL? Without > > resorting to bash? Is it really the only option to rename directory names > > to remove the .s? > > I don't follow this question. For the first part: > > Issue the command $ SET PROCESS/PARSE_STYLE=EXTENDED to be able to use filenames with ^ in them. I recommend putting this command in your LOGIN.COM file (let me know if this needs further explaining). > > If the filename in question is a directory reference you must type the filename as is, including the ^ characters, e.g. [.perl-5^.14^.2] > If the filename is a regular file, you can type it in with or without the ^ characters, e.g. file^.c.orig or file.c.orig. > > I don't know what the .s refers to. Can you provide an example? Sorry, wasn't clear. By ".s" I meant "the periods in the filenames" The problem was that I didn't have SET PROCESS/PARSE_STYLE=EXTENDED I do now. I've also found that I can avoid most of the problems in the first place by generating my perl tarball on Linux like this: commit=`git rev-parse --short=12 HEAD`; tar cf perl-$commit.tar --files-from <(sed -e 's/[ ].*//' MANIFEST) --transform 's!^!perl-'$commit'/!' from within a checkout, which gets me a tar with a "clean" name such as perl-247d6b204efe.tar with the internal pathnames prefixed with perl-247d6b204efe, and all the files nicely read-write. It looks like current *BSD tar can do the same trick, but the options have different names. > > > > > This might need more knowledge of the machine than the above -v and -V > > reveal > > > > 7: How do I actually use the libraries of that installed perl 5.8.6? > > The directory tree where perl is installed will be pointed to by the logical name PERL_ROOT. Try $ DIR PERL_ROOT:[LIB] as a starter. > The perl sharable image that one must link to will be pointed to by the logical name PERLSHR. Simply use the name PERLSHR in any link procedure to link to that library. It seems that the system setup wasn't correct. They've fixed it now - the system installed perl 5.8.6 now works. > I bought my system directly from Compaq/HP, with licenses, so I have no problem doing any form of development. If it will help, you are welcome to an account here. Thanks for the offer. I think (for now) it's much easier if I stick to the HP porting system, as it's a known quantity. In particular, it's "known" to John E. Malmberg, which means that he's mostly already worked out how to fix or work around the causes underlying the problems I describe. Nicholas Clark