Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Wed, 5 Mar 2003 11:35:10 -0500 (EST)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Martin Wolters <wol AT codingtechnologies DOT com>
cc: cygwin AT cygwin DOT com
Subject: Re: GCC-3.2 problem: undefined ___gxx_personality_v0
In-Reply-To: <200303051730.58213.wol@codingtechnologies.com>
Message-ID: <Pine.GSO.4.44.0303051133530.25599-100000@slinky.cs.nyu.edu>
Importance: Normal
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 5 Mar 2003, Martin Wolters wrote:

> 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

Martin,

To avoid this kind of trouble in the future, add "check_case:strict" to
your CYGWIN environment variable.  This will verify that the case you're
using to access the file is the actual case of the filename.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!
  -- /usr/games/fortune


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