lynx-dev Compiling LYNX on an NCR 3000 MP-RAS SVR4 platform

[Braman, Rick]

As far as I've been able to tell, NCR is not a tested UNIX platform for
running LYNX. This did not worry me too much, since it seems that
several other common UNIX platforms were tested and well supported. With
that I decided to compile LYNX for my NCR UNIX 3.0 system, after doing
extensive reading of all the docs and files. I chose to auto-configure
LYNX 2-8 via './configure'. This appeared to complete just fine,
creating assumingly good 'makefile' and 'lynx.cfg.h' in which to use for
the compile. I ran into a problem when I tried to actually compile LYNX
via 'make'. I received the following errors, to which I am now at a loss
as to what to do...

No suffix list.
       
        cd WWW/Library/unix && make CC="cc" \
       
                LY_CFLAGS="" \
       
                CPPFLAGS="" \
       
                LYFLAGS=""
       
        cc -c -o ../../Library/unix/HTParse.o -DHAVE_CONFIG_H
-I../../.. -I../
../../src -I../../.. -I../../../src
-I../../../WWW/Library/Implementation/ -D
XMOSAIC_HACK -DACCESS_AUTH
../../../WWW/Library/Implementation/HTParse.c       
NCR High Performance C Compiler R2.0a
       
(c) Copyright 1994-95, AT&T Global Information Solutions
       
(c) Copyright 1987-95, MetaWare Incorporated
       
E "/usr/include/sys/vnode.h",L357/C10(#489):    Unexpected symbol in
expression.
 Line ignored.
       
E (#499):       Invalid construct within #if expression.
       
2 user errors   No warnings
       
*** Error code 8 (bu21)
       
                                                                        
       
make: fatal error.
       
*** Error code 1 (bu21)
       
                                                                        
       
make: fatal error.

...I'm not sure where to start looking to find the source of the errors,
besides the obvious 'vnode.h' file, which I am rather unfamiliar with.
Are the (#489) & (#499) referring to line numbers in this file? Even if
they are, I cannot 'see' what could possibly be causing the errors. Any
and all thoughts on this would be greatly appreciated.

Rick Braman
"Native Californian stranded in a UNIX world without LYNX (but hopefully
not for long!)"