[gnu.gcc.bug] Problems building GCC 1.36 on Ultrix 3.0

rainwatr@ucunix.san.uc.edu (Don Rainwater) (01/11/90)

I've been trying to build GCC 1.36 on a VAX 8650 running Ultrix 3.0.
According to the installation instructions, all I need to do is type
'config.gcc vax', followed by 'make' to generate the stage1 compiler.
Everything goes seems to go okay up to this point, with the exception of
some warnings when dbxout.c is compiled (warning: enumeration type
clash, operator =).

I then type 'make stage1' to move the stage1 compiler to the stage1
directory, and this goes okay as well.  The problem occurs in the next
step - here's how it looks: (the line breaks on the first stage1/gcc
command are mine)

--
make CC=stage1/gcc CFLAGS="-g -O -Bstage1/"
stage1/gcc -g -O -Bstage1/ -I. -I. -I./config
  -DSTANDARD_STARTFILE_PREFIX=\"/usr/local/lib/\" 
  -DSTANDARD_EXEC_PREFIX=\"/usr/local/lib/gcc-\"
  -c  `echo ./gcc.c | sed 's,^\./,,'`
stage1/gcc -c -g -O -Bstage1/  -I. -I. -I./config version.c
stage1/gcc -c -g -O -Bstage1/  -I. -I. -I./config obstack.c
stage1/gcc -g -O -Bstage1/  -o gccnew gcc.o version.o obstack.o
mv gccnew gcc
mv: cannot access gccnew
*** Error code 1
 
Stop.
--

I tried to do the last step manually to see if it would create the
gccnew executable.  It doesn't.  I also tried to use the stage1 compiler
to compiler the standard 'hello world' program.  There appear to be no
errors, but there is no exec file produced.

Does anyone have any ideas on this?  Is there something I'm missing or
doing wrong?  Thanks for any info

--

grr@cbmvax.commodore.com (George Robbins) (01/11/90)

In article <88@ucunix.SAN.UC.EDU> rainwatr@ucunix.san.uc.edu (Don Rainwater) writes:
> I've been trying to build GCC 1.36 on a VAX 8650 running Ultrix 3.0.
> According to the installation instructions, all I need to do is type
> 'config.gcc vax', followed by 'make' to generate the stage1 compiler.

This isn't a very helpful answer, but I've made gcc a number of times
without any particular problems.  I'd start over, making sure you dot
the i's, etc.  Also, make sure defineitions for which ld, cpp and so on
that gcc is using are rational and there's not some confusion about your
path.

-- 
George Robbins - now working for,	uucp: {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)