develooper Front page | perl.perl5.porters | Postings from October 2000

perl@7463 not OK: lex trouble on VMS persists

Thread Next
From:
Peter Prymmer
Date:
October 27, 2000 17:46
Subject:
perl@7463 not OK: lex trouble on VMS persists
Message ID:
Pine.OSF.4.10.10010271745110.394078-100000@aspara.forte.com

In trying to link the dll for the Socket extension I now see:

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
%DCL-I-IGNQUAL, qualifiers appearing before this item were ignored
 \VERSION\

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,         S_SYYLEX
%LINK-W-USEUNDEFSYMV, undefined symbol S_SYYLEX referenced
        in symbol vector option
%MMS-F-ABORT, For target PERLSHR.EXE, CLI returned abort status:
%X10648268.

Was something unusual done with any /s_syylex/i symbols recently?

Peter Prymmer




Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About