Xref: utzoo gnu.g++.help:364 comp.lang.c++:11235
Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!tut.cis.ohio-state.edu!V6550C.NRL.NAVY.MIL!youngdale
From: youngdale@V6550C.NRL.NAVY.MIL (Eric Youngdale)
Newsgroups: gnu.g++.help,comp.lang.c++
Subject: Re: G++ not ready....
Message-ID: <00943161.22f44680.3227@v6550c.nrl.navy.mil>
Date: 22 Jan 91 16:03:01 GMT
Sender: daemon@tut.cis.ohio-state.edu
Followup-To: gnu.g++.help
Organization: Gatewayed from the GNU Project mailing list help-g++@prep.ai.mit.edu
Lines: 19


	I would like to point out that it is possible to build a compiler
that is very buggy by not following the proper procedures.  The first time that
I built it, I only compiled the modules in the g++ distribution, and linked
this with the object files that were generated when I built the comparable
version of gcc.  The resulting compiler would work - some times - and it had
all sorts of strange problems from occasional compiler crashes to spurious
results.  Interestingly enough, a few modules would compile correctly, as
evidenced by the fact that the output was correct.

	Once I figured that I had done something wrong, and rebuilt the
compiler properly, and I have had very little difficulty since.

------------------------------------------------------------------
Eric Youngdale          INTERNET:  YOUNGDALE@V6550C.NRL.NAVY.MIL
Naval Research Lab     	    SPAN:  11.13 (or 11277::)
Washington, DC	       FLAME-NET:  NLA0:
	Disclaimer:  The opinions expressed herein are my own and not
necessarily those of my employer.