🚀 go-pugleaf

After having no problem installing gcc-1.27, I just cannot get over the
hurdle of g++-1.27.

I have compiled and run a few little test programs with gcc-1.27; When
I try to use g++-1.27, it generates object code, but stops in ld with
an error complaining about crt0+.o.

During the g++ make, there is a warning about a double declaration of _eprintf;
I saw some comments about __eprintf vs. _eprintf in this group recently.  Is
that something I need to worry about?

Last night I scrapped the works, and started with a fresh ftp of gcc-1.27
and g++-1.27 from prep.ai.mit.edu, and I got the same result as before.

I would love to hear from someone with g++ running on a vax/Ultrix, or
from anyone else who could shed some light on my problem.

Q:  Why does dist-g++ -> g++-1.25 and not g++-1.27 at prep.ai.mit.edu?
	Should I try gcc/g++1.25 instead?
Q:  The VAX.README patches are not mentioned in the README instructions,
	but I applied them anyway (did it with and without, actually).
Q:  The README instructions are a little confusing about the file structure;
	I have been making it under /usr/users/johns/gnu/[gcc,g++,bison,etc]/,
	will it make a difference if I try it under, say, /usr/local/gnu....?

Well, if I have not already revealed my naivete, I would like to officially
do so now, and invite gentle responses.

I would like to thank Todd Inglett, for all his assistance so far....

Just Sign Me,

"Eager to get G++ running,"

John
-- 
John Sahr,                          School of Elect. Eng.,  Upson Hall   
                                    Cornell University, Ithaca, NY 14853

ARPA: johns@calvin.ee.cornell.edu; UUCP: {rochester,cmcl2}!cornell!calvin!johns