On Oct 24, 2008, at 5:10 AM, Vorländer, Martin wrote:
Hi!
I'm trying to build Perl 5.10.0 on my Integrity server. I downloaded
http://www.cpan.org/src/perl-5.10.0.tar.gz today, used GUNZIP and
VMSTAR to
unpack it,
I repacked it to ZIP under Windows before transfering it to Integrity.
and then ran CONFIGURE.COM taking all the default answers (except
for my email address).
Here's what happens when I try to build it:
$ mms
Copy/NoConfirm/Log [.VMS]SOCKADAPT.H []
%COPY-S-COPIED, D1:[perl.PERL-5_10_0.vms]sockadapt.h;1
copied to D1:[PERL.PERL-5_10_0]sockadapt.h;1 (10 blocks)
...
CC/DECC/NOANSI_ALIAS
/Include=[]/Standard=Relaxed_ANSI/Prefix=All/Obj=.obj/NoList/f
loat=ieee/ieee=denorm/Define=(PERL_CORE,_USE_STD_STAT=1) MRO.C
%MMS-F-GWKNOPRN, There are no known sources for the
current target GENERATE_UUDMAP.OBJ
This one I fixed here:
http://public.activestate.com/cgi-bin/perlbrowse/p/33589
It should be in 5.10.1.
@make_ext "Sys$Disk:[]miniperl.exe" "MMS"
Making attrs (dynamic)
Writing Descrip.MMS for attrs
cp attrs.pm [--.lib]attrs.pm
MCR [--]miniperl.exe "-I[--.lib]" "-I[--.lib]" -e "use
ExtUtils::Mksymlists;" -e "Mksymlists('NAME' => 'attrs',
'DL_FUNCS' => { }
, 'DL_VARS' => [], 'FUNCLIST' => [])"
MCR [--]miniperl.exe -e "print ""[--.lib.auto.attrs]attrs.olb/
Include=attrs\n[--.lib.auto.attrs]attrs.olb/Library\n"";" >>ATTRS.OPT
MCR [--]miniperl.exe -e "print qq{[--]PerlShr.exe/Share\n}"
>>ATTRS.OPT
MCR SYS$SYSDEVICE:[TEMP.PERL-5_10_0]miniperl.exe "-I[--.lib]" "-
I[--.lib]" "-MExtUtils::Command" -e cp ATTRS.OPT [--.LIB.AUTO.ATTRS]
ATTRS.OPT
%MMS-F-GWKNOACTS, Actions to update ATTRS.C are unknown.
%MMS-F-ABORT, For target DYNEXT, CLI returned abort status:
%X10EE805C.
A similar rule fails there:
attrs.c : $(XSUBPPDEPS)
instead of
attrs.c : attrs.xs $(XSUBPPDEPS)
I have MMS 3.8-2 on Alpha and seldom if ever use it because of this
problem. It appears to simply ignore the rule that looks like:
# --- MakeMaker xs_c section:
.xs.c :
$(XSUBPPRUN) $(XSPROTOARG) $(XSUBPPARGS) $(MMS
$TARGET_NAME).xs >$(MMS$TARGET)
I don't know if case sensitivity is a problem here, such that if you
defined .xs.C, .XS.C, and .XS.c as well as the above it might pick up
one of them. SET PROCESS/CASE_LOOKUP=SENSITIVE might do something for
this but would probably break a lot of other things.
I suppose we ought to diagnose what exactly MMS is doing here and fix
MakeMaker to work around it, but over the years they've always thought
of new ways to break MMS faster than we could come up with
workarounds. I use MMK almost exclusively, which avoids both of the
problems mentioned and is still available here:
http://www.madgoat.com/
http://www.kednos.com/kednos/Resources/MX
__________
Craig A. Berry
mailto:[EMAIL PROTECTED]
"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
