Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!tut.cis.ohio-state.edu!uccba!spca6!kgw2!dennisg
From: dennisg@kgw2.bwi.WEC.COM (Dennis Glatting)
Newsgroups: comp.sys.next
Subject: Re: Questions
Message-ID: <423@kgw2.bwi.WEC.COM>
Date: 8 Mar 90 15:48:52 GMT
References: <7866@tank.uchicago.edu>
Reply-To: dennisg@kgw2.UMD.EDU (Dennis Glatting)
Organization: Xetron Corporation, Cincinnati, Ohio
Lines: 32

In article <7866@tank.uchicago.edu> phd_ivo@gsbacd.uchicago.edu writes:
>
>Did anybody ever succeed in porting G++ to the NeXT?
>
>/ivo	ivo@next.agsm.ucla.edu

yes, i did.  
go ahead and compile everything.  don't compile ld++.  trick make into
thinking it is made.  ld++ is where the problem is.

you need to get a piece of software called NeXTgather.  you get it from me.
it may be included in the next release of g++.  the company i work for is
donating it to the FSF.  i've seen the paper work.

NeXTgather is much like collect.c and collect2.c.  it gathers the 
constructors/destructors which is the vital function that ld++ does;
otherwise, ld++ is the same ad ld.  not that the ld on the NeXT is GNU ld
so you're 95% done.

i've ran several of the test suites with g++ on the NeXT.  they worked.
the ones that didn't work are the ones that are currently being complained
about in gnu.g++.bug.

oh, i almost forgot.  cpp from cccp.c (the c preprocessor from gcc) needs
to be modified to handle the #import statement.  the stuff in /usr/include
is littered with them.  however you should be able to use the cpp that
comes with the NeXT.


--
 dennisg@kgw2.bwi.WEC.COM   | Dennis P. Glatting
 ..!uunet!tron!kgw2!dennisg |