LYNX-DEV problems compiling lynx 2-7 for VMS6.1 & Multinet 4.0

[Robin Tuttle, Systems Management & Operations Group]

Lynx Folks:

I have been trying, quite unsuccessfully, to compile Lynx 2-7 on a VAX 6000-430
running VMS 6.1 and Multinet 4.0.  I get errors when using the BUILD command
procedure, and also while using MMK.  I've tried compiling with VAX-C and
DEC-C.  I get the same errors while trying to build Lynx on a VAXstation 3100
and a MicroVAX 3900, too.  Simply put, I don't  know enough about the C
language to get very far in debugging the problem.  Any  help is appreciated. 
I've attached the various error message dumps that I've received.  Many
thanks for any help!  

Robin Tuttle
University of New Hampshire

===========================================================================

Errors received when running BUILD.COM:


$ cc [-.Implementation]HTFTP.c
            new_socket = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP);
        ........................^
%CC-E-UNDECLARED, In this statement, AF_INET is not declared.
                At line number 984 in
DISK$SCRATCH:[R_TUTTLE.LYNX2-7.WWW.LIBRARY
.IMPLEMENTATION]HTFTP.C;1.

            new_socket = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP);
        .................................^
%CC-E-UNDECLARED, In this statement, SOCK_STREAM is not declared.
                At line number 984 in
DISK$SCRATCH:[R_TUTTLE.LYNX2-7.WWW.LIBRARY
.IMPLEMENTATION]HTFTP.C;1.

        } /* open_file_read */
%VCG-I-NOBJECT, No object file produced.
                At line number 3255 in
DISK$SCRATCH:[R_TUTTLE.LYNX2-7.WWW.LIBRAR
Y.IMPLEMENTATION]HTFTP.C;1.

%VCG-I-SUMMARY, Completed with 2 error(s), 0 warning(s), and
                1 informational messages.
                At line number 3255 in
DISK$SCRATCH:[R_TUTTLE.LYNX2-7.WWW.LIBRAR
Y.IMPLEMENTATION]HTFTP.C;1.

$ CLEANUP:
$    v1 = f$verify(v)
$ set default [-.-.-]
$!
$!      Compile the Lynx [.SRC] modules
$!


===========================================================================

Errors received when running MMK:

LINK /Executable = Lynx.exe DefaultStyle.obj, GridText.obj, HTAlert.obj,
HTFWrit
er.obj,         HTInit.obj, HTML.obj, LYBookmark.obj, LYCgi.obj,
LYCharSets.obj,
        LYCharUtils.obj, LYClean.obj, LYCookie.obj, LYCurses.obj,      
LYDownlo
ad.obj, LYEdit.obj, LYEditmap.obj, LYexit.obj, LYForms.obj,     LYGetFile.obj,
L
YHistory.obj, LYJump.obj, LYKeymap.obj, LYLeaks.obj,    LYList.obj, LYMail.obj, 
LYMain.obj, LYMainLoop.obj, LYMap.obj,  LYNews.obj, LYOptions.obj, LYPrint.obj, 
LYrcFile.obj, LYReadCFG.obj,    LYSearch.obj, LYShowInfo.obj, LYStrings.obj,
LYT
raversal.obj,   LYUpload.obj, LYUtils.obj,
[-.WWW.Library.Implementation]WWWLib_
MULTINET.olb/lib, sys$disk:[]MULTINET.opt/opt, sys$disk:[]VAXC.opt/opt
%LINK-W-NUDFSYMS, 1 undefined symbol:
%LINK-I-UDFSYM,         __ASSERT 
%LINK-W-USEUNDEF, undefined symbol __ASSERT referenced
        in psect $CODE offset %X00000A4F
        in module GRIDTEXT file
DISK$SCRATCH:[R_TUTTLE.LYNX2-7.SRC]GRIDTEXT.OBJ;
1
%LINK-W-USEUNDEF, undefined symbol __ASSERT referenced
        in psect $CODE offset %X00000B07
        in module GRIDTEXT file
DISK$SCRATCH:[R_TUTTLE.LYNX2-7.SRC]GRIDTEXT.OBJ;
1
%MMK-F-ERRUPD, error status %X10648268 occurred when updating target LYNX.EXE
%MMK-F-ERRUPD, error status %X1C14803C occurred when updating target EXE
unh

===========================================================================

Errors received when running MMK and setting NDEBUG to 1 in GRIDTEXT.C, after
successful/no errors compilation of Lynx:

%SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=00000004,
PC
=00058CEE, PSL=03C00004
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

LYCURSES        setup                           15903      0000018A  00058CEE
LYMAIN          main                            21579      0000104D  00061E51

A Fatal error has occured in Lynx Ver. 2.7

Please notify your system administrator to confirm a bug, and if
confirmed, to notify the lynx-dev list.  Bug reports should have concise
descriptions of the command and/or URL which causes the problem, the
operating system name with version number, the TCPIP implementation, the
TRACEBACK if it can be captured, and any other relevant information.

Press
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;