Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!husc6!panda!genrad!decvax!ucbvax!telesoft.UUCP!bruceb From: bruceb@telesoft.UUCP.UUCP Newsgroups: mod.computers.vax Subject: Re: bigsis Message-ID: <8703260144.AA02282@sdcsvax.UCSD.EDU> Date: Wed, 25-Mar-87 20:44:47 EST Article-I.D.: sdcsvax.8703260144.AA02282 Posted: Wed Mar 25 20:44:47 1987 Date-Received: Sat, 28-Mar-87 05:43:36 EST References: <8703200403.20382@murdu.OZ> Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 105 Approved: info-vax@sri-kl.arpa > Our JPIDEF.H looks probably different from yours, but that can be fixed by > commenting your JPI define`s. But I cant't find PCBDEF.H nor any PCB-symbols > in any library. What am I missing? I don't understand why I have not yet seen the original posting in this news- group, however I understand that a few people have had problems getting BIGSIS.C to compile. My fault. Here is my 'standard' solution; sent to all who have contacted me in person... BTW, if anyone who is NOT on BITNET has seen the original posting, I'd like to hear from you. I am going to find out whoose mailer is loosing things. I'm getting pretty pissed that I can't seem to see anything I post to this newsgroup. Comments, etc., to me. Thanks. bruce bergman ------------------------------- how to fix BIGSIS.C ------------------------ Thanks for your response about BIGSIS.C not compiling correctly. You were not the only one who informed me that BIGSIS.C would not compile correctly with DEC C v2.[>0], so to make things simple, I have created this document. It will be sent to everyone who expresses the same problem, so please excuse anything that might seem 'simple' or 'obvious.' Meanwhile, here is the procedure for making sure it will compile on your system. First, I'll tell you why it *didn't* work. The 'globalvalue' statements in the code itself were to take care of the fact that DEC C v2.0 didn't have complete .h files in the distribution. For everyone who is using something more recent than v2.0, the correct .h files were provided by DEC, so we can simply remove those lines. So, to remedy situation #1, comment out all the 'globalvalue' statements in the original source. If you aren't familiar with C, use the /* and */ statements to surround the offending lines. E.g, OLD_49: globalvalue JPI$_CLINAME; NEW_49: /* globalvalue JPI$_CLINAME; OLD_56: globalvalue JPI$_MAXDETACH; NEW_56: globalvalue JPI$_MAXDETACH; */ Now, the second problem - not finding and - was strictly inattention on my part. I forgot that I created special .h files to solve some problems. Basically, these have to be created because the source code references some VMS internal values which aren't covered by the standard .h files included with DEC C (another bug in my opinion). In this case, we just want to *add* some statements to the .h files and change two lines. So, to remedy situation #2, first SET DEFAULT into the directory where you now have BIGSIS.C. Once there, you need to create two files and modify the source once more. The two files you should create can be made by doing the following (replace the with the actual keystroke...): $ CREATE PCBDEF.H globalvalue PCB$V_BATCH; globalvalue PCB$V_NETWRK; $ CREATE STATEDEF.H globalvalue SCH$C_CEF; globalvalue SCH$C_COM; globalvalue SCH$C_COMO; globalvalue SCH$C_CUR; globalvalue SCH$C_COLPG; globalvalue SCH$C_FPG; globalvalue SCH$C_HIB; globalvalue SCH$C_HIBO; globalvalue SCH$C_LEF; globalvalue SCH$C_LEFO; globalvalue SCH$C_MWAIT; globalvalue SCH$C_PFW; globalvalue SCH$C_SUSP; globalvalue SCH$C_SUSPO; Once these have been created, edit BIGSIS.C and change the angle braces around pcbdef.h and statedef.h to be double quote marks. Using quote marks tells the compiler to look for the files in the current directory instead of SYS$LIBRARY: (which is where we have just created the necessary files). E.g., OLD_59: #include NEW_59: #include "pcbdef.h" OLD_60: #include NEW_60: #include "statedef.h" Now, you should be all set to compile again. If you compile and still have errors, please let me know. It could be something else I haven't seen yet, however the procedure I outlined to you above has been tested on another site and worked properly. In any case, sorry about the mess-up. If I can help out any further in making it work, please contact me. Oh yes, comments and suggestions are always welcome... Thanks bruce -------------------- end of how to fix BIGSIS.C ----------------------