Nicholas Clark wrote:
On Sat, Jul 23, 2005 at 03:36:39PM -0400, John E. Malmberg wrote:
How do I reproduce this?
I pulled down perl-5.9.2 and started a build and it fails with:
CC/DECC/NOANSI_ALIAS
/Include=[]/Standard=Relaxed_ANSI/Prefix=All/Obj=.obj/List
#$d_sitecustomize USE_SITECUSTOMIZE /**/
.^
%CC-W-BADDIRECTIVE, "$d_sitecustomize" is an invalid preprocessor
directive, an
at line number 3462 in file PERL_BUILD_ROOT:[000000]config.h;1
%MMK-F-ERRUPD, error status %X10B91260 occurred when updating target
MINIPERLMA
23-JUL-2005 15:28:53
The perl 5.9.2 release is now somewhat out of date. That bug has been fixed.
And new ones introduced instead :-(
The best way to get the current source is with rsync. The master source
repository is in perforce, and there isn't anonymous access to that.
We don't tend to make snapshots, I think partly because everyone actively
developing is very happy with rsync, and partly because snapshots seem to
generate near zero feedback, suggesting the time is better spent elsewhere.
(I suspect that the widespread use of rsync helps explain the lack of
interest in specific snapshots. In effect every commit gets treated like a
snapshot)
There are a few paragraphs on what can be got with rsync in perlhack.pod:
http://search.cpan.org/~rgarcia/perl-5.9.2/pod/perlhack.pod#Keeping_in_sync
but most simply if you run
rsync -avz rsync://ftp.linux.activestate.com/perl-current/ perl/
I suppose it would be simple if I had a stable rsync to run. However
rsync source as supplied depends on one of those fork() things to work.
Well I will try my experimental prototype threaded version rsync. If I
run it enough times, it usually will get the stuff. I also may have to
delete some corrupted files.
Is the stuff in porting/.*.* important? It seems I have a bug in
mkstemp() to work around, nothing in that directory with a leading "."
transfered.
Aside from that, the first pass got me to:
xsutils.c
%SYSTEM-F-STKOVF, stack overflow, PC=FFFFFFFF810AD3C4, PS=0000001B
Subsequent passes hang at Changes5.6.
Maybe I got enough to do a build.
The copy of rsync source that I am using rsync to pull down is now clean
compiling, but I have to implement the POSIX thread synchronization code
before it will be usable.
-John
[EMAIL PROTECTED]
Personal Opinion Only