Message-Id: <199803201128.NAA68044@ieva06.lanet.lv>
From: "Andris Pavenis" <pavenis AT laima DOT acad DOT latnet DOT lv>
To: Robert Hoehne <robert DOT hoehne AT gmx DOT net>
Date: Fri, 20 Mar 1998 13:25:15 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Building gcc-2.8.1 for DJGPP
CC: djgpp-workers AT delorie DOT com
In-reply-to: <3511910E.289D4654@gmx.net>
Precedence: bulk

> Date:          Thu, 19 Mar 1998 22:41:34 +0100
> From:          Robert Hoehne <robert DOT hoehne AT gmx DOT net>
> Subject:       Re: Building gcc-2.8.1 for DJGPP

> 
> > Looks that libstdcxx.a generated by gcc-2.8.0 (from archive
> > lgpp280b.zip) is incompatible with gcc-2.8.1:
> 
> That's now really bad. But currently I haven't the time
> to check it.

I did some more testing also with version 2.7.2.1. It looks that
the problem I mentioned characterizes gcc-2.8.0 ONLY (looks 
that object files generated by gcc-2.7.2.1, gcc-2.8.1 and pgcc-2.90.23
are compatible at least in one direction)
Destructor ostrstream::~ostrstream(void) is public symbol also
in library built with gcc-2.7.2.1 (I tested version from distribution).

So the pecularity that this symbol is not made public and also
compiler does not generate references to it is characteristic of 
only gcc-2.8.0. There were at least one more such destructor in
iostream library (I don't remember exactly for which class, but 
even one is too much)

If it is so then perhaps we should get rid of gcc-2.8.0 as quickly as 
possible and change to 2.8.1.

Andris Pavenis