Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!gem.mps.ohio-state.edu!uwm.edu!uwvax!tank!ncar!boulder!grunwald
From: grunwald@foobar.colorado.edu (Dirk Grunwald)
Newsgroups: gnu.g++
Subject: Re: Please describe how to use g++/gdb with COFF
Message-ID: <13295@boulder.Colorado.EDU>
Date: 28 Oct 89 18:26:37 GMT
References: <8910212151.AA26599@lurch.Stanford.EDU>
	<20941.625010978@ics.uci.edu> <13058@boulder.Colorado.EDU>
	<1989Oct27.192234.24792@paris.ics.uci.edu>
Sender: news@boulder.Colorado.EDU
Reply-To: grunwald@foobar.colorado.edu
Distribution: gnu
Organization: University of Colorado at Boulder
Lines: 9
In-reply-to: rfg@ics.uci.edu's message of 28 Oct 89 02:22:34 GMT


The man page for `ld' says something about putting test in a .init
section; however, this doesn't sound like the ifile option. The other
documentation I have on this is relatively moot.

cDoPortability extends to the class of machines that have 4.3ish headers
but can't, for one reason or another, use gnu ld. There's lots of
#ifdefs in collect.c for this case. Thus, a single common tool handles
the problems with out modification of the cc1plus itself.