"Craig A. Berry" <[EMAIL PROTECTED]> wrote on 08/25/2004 11:13:57 PM:

<snip! />

> >I tried this [the easy-to-build source kit] yesterday, doing everything
> >under my own username, with all
> >privileges except NETMBX and TMPMBX turned off. The environment is:
> >VMS: 7.1-1H2
> >CC: DEC C V5.6-003
> >TCP/IP: Multinet 4.1 Rev A-X
> >Make: MMK 3.9-6.

> That's all on the older side except for MMK.

I know :-(

> >
> >The build was done from users:[wyanttr.perlbuild584], with "users:" 
being
> >a rooted directory that adds one level to the nest depth.
> >
> >I experienced one test failure in core Perl:
> >lib/Net/hostent......................FAILED at test 5

> See the section entitled, "Multinet issues with Perl on VMS" in
> README.vms in the [.source] directory, or at

> http://www.perldoc.com/perl5.8.4/README.vms.html#Multinet-issues-
> with-Perl-on-VMS

Thank you for the pointer.

> >This was after applying my patch for the "stat" bug in the C RTL.

> Remind me whether this is something you are applying locally or
> something we have incorporated into Perl.  And is this a bug that
> later C RTL's have fixed?

This is one I did myself to compensate for a bug in the C RTL that I'm 
running. The symptom was that the file modification time reported by the 
stat function was off by an hour during Daylight Saving.

You were very helpful back in June of 2002, by pointing me both to the 
knowledge base of whoever owned VMS back then, and to the Perl source 
module I needed to look at. Thanks again.

The scary thing about this patch is after I got it working, someone with a 
.mil domain asked that I publish, because he had the same problem (old C 
RTL and unable to upgrade). I'll be glad to publish again, once I figure 
out how I made the diff file last time.

<snip! />

> >VMS::FindFile failed tests 3 and 4 of t/1
> >This failure goes away if you run the build as SYSTEM (and therefore 
with
> >privileges turned on).

> That's a little bothersome as it should just be doing lib$find_file on
> directories you have access to.  Running the test in verbose mode
> might be warranted if you are planning to use this extension.

I hope to provide more information when I can delve deeper into this. And 
the check is in the mail ...

<snip! />

> >So regardless of the verbiage I have dumped into this message, it 
appears
> >that the source kit is pretty usable.

> Good, glad to hear it.  I've built the kit on a 7.1 system and use it
> regularly.  I did not encounter many of the problems you did, but I
> have C 6.5, which does make a difference.

Unfortunately, I'm stuck where I am. Sigh.

Thanks for the feedback,
Tom Wyant


This communication is for use by the intended recipient and contains 
information that may be privileged, confidential or copyrighted under
applicable law.  If you are not the intended recipient, you are hereby
formally notified that any use, copying or distribution of this e-mail,
in whole or in part, is strictly prohibited.  Please notify the sender
by return e-mail and delete this e-mail from your system.  Unless
explicitly and conspicuously designated as "E-Contract Intended",
this e-mail does not constitute a contract offer, a contract amendment,
or an acceptance of a contract offer.  This e-mail does not constitute
a consent to the use of sender's contact information for direct marketing
purposes or for transfers of data to third parties.

 Francais Deutsch Italiano  Espanol  Portugues  Japanese  Chinese  Korean

            http://www.DuPont.com/corp/email_disclaimer.html


Reply via email to