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: Mon, 6 Jan 2003 13:47:58 -0500
From: Christopher Faylor <cgf-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: gcj and -mno-cygwin
Message-ID: <20030106184758.GM25858@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <3E19B8FE DOT 304 AT decodon DOT com> <20030106173525 DOT GA27737 AT redhat DOT com> <3E19C176 DOT 4050009 AT decodon DOT com> <3E19CC2E DOT 5000506 AT lapo DOT it>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3E19CC2E.5000506@lapo.it>
User-Agent: Mutt/1.5.1i

On Mon, Jan 06, 2003 at 07:34:22PM +0100, Lapo Luchini wrote:
>Frank-Michael Moser wrote:
>>Are there plans to implement -mno-cygwin for gcj?
>
>cygwin and no-cygwin are quite different platform, gcj would need to be
>ported "twice" in pratice and, of course, cygwin is closer to original
>linux's gcj.  Though I've just seen a "gcj release candidate" on
>http://www.mingw.org/ and AFAIK mingw is not-so-different from
>no-cygwin.

Cygwin uses a lot of mingw's infrastructure for -mno-cygwin, however, I
don't believe gcj was available when I packaged gcc and gcc-mingw.
gcc-mingw is just a minor repackaging of the offerings from mingw so a
gcj-mingw would be similar.

>They have different meanings but I guess/hope one day they'll converge.

They've already converged for the most part.  Obviously the compilers
are different since the mingw compiler understands only MS-DOS paths
and the cygwin compiler understands UNIX paths but under-the-hood they
should be close to the same thing.  Getting -mno-cygwin working correctly
is tricky though.  It doesn't help that people often think that they can
get around portability problems by doing something like:

gcc -mno-cygwin -I/usr/include foo.c

either.

cgf
--
Please use the resources at cygwin.com rather than sending personal email.
Special for spam email harvesters: send email to aaaspam AT sources DOT redhat DOT com
and be permanently blocked from mailing lists at sources.redhat.com

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