X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-4.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<6BFA9AF2C7556E42AFF3F187ECAB07B802F9D004@bespdc01.mediaxim.local>
References:	<6BFA9AF2C7556E42AFF3F187ECAB07B802F9CFD0 AT bespdc01 DOT mediaxim DOT local> <CA+sc5m=cKU5DaZFeJuEas-nfXD9uAsxq4V_9hcoUAM77u3OKNA AT mail DOT gmail DOT com> <6BFA9AF2C7556E42AFF3F187ECAB07B802F9CFEF AT bespdc01 DOT mediaxim DOT local> <CA+sc5m=mC16bBFTBpPACoewcxKWt4KSsH22mUiVu0BrYCVObyQ AT mail DOT gmail DOT com> <6BFA9AF2C7556E42AFF3F187ECAB07B802F9D004 AT bespdc01 DOT mediaxim DOT local>
Date:	Mon, 23 Apr 2012 16:04:01 +0200
Message-ID:	<CAEhDDbA2j21rL5PNw+ni2X_kXErjquZUtCUwK8zZTqT9hK3ijQ@mail.gmail.com>
Subject:	Re: Building for nocygwin
From:	Csaba Raduly <rcsaba AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id q3NE4R0j021642

Hi,

On Mon, Apr 23, 2012 at 3:56 PM, Michel Bardiaux  wrote:
> [snip]
>
>> That is the "general solution".  The error message was appropriate and gave a clue.  Beyond that
>> you'll need to communicate a patch to the maintainers of the package that is still using -mno-cygwin.
>
> Let me rephrase.
>
> gcc-3 -mno-cygwin -o foo.exe foo.c
>
> under cygwin, works to create a windows executable that does not reference the cygwin dlls. (provided of course that foo.c does not call any APIs that can only be provided by cygwin, like fork). That *was* a general solution.
>
> What is the equivalent using gcc-4 under cygwin?
>

i686-pc-mingw32-gcc -o foo.exe foo.c

Csaba
-- 
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real numbers.
Life is complex, with real and imaginary parts.
"Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds
"People disagree with me. I just ignore them." -- Linus Torvalds

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

- Raw text -