Hi,
Although we discussed this change and found it should be safe, I now find that
it isn't on VAX/VMS V7.2
So here is one that works on the VAX and still makes Porting/checkcfgvar.pl
see the sig_name_init symbol. (May need some real VMSers' eyes.)
--- configure.com.orig Mon May 29 22:32:02 2006
+++ configure.com Mon May 29 22:38:33 2006
@@ -6281,7 +6281,14 @@
$ WC "shortsize='" + shortsize + "'"
$ WC "shrplib='define'"
$ WC "sig_name='" + sig_name + "'"
-$ WC "sig_name_init='" + sig_name_init + "'"
+$ IF (f$length(sig_name_init) .GES. 1024)
+$ THEN
+$ tmp = "sig_name_init='" + sig_name_init + "'"
+$ WC/symbol tmp
+$ DELETE/SYMBOL tmp
+$ ELSE
+$ WC "sig_name_init='" + sig_name_init + "'"
+$ ENDIF
$ WC "sig_num='" + sig_num + "'"
$ WC "sig_num_init='" + sig_num_init + "'"
$ WC "sig_count='" + sig_count + "'"
After applying this patch I get this error with MMK:
CC/DECC /Include=[]/Standard=Relaxed_ANSI/Prefix=All/Obj=GLOBALS.obj/NoList/
FLOAT=G_FLOAT/Define=PERL_CORE GLOBALS.C
*/
%VCG-W-BADPSECT, The program section(psect) specified by this statement has
conflicting 'nowrite' attributes with another definition
of the same program section.
At line number 42 in DISK$USER_2:
[TIMMERMAN.KLAD.PERL-CURRENT]GLOBALS.C;1.
%VCG-I-SUMMARY, Completed with 0 error(s), 1 warning(s), and
0 informational messages.
At line number 42 in DISK$USER_2:
[TIMMERMAN.KLAD.PERL-CURRENT]GLOBALS.C;1.
%MMK-F-ERRUPD, error status %X10B90000 occurred when updating target
GLOBALS.OBJ
HTH +
Good luck,
Abe
--
[about random hash-seed]
On Windows, I guess we just seed using the user's credit card number as
extracted from the registry. Product activation collects that, doesn't it?
-- Nicholas Clark on p5p @ 2003-07-07
