Original Message
>From: Brian K. Whatcott
>Sent: 28 March 2005 17:52
> I am forwarding this reply and the simpler example on to the mailing list.
> The attached files are:
>
> hello.cc- Hello world that writes to a file, instead
> of cout.
> command.txt
At 02:15 AM 3/26/2005, you wrote:
> Tim,
>
>I did install the gcc C compiler. What switches need to be set with
>cygcheck? I'll run it and forward the results.
See:
>Problem reports: http://cygwin.com/problems.html
--
Larry Hall http://www.rfk.com
RFK Par
ECTED]
-Original Message-
From: Tim Prince [mailto:[EMAIL PROTECTED]
Sent: Friday, March 25, 2005 6:34 PM
To: Brian K. Whatcott; cygwin@cygwin.com
Subject: Re: Errors in #include files when compiling a Legacy C++
Application
At 03:19 PM 3/25/2005, Brian K. Whatcott wrote:
>I am confused, bec
At 03:19 PM 3/25/2005, Brian K. Whatcott wrote:
I am confused, because the two flavors of SuSe use g++ 3.2 and 3.3.4, and
there wasn't a big problem going from 3.2 to 3.3.4. Since Cygwin uses g++
3.3.3, I would think that the code that works on 3.3.4 (SuSe 9.1) would be a
no brainer. I think the
Hi!
Our legacy C++ application was written on SGI IRIX using older compiler
features. Last year, we ported it to SuSe Linux (both 8.2 and 9.1). We
have had a few challenges, but nothing big. Recently, I have been asked to
get the application to run on MS-Windows, with very little time. I looke
5 matches
Mail list logo
