On Dec 22, 2012, at 5:14 PM, Thomas Pfau <tfp...@gmail.com> wrote:

> My build had problems with DynLoader which I was able to get past with 'mmk 
> dynloader.xs', 'mmk dynloader.c', 'mmk all'.

I didn't have that problem.  I don't know if it makes a difference, but I was 
using MMK 4.1 for this.

>   After that I restarted the full build.  It died with the following while 
> building in dist/Cwd:
> 
> Link /NoTrace/NoMap /Shareable=[--.LIB.AUTO.CWD]PL_CWD.EXE 
> Cwd.opt/Option,[--]perlshr_attr.opt/Option
> %LINK-W-SHRWRNERS, compilation warnings 
>         in shareable image file 
> DISK$USERS:[pfau.FREEWARE.perl-5_16_2]PERLSHR.EXE;1
> %MMK-F-ERRUPD, error status %X10648268 occurred when updating target 
> [--.LIB.AUTO.CWD]PL_CWD.EXE
> %MMK-F-ERRUPD, error status %X10648268 occurred when updating target 
> [--.LIB.AUTO.CWD]PL_CWD.EXE
> Unsuccessful make(dist/Cwd): code=1024 at make_ext.pl line 466.
> %NONAME-F-NOMSG, Message number 0C14803C
> %MMK-F-ERRUPD, error status %X0C14803C occurred when updating target DYNEXT

This is almost certainly a symptom of not getting completely cleaned up after 
the compiler warnings you reported earlier.

> 
> I looked further up in the build log and found this:
> 
> Link /NoTrace/NoMap/Share=PERLSHR.EXE DynaLoader.obj, 
> []perlshr_bld.opt/Option, perlshr_attr.opt/Option
> %LINK-W-NOSUCHMOD, module PERL not found
>         in library DISK$USERS:[pfau.FREEWARE.perl-5_16_2]LIBPERL.OLB;1
> %LINK-W-NOSUCHMOD, module GLOBALS not found
>         in library DISK$USERS:[pfau.FREEWARE.perl-5_16_2]LIBPERL.OLB;1
> Link /NoTrace/NoMap/THREADS=(MULTIPLE_KERNEL,UPCALLS)/Exe=PERL.EXE 
> perlmain.obj, perlshr.opt/Option, perlshr_attr.opt/Option ,[]crt$
> %LINK-W-SHRWRNERS, compilation warnings 
>         in shareable image file 
> DISK$USERS:[pfau.FREEWARE.perl-5_16_2]PERLSHR.EXE;1
> 
> Any ideas?

Something went wrong compiling globals.c and/or perl.c.  If you have compiler 
warnings or failures that we haven't addressed yet, that would be the place to 
start.  If there aren't any that we haven't dealt with, then you haven't been 
getting the results of the previous compiles cleaned up adequately.  

> BTW, is threading supported on VMS?

It is, but you don't get it unless you configure with -"Dusethreads".  My link 
looked like:

$ sea  sys$login:build_5_16_2.log "exe=perl"
Link /NoTrace/NoMap/Exe=PERL.EXE perlmain.obj, perlshr.opt/Option, 
perlshr_attr.opt/Option ,[]crtl.opt/Options


________________________________________
Craig A. Berry
mailto:craigbe...@mac.com

"... getting out of a sonnet is much more
 difficult than getting in."
                 Brad Leithauser

Reply via email to