Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ICS.UCI.EDU!rfg
From: rfg@ICS.UCI.EDU
Newsgroups: gnu.g++
Subject: Re: Please describe how to use g++/gdb with COFF
Message-ID: <20941.625010978@ics.uci.edu>
Date: 21 Oct 89 22:09:38 GMT
References: <8910212151.AA26599@lurch.Stanford.EDU>
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 33


MDT writes:

         The "GNU Linker" Approach
         -------------------------
         A very different means of getting g++ up on COFF systems has been implemented
         primarily by Dirk Grunwald (grunwald@cs.colorado.edu).  I appologize if there
         were other people (in particular, MDT) who also worked on this, and who I
         have failed to give proper credit to.  In any case, the "GNU Linker"
         approach is prefered by Michael Tiemann and by the FSF because it uses
         fewer non-free software tools.  This approach relies on a program call
	  ed

     Another reason I prefer this approach is because linking need only be
     performed once.  Using other approaches require the link to be
     performed at least twice: once to figure out what is needed, and once
     to then link in code which performs the initialization.

Which "other approaches" are you refering to?  The "AT&T Linker" approach
I described only does *one* link step.  Are there yet more approaches that
I should have mentioned also?

     But I suppose
     if you are afflicted with COFF (or its related diseases), the time
     spent linking is among the least of your overall computer problems.

I cannot (and do not) disagree that COFF is a "disease".  I do prefer
a less drastic "cure" however. :-)

P.S.  Can you comment on the shared library problem?  Is there really a
problem there, or was that just a rumor?

// rfg