Date: Sat, 15 Jun 2002 10:56:17 +0300 (WET)
From: Andris Pavenis <pavenis AT lanet DOT lv>
X-Sender: pavenis AT ieva06
To: "Rafal 'Raf256' Maj" <rafal AT raf256 DOT com>
Cc: djgpp AT delorie DOT com
Subject: Re: gcc problems
In-Reply-To: <Xns922DB2D13F854raf256com@213.180.128.20>
Message-ID: <Pine.A41.4.05.10206151049410.9930-100000@ieva06>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk



On 14 Jun 2002, Rafal 'Raf256' Maj wrote:

> HI,
> after all - what should I exacly do to compile program under RHIDE using 
> gcc 3.1 - due to problem with <iostream> ?
> How can I in RHIDE "link libm.a after libstdcxx.a" ?

Specify both stdcxx and m in this order. RHIDE links libstdcxx.a
automatically for C++, but You can specify it once more.

> Btw. has someone other noticed problem with gcc 3.02 (or 2.9x) with writing 
> long files using <fstream> ? i fiel was over ~5-10 kB, then trash started 
> to show on file instead of data, it looked like problme with buffering 
> stream.

It was gcc-3.0.2 and gcc-3.0.3 before it was rerelead in March due to
this bug. Unfortunatelly no one reported it and I had to notice it myself
to fix it. gcc-3.0.4 is Ok.

Then it could be fixed earlier, but as I wrote, nobody reported it

Andris