Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!netnews.upenn.edu!dsinc!ub!uhura.cc.rochester.edu!rochester!cornell!rcbc
From: rcbc@cs.cornell.edu (Robert Cooper)
Newsgroups: comp.sys.isis
Subject: Re: problem with isisv2.1 on VAX and a question.
Message-ID: <47850@cornell.UUCP>
Date: 1 Nov 90 15:57:25 GMT
References: <125054@linus.mitre.org>
Sender: nobody@cornell.UUCP
Reply-To: rcbc@cs.cornell.edu (Robert Cooper)
Distribution: usa
Organization: Cornell University Computer Science Department
Lines: 34
In-reply-to: pop@linus.mitre.org (Paul Perry)

In article <125054@linus.mitre.org>, pop@linus (Paul Perry) writes:
>When building isisv2.1 for a VAX3100 Ultrix-32 V3.0 (Rev 64) I ran
>into this error:
>"../../util/long_haul.c", line 2663: warning: old-fashioned initialization: use
>=

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

Thanks, we'd already caught that one, but assumed most compilers
would only give a warning not an error so we didn't post the fix.
Here's the fix:

2663c2663
<   int i, j=*addrlen;
---
>   int i, j = *addrlen;

Since most of us learnt C after they replaced the dangerous i =+ 1 syntax
with the more sensible i += 1, we often forget to leave the requisite 
space.

>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.

You must compile all binaries with the same setting of the BYPASS flag.  We
might put in a run-time sanity check for this, but at some point BYPASS
will be standard and non-BYPASS will be removed as an option anyway.

                           -- Robert Cooper