Very Computer

I'm new to Solaris sysadmining.  My first task is to install gcc (v2.5.6) and  
Gopher on our new Sparc 1000 runninng Solaris 2.x.  Gcc seemed to install  
correctly, but when I make Gopher (v2.014) this is what happens:

[dudley:blake015] > make
Making Objects
(cd object; make )
gcc -g  -DUSG -DNO_WAITPID -DUSE_FLOCK -DDEBUGGING -I.  -c STRstring.c
gcc: installation problem, cannot exec cpp: No such file or directory
*** Error code 1
make: Fatal error: Command failed for target `STRstring.o'
Current working directory /opt/local/gopher/gopher2.014/object
*** Error code 1
make: Fatal error: Command failed for target `object/libgopher.a'

cpp _does_ exist, in /usr/ccs/lib/cpp (as it should according to the cpp man  
page); this is the cpp that came with Solaris, not the one from the gcc  
release.

Can someone tell me what's wrong?  Do I need to replace /usr/ccs/lib/cpp with  
the cpp from the gcc release?

Thanks--

Denise
--
Denise Blakeley              | PROGRAM, tr. v., An activity similar
Duke Med Center Info Systems | to banging one's head against a wall,
Durham, NC                   | but with fewer opportunities for
(919) 286-6468 W             | reward.

gcc is just a little shell script frontend that runs the appropriate
parts of the compiler.  Each of these parts: cpp, cc1, etc.  are
stored in a gcc directory.  You can find the name of the gcc directory
by running:

        gcc -v

Mine looks like:

31> gcc -v
Reading specs from /usr/local/gcc/lib/gcc-lib/sparc-sun-solaris2.3/2.5.8/specs
gcc version 2.5.8

By stripping off the "specs" file from the path, you get the name
of the gcc directory.  My best guess is that the permissions on
one of your directories in that path.

Quote:>cpp _does_ exist, in /usr/ccs/lib/cpp (as it should according to the cpp man  
>page); this is the cpp that came with Solaris, not the one from the gcc  
>release.

It doesn't use that one.

Quote:>Can someone tell me what's wrong?  Do I need to replace /usr/ccs/lib/cpp with  
>the cpp from the gcc release?

Leave your original cpp alone.  gcc doesn't need to mess with it.
--
                                         Michael A. Griffith
                                         University of California, Riverside

You;ve installed a binary version of gcc in a different location
than the one it expected to be installed in.

I'd recommend reinstalling from source, if you don't want to do that,
look into the GCC_EXEC_PREFIX environment variable.

I think it expects to be installed under /opt/gnu, so
intsalling one symlink there should work too.

Casper