[comp.windows.interviews] installing on SPARCstation running 4.0.3

drich@klaatu.lanl.gov (David O. Rich) (04/20/91)

Are there any know problems trying to install InterViews 3.0 (Beta) on
a SPARCstation running SunOS 4.0.3? In my first attempt (using
Saber-C++) several files did not compile due to "cpp" segmentation
faults or bus errors (weird).  I'm in the process of trying it using
the Sun C++ compiler instead.  Anyone seen this weirdness?

Thanks.
--

David Rich            | Military Systems Analysis Group
Email: dor@lanl.gov   | Mail Stop F602
Phone: (505) 665-0726 | Los Alamos National Laboratory
FAX  : (505) 665-2017 | Los Alamos, NM 87545

nishio@kuis.kyoto-u.ac.jp (Nishio `Cchwitz' Shuichi) (04/23/91)

In article <DRICH.91Apr19154314@klaatu.lanl.gov> drich@klaatu.lanl.gov (David O. Rich) writes:

   Are there any know problems trying to install InterViews 3.0 (Beta) on
   a SPARCstation running SunOS 4.0.3? In my first attempt (using
   Saber-C++) several files did not compile due to "cpp" segmentation
   faults or bus errors (weird).  I'm in the process of trying it using
   the Sun C++ compiler instead.  Anyone seen this weirdness?

From my experience,

1. for cpp's segmentation fault, add +i option to C++ driver(CC) .
2. in 4.0.3, waitpid() is lacking, so you cannot link ibuild. 
  I tried to substitute with wait4(),  but ibuild dies when I try to 
  execute the produced code, so this might have been wrong.

--nishio

interran@lurch.Stanford.EDU (John Interrante) (04/23/91)

In article <DRICH.91Apr19154314@klaatu.lanl.gov> drich@klaatu.lanl.gov
(David O. Rich) writes:
   Are there any know problems trying to install InterViews 3.0 (Beta) on
   a SPARCstation running SunOS 4.0.3? In my first attempt (using
   Saber-C++) several files did not compile due to "cpp" segmentation
   faults or bus errors (weird).

Just two days ago, somebody else posted that if you added +i to
CCDriver in your local.def, Saber C++ would be able to compile
3.0-beta.  Nobody's reported a similar problem with Sun C++, probably
because Sun C++ uses its own cpp.  We haven't encountered this problem
with AT&T C++, but we're running SunOS 4.1 so 4.1's cpp is probably
better than 4.0.3's cpp.
--
John Interrante / interran@lurch.stanford.edu

siegel@cs.columbia.edu (David Siegel) (04/24/91)

>      This is very probably the Sun cpp #include limit.  Sun's version of
> cpp can't handle more than a fixed number of total #include statements.
> The workaround is to use another version of cpp, ie. GNU's version.

Or call Sun and ask for the latest version, which they claim will support
64 nested #includes -- I can't verify the limit of 64, but it did solve a
similar problem for me.

-dms

gjb@cs.brown.edu (Gregory Brail) (04/25/91)

In article <DRICH.91Apr19154314@klaatu.lanl.gov> drich@klaatu.lanl.gov (David O. Rich) writes:
>Are there any know problems trying to install InterViews 3.0 (Beta) on
>a SPARCstation running SunOS 4.0.3? In my first attempt (using
>Saber-C++) several files did not compile due to "cpp" segmentation
>faults or bus errors (weird).  I'm in the process of trying it using
>the Sun C++ compiler instead.  Anyone seen this weirdness?

I had this problem, but the new Sun cpp (which comes with SunOS 4.1.1)
fixed it. The cpp that comes with Sun C++ 2.0 also works properly, as
does gnu cpp and several others.

				-greg


+----------------------------------------------------+
Greg Brail
Internet: gjb@cs.brown.edu  BITNET: gjb@browncs.bitnet
UUCP:	..uunet!brunix!gjb  Home:   (401)273-1172