🚀 go-pugleaf

I wrote (regarding the possibility of installing g++ without knowing about
the copyleft)
> >This would be difficult; the installation procedure for g++ is quite complex
> >and you have to do a lot of work to make it fly. It's not like typing
"make".
> >Joe Buck
> >jbuck@ohm.berkeley.edu	 {uunet,ucbvax}!ohm.berkeley.edu!jbuck	

Gordon Joly replies: 
> I strongly disagree. For a sun3 with SunOS 4.x, config sun3-os4 and
> typing "make install" (these days ;-), is all you need for G++; libg++
> may be a little more involved. If you are running on a ToasTer with
> ToasTOS 5.88 under VM (tm?) then you may have some work to do.

You've skipped a few steps, Gordon.  Like the fact that you have to build
gcc first, have to have the gcc directory in a certain position with
respect to the g++ directory, etc.  Also, if you've used the gcc option
to build in a different directory (as I did) the installation procedure
won't work.

There are quite a few people who ftp'd g++ and only then found out they'd
need to get gcc as well, as well as libg++.  It takes a bit of time.
Once you've done it once it gets a lot simpler.

And even if all I had to do was say "config sun3-os4" and "make install",
I'd still need to read the file telling me to do that, which points
indirectly to the copyleft.

Is there anyone out there who managed to install g++ successfully on their
system without ever reading the Gnu copyright? (That is, you never saw
it in your whole life, and managed to install gcc, maybe Gnu Emacs, etc
and STILL didn't know there was a specific set of rules?)