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:	<3D77AE65.94BA61A9@t-online.de>
Date:	Thu, 05 Sep 2002 21:20:05 +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'" <cygwin AT cygwin DOT com>
Subject:	Re: NTVDM error - summary
References:	<3D848382FB72E249812901444C6BDB1D0BA967 AT exchange DOT timesys DOT com>
X-Sender:	051392936-0001 AT t-dialin DOT net

High,

I've encountered NTVDM illegal instruction message boxes when building
an powerpc-eabi crosscompiler during "checking for ANSI C header
files..." while "Configuring in powerpc-eabi/libiberty" for the full
blown gcc.

Samrobb thankworthy pointed me to

 http://sources.redhat.com/ml/crossgcc/2002-01/msg00067.html

I used the second tip of this message, and changed the value of cmdline
under the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WOW in
the registry to something slightly different, just to avoid NT starting
NTVDM, with regtool.

This cured the symptom. The build runs smooth and flawless. The
resulting gcc seems to be identical to the one generated with the NTVDM
message boxes, except of timestamping etc.

Hope, this helps.

Kind regards,
   Andreas Hadler

-- 
The sooner you get behind, the more time you'll have to catch up.

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