Path: utzoo!utgpu!watmath!uunet!tut.cis.ohio-state.edu!cs.utexas.edu!uwm.edu!uakari.primate.wisc.edu!samsung!usc!orion.oac.uci.edu!uci-ics!rfg
From: rfg@ics.uci.edu (Ron Guilmette)
Newsgroups: gnu.g++
Subject: Re: Please describe how to use g++/gdb with COFF
Message-ID: <1989Oct27.192234.24792@paris.ics.uci.edu>
Date: 28 Oct 89 02:22:34 GMT
References: <8910212151.AA26599@lurch.Stanford.EDU> <20941.625010978@ics.uci.edu> <13058@boulder.Colorado.EDU>
Reply-To: Ron Guilmette <rfg@ics.uci.edu>
Distribution: gnu
Organization: University of California, Irvine - Dept of ICS
Lines: 27

In article <13058@boulder.Colorado.EDU> grunwald@foobar.colorado.edu writes:
>
>Ron asks ``are there other alternatives that I didn't mention'' & the
>answer is `yes'.
>
>Namely, collect & native assembler/linker. In this combination, you...

>The advantages of this over e.g., using the COFF link directives file
>is that it's more portable.
         ^^^^^^^^^^^^^^^^^^

You have been saying this for a long time, Dirk, but what evidence do you
base this opinion on?

>You can use the same mechanism on the MIPS
>assembler/linker, where it's not clear if you *have* linker files
                         ^^^^^^^^^^^^^^
>(ifiles, I think they're called).

That's a rather non-commitial statement if I ever heard one!  You have got one
of the PMAX beasts don't you, Dirk?   So look in the manual and tell us the
whole true story.  Do these things that use MIPS chips support COFF extra
sections or don't they?  Do they support "ifiles" or don't they?

Inquiring minds want to know!

// rfg