problem bootstrapping egcs-971105

Joseph H. Buehler jbuehler@hekimian.com
Fri Nov 14 08:49:00 GMT 1997


I am trying to install egcs-971105 as both a native compiler and a
cross-compiler on a number of different platforms and am having a
couple problems.

I am not using gcc as my bootstrap compiler, I am using the native cc
compiler.

I am installing by doing something similar to this in the top-level
egcs snapshot directory:

  configure ...
  make ...
  make ... install

The default appears to attempt a build of the FORTRAN compiler.  Well,
it tries, anyway, my recollection is that the compile issued an error
message saying that the FORTRAN compiler must be compiled with gcc.
How can I do that before it is installed???

OK, so I turned off FORTRAN by setting LANGUAGES="c c++".  This works
pretty well, until the install fails with the following error while
trying to make some of the .info files:

cc: "f/ansify.c", line 65: error 1000: Unexpected symbol: "a".
cc: "\n", line 28: error 1000: Unexpected symbol: "c".
cc: "\n", line 18: error 1000: Unexpected symbol: "c".
cc: "\n", line 1: error 1000: Unexpected symbol: ";".
cc: "\n", line 10: error 1000: Unexpected symbol: "}".
cc: "\n", line 15: error 1000: Unexpected symbol: "for".
cc: error 2017: Cannot recover from earlier errors, terminating.

Apparently the ansify.c file is assuming that an ANSI compiler is
being used, and I am not using one?  Line 65 in the file in question
expands into this:

  do if (!(argc == 2)) { fprintf ((&__iob[2]), "%s:%lu: " #argc == 2 "\n", argv[1], lineno); die (); } while(0);

I don't think the files under f/ should be used at all when I do not
compile FORTRAN.  It seems like configure needs to be fixed to not use
*any* of the FORTRAN stuff if gcc is not the compiler.

I have not tried blowing away the f/ directory before compiling, I
guess I can try that and see if the gcc configure script is smart
enough to autoconfigure for whatever is left.

Joe Buehler



More information about the Gcc-bugs mailing list