This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Errors in #include files when compiling a Legacy C++ Application


Wayne,

I must admit, I read that page quickly, and saw the parts about giving a
complete explanation, but missed the part about how to do cycheck.  I am
sorry for the omission.  I have created a much simpler example (a version of
the proverbial "hello world" program).  Since the problem is in the compile,
the errors were basically the same.

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		- The compile command.
	hello_errors.txt	- File with the errors from the compile.
	cygcheck.out	- The cycheck output file.

All files are straight text (probably with Unix/Linux end of lines).

Thank you for taking the time to answer my email, and pointing out how I
could better state my problem.  Also, thanks in advance to anyone how can
help me solve this.


Brian K. Whatcott
Senior Software and Systems Engineer
Millennium Engineering Integration
(719) 264-4310, FAX (719) 264-4318
(719) 331-5100 (Cell)
bwhatcott@meicompany.com 
-----Original Message-----
From: Wayne [mailto:dockeen@mchsi.com] 
Sent: Saturday, March 26, 2005 8:32 AM
To: bwhatcott@meicompany.com
Subject: Re: Errors in #include files when compiling a Legacy C++
Application


According to this:
http://cygwin.com/problems.html

You should:

"Run cygcheck -s -v -r > cygcheck.out and include that file as an attachment
in your report. Please do not compress or otherwise encode the output. Just
attach it as a straight text file so that it can be easily viewed."

Note they do want it attached, not directly included in the posting.

It also would probably help if you would include

(1) A simple as possible example program that shows the effect

(2) The command line you are using to compile it

(3) The first few errors generated

Wayne Keen

p.s. I noted you worked for MEI, thats why I sent this.

Attachment: hello_errors.txt
Description: Text document

Attachment: hello.cc
Description: Binary data

Attachment: command.txt
Description: Text document

Attachment: cygcheck.out
Description: Binary data

--
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/

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]