Date: Fri, 15 Aug 1997 11:51:32 +0200 (MET DST)
From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Subject: Re: gxx ?s / 2.7.2.3 ?s
In-reply-to: <199708142311.AA188050311@typhoon.rose.hp.com>
To: Andrew Crabtree <andrewc AT typhoon DOT rose DOT hp DOT com>
Cc: djgpp-workers AT delorie DOT com
Message-id: <Pine.LNX.3.91.970815114510.1657D-100000@acp3bf>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Content-transfer-encoding: 7BIT
Precedence: bulk

> > I'm not subscribed so CC responses please.  Could someone explain 
> > how the gxx that comes in the C++ compiler works?  My assumption 
> > is that it is just a wrapper program that calls gcc.  

Yes. Its sources are in djlsr, in directory src/utils, if memory serves. 

> > Is that 
> > correct?  The reason I ask is that I have received bug reports regarding
> > gxx from the latest pcg snapshots.  

??? Does that mean you have a 'gxx.exe' in those snapshots? If so, it's
probably a bad idea to include it at all. But I may be wrong here.

> > If I add a [gxx] section to the 
> > djgpp.env file that is the same as the one for [gcc] everything works 
> > OK.  My simple test case for the theory was 'gxx -v -c hello.c' (this
> > is with the [gxx] change to djgpp.env)

This sure looks as if you actually use a gxx build by the gcc sources,
i.e. the equivalent of the unix 'g++' binary. That's really not too
good an idea, I suspect. The 'gxx' of DJGPP is a specialised product,
and you shouldn't substitute the Unix-borne g++ for it.

> > Although primarily for linux/glibc fixes they also were accepting
> > general bug fixes.  Since there has been a lot of questions on djgpp
> > list about debugging .cpp files or using -gstabs it may be worthwile
> > to submit that to HJ Lu and roll another 'official' DJGPP gcc release.

This probably means: "Robert and/or DJ: hurry to submit any patches you
have sitting on your shelves to the FSF." 

HBB