[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-dejagnu] Re: Compiling Using gcc 3.0

From: Jeffrey Oldham
Subject: [Bug-dejagnu] Re: Compiling Using gcc 3.0
Date: Mon, 28 May 2001 15:00:48 -0700
User-agent: Mutt/1.2.5i

On Mon, May 28, 2001 at 07:43:18AM -0600, Rob Savoye wrote:
> On Sun, May 27, 2001 at 08:51:12PM -0700, Jeffrey Oldham wrote:
> > To compile today's (27May) dejagnu using gcc 3.0 (as of 22May) on
> > i686-pc-linux-gnu, I had to modify the source code ala the attached
> > patch.  I have not yet confirmed the resulting code actually works
> > correctly.
>   It's close, but not quite. This compiles, it just doesn't execute
> correctly! :-) For some reason, (I'm still coming up to speed on
> libstdc++-v3) changing from an ostrstream to a ostringstream stops
> outputting the test state completely.
>   All this function does is let me do a:
>       std::cout << testout(FAILED) << std::endl
>   where FAILED is an index into an array, and testout() prints the
> string with that entry. You can see if this works or not by trying
> the unit.cc test case in testsuite/libdejagnu/.

I do not know how to fix the execution problem.  For my gcc 3.0
(~May22), the problem seems to be trying to change cout's stream
buffer.  If the debugger is not lying, unit.cc's putsetbuf() is
invoking std_streambuf's setbuf(), which does nothing.  I do not like
the design choice, but the published interface makes changing it
beyond my ability to think of another approach.

Jeffrey D. Oldham

reply via email to

[Prev in Thread] Current Thread [Next in Thread]