🚀 go-pugleaf

From: zhenyu@pappus.uucp (Zhenyu Li)
Path: pappus!zhenyu

In article <1991Jun25.153532@deadlock.hrl.hac.com> williams@deadlock.hrl.hac.com (Ron Williamson (213)317-5687) writes:
>In testing our installation of Saber C++ 1.02 on the tut2.code.shar  tutorial
>files for the minidraw application I ran into the problem referenced
>below.  Has  anyone else run into this bus error problem with the
>minidraw or other applications ?
>
>making all for sparc in ./sparc
>compiling ../minidraw.c
>rm -f minidraw.o minidraw..c
>/usr/local/Saber/bin/CC    -O     -Dcplusplus_2_0 -Div2_6_compatible   
>-I..  -I
>/interviews/include/InterViews/2.6 -I/interviews/include/IV-look/2.6 
>-I/intervi
>ews/include  -I/usr/local/include     -c ../minidraw.c
>CC  ../minidraw.c:
>"../minidraw.h", line 72: internal << AT&T C++ Translator 2.00 5/10/91
>(Saber-C+
>+ 1.0.2 (Release 1.0)) >> error: bus error (or something nasty like
>that)
>1 error
** Error code 1
>make: Fatal error: Command failed for target `minidraw.o'

I came across similar problems when I compiled Interviews 
3.0-beta using Saber C++ 1.0.  I had  bus error on 7 of
the source files under iv/src/bin/ibuild and 2 under iv/src/bin/idraw. 

>If so what is was the solution.

I got around the problem by changing to Sun C++ (I don't know the 
version number, it was installed in 1989 using AT&T cfront 2.0) 
to compile the files that could not be compiled by Saber C++ and 
then linked the object codes. All the object codes  are generated by
same cc compiler, so no problem happened during the linking step.

The problem with Sun C++ (the one I use) was that it could not compile
some of the files under iv/src/lib/graphic and iv/src/lib/Unidraw. 
So I couldn't get the libraries with  Sun C++ while Saber C++ happened
to  have no problem with that.

                                         zhenyu@das.harvard.edu