Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!mit-eddie!bu.edu!rpi!julius.cs.uiuc.edu!apple!agate!linus!linus!pop
From: pop@linus.mitre.org (Paul Perry)
Newsgroups: comp.sys.isis
Subject: problem with isisv2.1 on VAX and a question.
Message-ID: <125054@linus.mitre.org>
Date: 1 Nov 90 03:23:34 GMT
Reply-To: pop@linus.mitre.org (Paul Perry)
Distribution: usa
Organization: The MITRE Corporation, Bedford MA
Lines: 36


A problem, a fix, and a question.

When building isisv2.1 for a VAX3100 Ultrix-32 V3.0 (Rev 64) I ran
into this error:

cd util; make MCHTYPE=VAX MCHDEPCFLAGS="-DBYPASS" OPLIBS= CC=cc OPTIM="-O" ; cd
..
cc -DBYPASS -DVAX -I../../include -c -O ../../util/long_haul.c
"../../util/long_haul.c", line 2663: warning: ambiguous assignment: assignment o
p taken
"../../util/long_haul.c", line 2663: warning: old-fashioned initialization: use
=
"../../util/long_haul.c", line 2663: syntax error
"../../util/long_haul.c", line 2663: warning: old-fashioned initialization: use
=
"../../util/long_haul.c", line 2663: warning: illegal combination of pointer and
 integer, op =
*** Error code 1

which is easily fixed by adding a space after the = sign on that line.
ISIS then compiles and work fine.

The question is: if I build one isis on a sun4 with the BYPASS and a
second isis on a VAX3100 withought the BYPASS flag are they going to
communicate well ?  I ask because I noticed that the grid demo didn't
seem to behave as expected when I had this setup.  I realize I am
being vague here.  I have since rebuilt isis with the BYPASS flag on
and all is ok.


-- 
Paul O. Perry                                    MITRE Corporation
Phone: (617) 271-5230                            Burlington Road
ARPA: pop@mitre.org                              Bedford, MA  01730
UUCP:   ...{decvax,philabs,genrad}!linus!pop