><[EMAIL PROTECTED]>:
>This mailinglist does not accept postings crossposted to newsgroups -
>Contact [EMAIL PROTECTED] for help
I just checked for new mail and received the above after sending a response
which was again posted to c.o.v and VMS Perl.
My apologies, I was unaware of this restriction. Would it be possible to
permit crossposts to VMS Perl and comp.os.vms? Most VMS people will check
the newsgroup archive first when seeking information.
OTOH, I'll bet if I use the mail2news-<YYYYMMDD>-<newsgroup>@nym.alias.net
address to get my post to comp.os.vms that will defeat the mailing list's
checks. ;-}
Anyway, for those who don't follow comp.os.vms, here is what I posted there
(and will have been rejected by the mailing list)...
On Mon, 17 Mar 2003, Charlie McCutcheon <[EMAIL PROTECTED]>
wrote:
>As other posters noted, there is a new function poll() in the C Run-Time.
>
>From the release notes, which we suggest all customers read:
>
> o The new socket routine poll() is provided with this kit.
<snip>
>All changes on the kit were asked for by active users requiring them
>before a next OpenVMS release.
I don't have a problem with that, my users can still perform basic Perl
stuff. As a Hobbyist system that I give out accounts on people should
expect to see some bleeding edge issues.
On Mon, 17 Mar 2003, Craig A Berry wrote (on the VMS Perl mailing list):
>Perl needs to be made to work with as many C RTL versions as
>possible, so it's looking like we'll need to add a test for poll().
>Thanks, Doc. This is precisely the reason that I wanted more
>widespread testing. The weird thing is that I didn't think we had a
>poll() override, but there must be one in there somewhere that's
>causing the conflict.
I hit the same problem with 5.8.0 following this ECO application. It
probably impacts the 5.6.0 and 5.6.1 build too. I haven't checked them due
to the amount of time a build takes. I'm sorry I can't provide patches
myself, but I'll be happy to work with any provided or grant access to the
system if that would be of use.
Patches is actually something I had a problem with for Perl 5.8.0. I found
two patches via the VMS Perl mailing list archive, but had problems
applying them that led me to believe I was missing other patches.
This leads on to a few questions I've not found a clear answer on...
Where precisely can I obtain patches for Perl and now do I identify those
I should apply (VMS specific, or generally required)?
What is the syntax to use with GNU patch on VMS assuming I have the
following setup on DISK$PERL
[5_8_0] Build directory created from tarball downloaded off
CPAN.
[5_8_0_ROOT] The [000000] directory for PERL_ROOT.
[5_8_0_PATCHES] Where I download patches to.
My thanks to those that have responded so far.
Doc.
--
Time and money, the psychotropics of the business world...
~ VAXman https://vmsbox.cjb.net
