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
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <04f201c19bc0$307a1da0$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Jon Leichter" <jonleichter AT mediaone DOT net>, <earnie_boyd AT yahoo DOT com>
Cc: <hschwentner AT yahoo DOT com>, <cygwin AT cygwin DOT com>
References: <CIENIMJIOHKBPJEFFFOBIEIJCBAA DOT jonleichter AT mediaone DOT net>
Subject: Re: Compiling apps to Mingw32 with cygwin
Date: Sun, 13 Jan 2002 10:23:48 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-OriginalArrivalTime: 12 Jan 2002 23:23:43.0656 (UTC) FILETIME=[2D25C280:01C19BC0]


===
----- Original Message -----
From: "Jon Leichter" <jonleichter AT mediaone DOT net>

>
> Earnie and Robert,
>
> I'm a bit confused when I consider the commentary that you both have
> contributed on this topic. Here's what I have assessed. You two guys
correct
> me where I'm wrong.
>
> ===
>
> Robert has implied that using GCC with -mno-cygwin is virtually a
> cross-compile and should be treated as such. An up-to-date and well
written
> configure script would require that the user have i686-pc-mingw32-gcc
(which
> as a script or a binary invokes gcc -mno-cygwin). He would not
necessarily
> need to symlink other binutils to i686-pc-mingw32-<tool> because the
> configure script would find the build (Cygwin) tools after checking
for the
> host tools. He would invoke configure with the following:

Reread the thread. I indicated you should have those symlinks. It *may
work* without them, that is different from what *I would do*.

> Earnie. Your comments seem to contradict each other. In your last
email, it
> seems you are implying that "gcc -mno-cygwin" is NOT a cross-compile.
And
> then you went on to explain how I could safely use the switches if I
set
> symlinks to emulate a cross-compile. Which point of view do you
support
> Earnie?

gcc -mno-cygwin isn't a cross compile. It links with a different libc,
and puts different headers in the search path - that's all. It *also*
happens to meet the criteria for a cross compile in that
1) cygwin gcc accepts / and \ paths
2) the mingw libraries are present and the file format is understood.
3) The resulting binaries are compatible with the platform.

This is more of an accident than plan :}

Rob


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