On Fri, 7 Jul 2000, Craig A. Berry wrote:

> Scott,
> 
> The best place to look for tips on building 5.6.0 is
> 
> <http://www.crinoid.com/perl560.htmlx>
> 
> where you will find a number of patches.  I put together one very 
> large patch including those and more; you can get it at:
> 
> <http://www.xray.mpe.mpg.de/mailing-lists/vmsperl/2000-05/msg00190.html >
> 
> There have been a number of test failures fixed, although I don't 
> recall seeing the ones you mention.  You can search the archives of 

Craig,

I am not sure which of those patches made it into Jarkko's cfgperl,
but trying one of the latter ones:

   http:[EMAIL PROTECTED]

there is a difference between the [.vms]subconfigure.com in that
kit and the one in 5.6.0 from CPAN (configure.com is unchanged).  
Oddly there is a spot with two "=" signs in a symbol assignment and there
is one or two DCL errors/missing symbols in the cfgperl@6290
subconfigure.com.

The big reason I mention the new cfgperl@6290 kit is that with or
without some tweaking to configure.com and [.vms]subconfigure.com
I obtain this unknown symbol during the build of Socket (just after the
build of dl_vms):

MCR Sys$Disk:[]miniperl.exe "-I[.lib]" "-I[.ext.re]" [.lib.extutils]xsubpp
-noprototypes [.EXT.SOCKET]SOCKET.XS >[.EXT.SOCKET]SOCKET.C
CC/DECC /Include=[]/Standard=Relaxed_ANSI/Prefix=All/Obj=.obj/NoList
/Object=[.EXT.SOCKET]SOCKET.OBJ [.EXT.SOCKET]SOCKET.C
MCR Sys$Disk:[]miniperl.exe "-I[.lib]" [.vms]gen_shrfls.pl -f gen_shrfls.opt
Link /NoTrace/NoMap/Share=PERLSHR.EXE [.ext.dynaloader]dl_vms.obj,
[.ext.socket]socket.obj, []perlshr_bld.opt/Option, perlshr_attr.opt/Option
%LINK-W-NUDFSYMS, 1 undefined symbol:
%LINK-I-UDFSYM,         PERL_LOCK
%LINK-W-USEUNDEFSYMV, undefined symbol PERL_LOCK referenced
        in symbol vector option
%MMS-F-ABORT, For target PERLSHR.EXE, CLI returned abort status:%X10648268.


I've not had time to dig for PERL_LOCK (I was hoping to concentrate on
DCL hacking :-) but I thought folks here might like to know what may
be in store :-(

Peter Prymmer





Reply via email to