Date: Wed, 31 Jul 1996 08:17:26 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Douglas Rupp <drupp AT cs DOT washington DOT edu>
Cc: DJ Delorie <dj AT delorie DOT com>, drupp AT cs DOT washington DOT edu,
        djgpp-workers AT delorie DOT com
Subject: Re: gcc -g -o
In-Reply-To: <199607301736.KAA15461@june.cs.washington.edu>
Message-Id: <Pine.SUN.3.91.960731081533.1793E-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Tue, 30 Jul 1996, Douglas Rupp wrote:

> > > How about making it do something useful, like w/o -g the .exe file will
> > > be stripped and the coff file deleted after linking.
> > 
> > This would make djgpp operate differently than unix gcc, which does no
> > such thing.  Besides, if you specify the .exe file as the output file,
> > the coff file is already deleted.
> > 
> 
> I not sure quite what you mean by "does no such thing", if you mean that
> the unix gcc doesn't delete its coff file after linking then I suppose
> you're right :-)

On Unix, gcc without -g does NOT strip the binary.  If ours will, that 
would be a deviation from the normal behavior, which might bite you if 
you use Makefiles that come from Unix.