Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com From: "Dave Korn" To: Subject: RE: file not recognized:File format not recognized Date: Thu, 10 Jun 2004 17:04:12 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit In-Reply-To: <20040610152123.76705.qmail@web16804.mail.tpe.yahoo.com> Message-ID: X-OriginalArrivalTime: 10 Jun 2004 16:04:12.0781 (UTC) FILETIME=[926591D0:01C44F04] > -----Original Message----- > From: cygwin-owner On Behalf Of c dana > Sent: 10 June 2004 16:21 > --- Igor Pechtchanski 的訊息：> ^^^^^^^^^^^^^^^^^^^^^^^ Hey Dana, check this link -> > You're right.I was not not telling the truth when I > posted the previous message. I compiled successfully > now. > "@gcc test.txt" does not work. > "@gcc test.c" works. FYI, gcc normally works out what language a file contains by looking at the extension, so when it ends in .txt it can't guess what language it's in. But you can always tell it specifically: if you use the command line option "-x c" to tell gcc that the file was a C file then it would still work, i.e. "@gcc -x c test.txt" 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/