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
Message-ID:	<3D7687DD.A51BFF0C@t-online.de>
Date:	Thu, 05 Sep 2002 00:23:25 +0200
From:	Andreas DOT Hadler AT t-online DOT de (Andreas Hadler)
X-Accept-Language:	en
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: NTVDM error
References:	<3D767411 DOT CE1BDB47 AT t-online DOT de> <20020904211855 DOT GA7950 AT redhat DOT com>
X-Sender:	051392936-0001 AT t-dialin DOT net

Christopher Faylor wrote:
> 
> On Wed, Sep 04, 2002 at 10:58:57PM +0200, Andreas Hadler wrote:
> >I've seen the problem of NTVDM-error messages on W2k, generated while
> >e.g. building cross-compilers (powerpc-eabi in my case), sometimes asked
> >and answered in the archives, but I've never seen any confirmation, that
> >e.g. replacing symlinks with direct copies is the ultimate remedy.
> 
> "the problem of NTVDM-error messages"?
> 
> You're working under an apparent misapprehension that there is a known
> problem with symlinks and cygwin.  That is not the case.
> 

There was no offense intended.

I get two (exactly) NTVDM illegal instruction boxes when building an
powerpc-eabi crosscompiler, hosted on cygwin, using a (slightly
modified) script from Bill Gatliff
(http://crossgcc.billgatliff.com/build-crossgcc.sh).

The first one occurs when "checking for ANSI C header files..." during
"Configuring in powerpc-eabi/libiberty" for the full blown gcc. It seems
to be independent of the source version and independent of my installed
compiler version (if the build process comes as far).

I've seen the problem of NTVDM errors reported more than one time in
this list. The most reasonable explanation seems to be the (undesired)
execution of some non-executable code, like as trying to execute
symlinks, as some posters suggested. So before digging deeper, my
intention was to get result reports, e.g. from previos OPs.

I am in no way under the apprehension that this is a (well) known
problem, neither with symlinks, nor with cygwin - au contraire, it seems
to happen in just some not well analysed cases (mostly because of the
OPs not reporting). If I'm able to help with my observation I'm glad to
do so. But please bear with me - concerning cygwin, i'm just a dumb
user, loving to have the unix tools handy on my windoze box.

Kind regards
   Andreas Hadler

-- 
Light travels faster than sound. This is why some people appear bright
until you hear them speak

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

- Raw text -