Re: [PATCH] 2nd patch Re: [Jade/OpenJade] g++ 2.95 C++ portabilit y problems

Subject: Re: [PATCH] 2nd patch Re: [Jade/OpenJade] g++ 2.95 C++ portabilit y problems
From: Adam Di Carlo <adam@xxxxxxxxxxx>
Date: 16 Aug 1999 20:23:40 -0400
Matthias Clasen <clasen@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> writes:

> > I'm no gcc expert, but looking at the docs I see a -frepo flag which seems
> > to allow you to get rid of the _inst files completely. Surely that would be
> > better? Or is there a catch?

That would be better, if it works.  Are the _inst files used in
Windows are other places, such as the Sun C++ compiler?

> I don't know. I want to test this soon. The only thing to keep in mind
> is that you have to change include/config.h to not define SP_MANUAL_INST
> for gcc anymore. 

Well, g++ for 2.95 or better, I would suppose.

> And you have to remove -fno-implicit-templates from
> CXXFLAGS in Makefile.comm.

Yeah, add -fpermissive for GCC while we're at it, and -frepo.

--
.....Adam Di Carlo....adam@xxxxxxxxxxxxxxxx<URL:http://www.onShore.com/>


 DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist


Current Thread