🚀 go-pugleaf

In article <PCG.90Jul5162042@odin.cs.aber.ac.uk> pcg@cs.aber.ac.uk (Piercarlo Grandi) writes:
<In article <578@vidiot.UUCP> brown@vidiot.UUCP (Vidiot) writes:
<
<   Welcome the the GNU g++ installation fustration club.
<
<It has never taken me more than a couple of hours to get G++ running;
<all I have done has been to compile it with 'cc -O -W2,-y0', link it
<with the '-lPW' switch, and use COFF support. I have also found the
<time to slightly improve (some releases back) support for shared
<libraries, linking with holes, etc... Very few problems even there. My
<next project, when I reinstall it (I am waiting 2.0), is to get rid of
<the collect pass and put in the COFF .init .fini section support as
<already done by others (Grunwald?). Even there I expect very little
<sweat.
<
<What's all this fuss about G++ and SysV386, I always ask myself.

So, what OS and machine are you using?

<   I too want to get groff running, but can't because of the same ld.c
<   problems.  I had others as well, that wasted about 6 hours of time.
<   I have written to the author and am awaiting an answer.
<
<   I would make installation much easier if the GNU team would use the
<   configure program package, like rn and elm. [ ... ] I believe that
<   the GNU team should very seriously consider this installation aid.
<
<They will not, because the GNU team is seriously interested in getting
<the GNU OS off the ground, not supporting other OSes. The rely on the
<public to care for this, as noted above.

If GNU OS for the 386 is like the GNU compiler stuff, I won't touch it
with a ten-foot-pole.  BTW, the configure is not OS, related, but obviously
it looks around the see what OS stuff is there.

I am very gun-shy at the moment.
-- 
      harvard\     att!nicmad\        spool.cs.wisc.edu!astroatc!vidiot!brown
Vidiot  ucbvax!uwvax..........!astroatc!vidiot!brown
      rutgers/  decvax!nicmad/ INET:<@spool.cs.wisc.edu,@astroatc:brown@vidiot>