Date: Tue, 7 Feb 2012 13:19:51 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Documentation on -mno-cygwin Accuracy
Message-ID: <20120207181951.GB22372@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <CAGJFqDVGy9pMbpYizQhX3qZCRzALS9r9N=RbL6FQbHwrAdkR7A@mail.gmail.com> <1328569526.8848.3.camel@YAAKOV04> <jgrik0$6k3$1@dough.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <jgrik0$6k3$1@dough.gmane.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Tue, Feb 07, 2012 at 10:13:49AM -0600, carolus wrote:
>On 2/6/2012 5:05 PM, Yaakov (Cygwin/X) wrote:
>>The -mno-cygwin flag is still handled by gcc3, but that is deprecated
>>and may be removed at any time.  The officially supported way to build
>>such apps is to use the appropriate mingw or mingw64 cross-compiler.
>>
>Is there an easy procedure that is equivalent to the old -mno-cygwin
>(suitable for a dumb engineer who is not a programmer and knows nothing
>about cross-compilation)?  -mno-cygwin was a very handy way to
>distribute a cygwin fortran executable to non-cywin users without
>having to include cygwin1.dll (which I think is not exactly legal).

A cygwin fortran executable would need cygwin1.dll.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple