Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
X-Authentication-Warning: hp2.xraylith.wisc.edu: khan owned process doing -bs
Date: Fri, 9 Mar 2001 22:21:13 -0600 (CST)
From: Mumit Khan <khan AT NanoTech DOT Wisc DOT EDU>
To: John Andrews <john AT triscend DOT com>
cc: cygwin AT cygwin DOT com
Subject: RE: cross compiler for Cygwin
In-Reply-To: <2407239113CD914CBA855A47698F01B0F53E@SUGAH2.triscend.com>
Message-ID: <Pine.HPP.3.96.1010309221520.14734B-100000@hp2.xraylith.wisc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 9 Mar 2001, John Andrews wrote:

> Well now that you've offered Mumit... 8-)

That's why I wrote up a few howto's in the past, and the latest one is
cygwin->linux. See http://www.nanotech.wisc.edu/~khan/software/gnu-win32/
for details.

The trouble, as you've found out, is that various targets use different
gcc versions (or patches to it), and it gets trickier to build. The only
gcc that will build without tweaking is the gcc distributed by Cygwin
team, but that may not have some of the patches that your target may
require. And this is where the vendors for these embedded systems can
do a lot of good, but of course support costs real money. Then again, so
does time.

[ steps in building look good. However ... ]
> #12) make gcc with:
> make -w all-gcc LANGUAGES="c" 2>&1 | tee make.out
> 
> And that brings us full circle to where I was when I posted my first message
> a couple of days ago. The make dies with the following error message:

> ---tail of gcc make.out---
> gcc -DCROSS_COMPILE -DIN_GCC     -g -O2  -DHAVE_CONFIG_H    -I.
> -I/usr/src/gcc-2
> .95.2/gcc -I/usr/src/gcc-2.95.2/gcc/config
> -I/usr/src/gcc-2.95.2/gcc/../include
> \
> -DPREFIX=\"/usr/arm-uClinux\" \
>   -c `echo /usr/src/gcc-2.95.2/gcc/prefix.c | sed 's,^\./,,'`
> In file included from /usr/include/w32api/windef.h:143,
>                  from /usr/include/w32api/windows.h:96,
>                  from /usr/src/gcc-2.95.2/gcc/prefix.c:69:
> /usr/include/w32api/winnt.h:2266: two or more data types in declaration of
> `type
>  name'

This is where debugging comes in. Here's what you do:
  
  $ make all-gcc LANGUAGES="c" CFLAGS=-save-temps

and look at prefix.i file and see what gives. And then you'll get to the
next problem, and the same applies, and so on. Fun, isn't it?

Regards,
Mumit



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple