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: Martin Wolters Organization: Coding Technologies To: Subject: Re: GCC-3.2 problem: undefined ___gxx_personality_v0 Date: Wed, 5 Mar 2003 17:30:58 +0100 User-Agent: KMail/1.5 References: <157240-22003335151848272 AT M2W097 DOT mail2web DOT com> <200303051712 DOT 22830 DOT wol AT codingtechnologies DOT com> <007801c2e332$ee841a20$78d96f83 AT pomello> In-Reply-To: <007801c2e332$ee841a20$78d96f83@pomello> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200303051730.58213.wol@codingtechnologies.com> On Wednesday 05 March 2003 17:19, Max Bowsher wrote: > Martin Wolters wrote: > > On Wednesday 05 March 2003 16:18, lhall AT pop DOT ma DOT ultranet DOT com wrote: > >> OK. And that file contains only C code? > > > > That's a good question. I thought so and I still think so. However, I > > just tried "g++ myCFile.c" and it compiles like a charm!! > > > > Well, maybe I can find the code that breaks the gcc-build. And if it > > turns out to be a valid c-construct I'll send the requested > > informationen. But for now I at least have a "workaround". > > foo.C means C++. Could your file extension be uppercase accidentally? Now that is interesting and it actually is the cause of all troubles. My file is really called "MYCFILE.C". Renaming it (mycfile.c) and then using gcc mycfile.c works perfectly. I didn't now the upper-case C rule. Is that gcc-specific? Anyhow, thanks so much. -M -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/