Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dave Korn" To: Subject: RE: New Cygwin installation Date: Wed, 17 Mar 2004 18:33:56 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In-Reply-To: <30979.1079541782@www45.gmx.net> Message-ID: X-OriginalArrivalTime: 17 Mar 2004 18:33:56.0984 (UTC) FILETIME=[68496780:01C40C4E] > -----Original Message----- > From: Frank Wagner > Sent: 17 March 2004 16:43 > Hi Dave, Hi Frank! > first thanks for your fast reply. > I replaced the #include with #include > but the type ostrstream type is still unknown. That's not surprsing. It's not what either I or the compiler were telling you to do: we only said you should change #include to if there was one, didn't say anything about at all. #include is correct - note that it doesn't end in ".h". > So must I throw away all my old books about C++ or what can I > do to compile my older programs like they are? No! The first thing you should have tried was removing the incorrect include directory search paths from your dev-cpp setup! That was the main point of my last email and I think it's the most likely source of the problem. You seem to be suggesting that you haven't tried it yet, but it's really the first thing you should have tried. Your code is almost certainly correct and should continue to compile in the ordinary fashion once you have sorted out the bad -I options you're using Dev-Cpp to pass to g++.exe. Get rid of them! cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/