Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id: <200001121743.LAA03815@hp2.xraylith.wisc.edu>
To: Egor Duda <deo AT logos-m DOT ru>
cc: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: problem with cross-gcc 2.95.2 
In-reply-to: Your message of "Wed, 12 Jan 2000 17:08:42 +0300."
             <9714 DOT 000112 AT logos-m DOT ru> 
Date: Wed, 12 Jan 2000 11:43:16 -0600
From: Mumit Khan <khan AT NanoTech DOT Wisc DOT EDU>

Egor Duda <deo AT logos-m DOT ru> writes:
> 
>   I've compiled gcc-2.95.2 with binutils-19991221 with --host=i586-pc-linux-g
> nu
> --target=i586-pc-cygwin and encountered a problem. i586-pc-cygwin-ld
> seems to generate incorrect executable. i've compiled
> #include <stdio.h>
> main()
> { printf("123"); }

If you search this list and binutils list, you'll see previous posting (by
others and I) that binutils sourceware tree is unstable for pe-i386, and
you need to roll back to a much earlier tree to usable one.

Essentially, anything past 1999-09-11 won't work at all, and anything after
1999-08-l9 or so may have problems when you strip DLLs.

You may want to try my last snapshot, based on 1999-08-18 + local patches:

ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/snapshots/binutils-19990818/

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com