Date: Thu, 17 Jun 1999 10:56:21 +0300 (WET)
From: Andris Pavenis <pavenis AT ieva01 DOT lanet DOT lv>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc: Sanda AT 97 DOT gyarab DOT cz, djgpp AT delorie DOT com
Subject: Re: iostream.cc
In-Reply-To: <Pine.SUN.3.91.990617101715.22717E-100000@is>
Message-ID: <Pine.A41.4.05.9906171053580.76382-100000@ieva01.lanet.lv>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk



On Thu, 17 Jun 1999, Eli Zaretskii wrote:

> 
> On Wed, 16 Jun 1999 Sanda AT 97 DOT gyarab DOT cz wrote:
> 
> > When i trace my cc programs, rhide gdb wants to trace into c++ 
> > library, natably all cout and such operations. For this I need 
> > iostream.cc which is nowhere to be found.
> 
> The sources of the C++ libraries are in v2gnu/lgp2811s.zip, available
> from the same place you get DJGPP.  However, not that, to debug
> library code, you will need to rebuild the libraries with debug info,
> which might not be a simple task.

One related question. Should I build C++ libraries (libstdcxx.a and
libgpp.a) for upcomming gcc-2.95 with debug info (the size of each library
will grow approximatelly to 1.5-1.7Mb)

Andris