Michael G Schwern wrote:
On Sun, Jul 24, 2005 at 08:57:52PM -0400, John E. Malmberg wrote:
Might I suggest you check your local copies of Perl into a local version
control system? I usually use RCS for small changes to small groups of files
or I dump the whole thing into darcs for larger changes.
I was not intending on working on bleadperl, or doing any perl
development at home. It is just that this bug report kept showing up on
the vmsperl list, and fixing this type of bug is usually more trivial
than it turned out to be.
So I got sucked in, and was unprepared :-)
I do not have remote access to the work system, so if the code is there,
I do not have access to it until Monday.
I only put in a modified copy here last week in case I got around to
using one of the Perl scripts that potentially need it.
Now that I have a copy of bleadperl pretty much almost linking, I should
be able to keep it running.
I really need to get my copy of rsync fixed though. The quick and dirty
hacked version has some strange bugs.
I think that Craig can verify that I am probably the only one running
rsync on VMS at all.
Craig, if you can still build your snapshot of rsync I posted earlier,
modifying the pthread attributes before the thread creation to have a
stack of about 32K should hide many of the problems.
One of these days I need to get a LINUX system set up here.
-John
[EMAIL PROTECTED]
Personal Opinion Only
