lofaso@TITAN.TSD.ARLUT.UTEXAS.EDU (Bernie Lofaso) (05/11/89)
I am currently trying to install g++ in a sun3/280 with SunOS 4.0.1. After having much trouble installing the g++ compiler, I got the makefile execution to finish. When trying to make the libg++.a, the first invokation of g++ on the file builtin.cc bombed with the assembler giving the error "Invalid operation" twice. This may not be a problem with libg++, but rather some problem with the way that I made the g++ compiler. I am using the following GNU versions: gcc = 1.34 g++ = 1.34.2 libg++ = 1.34.0 Initially I installed gcc-1.35, but then I was told that I must use 1.34 to be compatible with the 1.34.2 release of g++. I did not reinstall gcc when I obtained the 1.34 version. I am using the 1.35 compiler to compile, but my file links are set up to that I am linked to the 1.34 source code. Do you know if this is o.k.? Should I have run any set-up files from the 1.34 distribution first. I followed the g++ installation instructions but the file cplus-lex.c bombed with an undeclared type (yyltype). I found a definition for this type in another file, added it to cplus-lex.c and the compilation of g++ succeeded. If you have any ideas, any help would be appreciated. Since my problem may be in the g++ compiler rather than the library, if you can give me the name and address of someone to talk to about the compiler, I would also be grateful. Bernie Lofaso (lofaso@titan.tsd.arlut.utexas.edu)
tiemann@YAHI.STANFORD.EDU (Michael Tiemann) (05/11/89)
See README, which shows how to patch bison to avoid the yyltype problem. Also, see HINTS, to find out how to compile cplus-decl.c (i.e., define FASCIST_ASSEMBLER). Michael