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
Date:	Sun, 9 Feb 2003 18:37:14 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Problems compiling trivial C program.
Message-ID:	<20030209233714.GB30989@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20030207151106 DOT GC5098 AT redhat DOT com> <LPEHIHGCJOAIPFLADJAHOEMEDEAA DOT chris AT atomice DOT net>
Mime-Version:	1.0
In-Reply-To:	<LPEHIHGCJOAIPFLADJAHOEMEDEAA.chris@atomice.net>
User-Agent:	Mutt/1.5.1i

On Sun, Feb 09, 2003 at 10:46:25PM -0000, Chris January wrote:
>> >I'm having trouble compiling this test program:
>> >
>> >void f(){}
>> >
>> >using the command line:
>> >gcc test.c -c -o test.o
>> >
>> >using 1.3.19 or latest Cygwin snapshot (2003-Feb-07) (same error with
>> >both) and gcc-3.2-3.
>> >
>> >The error I see is:
>> >
>> >16 bit MS-DOS Subsystem
>> >/usr/src/cygwin-cvs/obj
>> >The NTVDM CPU has encountered an illegal instruction.
>> >CS:0000 IP:0077 OP:f0 37 05 0e 02 Choose 'Close' to terminate the
>> >application.
>> >Close | Ignore
>> >
>> >AFAICT the command that is failing is:
>> >/usr/lib/gcc-lib/i686-pc-cygwin/3.2/../../../../i686-pc-cygwin/bi
>> n/as.exe,
>> >P:\ccj00\cygwin\usr\i686-pc-cygwin\bin\as.exe --traditional-format -o
>> >test.o /cygdrive/c/DOCUME~1/ccj00/LOCALS~1/Temp/cc50BUPU.s
>> >See the following strace portion:
>> >39542 4773296 [main] gcc 1428 spawn_guts: 1428 = spawn_guts
>> >(/usr/lib/gcc-lib/i686-pc-cygwin/3.2/../../../../i686-pc-cygwin/b
>> in/as.exe,
>>
>>    ^^^^^^
>>
>> Sounds like a corrupted symlink.
>Apologies if mails on this are sporadic, but I can only test this at
>college. Would reinstalling gcc solve the corrupted symlink problem as I
>have already tried that and I still get the same error. A process is
>actually being spawned (the as.exe process) so it doesn't sound like the
>symlinks are corrupted.

Why would you say that?  Of course a process is being spawned.  You're
getting an error as a result.  The theory is that the symlink is not
being interpreted as a symlink or it is pointing to the wrong thing.
I don't know why.

>Do you (Chris) or anyone else have any good tips I can use to debug this?

ls -l /usr/lib/gcc-lib/i686-pc-cygwin/3.2/../../../../i686-pc-cygwin/bin/as.exe

should result in something like:

lrwxrwxrwx  1 foo  bar    26 Nov 19 01:57 /usr/lib/gcc-lib/i686-pc-cygwin/3.2/../../../../i686-pc-cygwin/bin/as.exe -> /usr/bin/as.exe

cgf

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