X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: References: <30467239.post@talk.nabble.com> From: =?ISO-8859-1?Q?Fr=E9d=E9ric_Bron?= Date: Wed, 22 Dec 2010 14:13:15 +0100 Message-ID: Subject: Re: mingw-targeted cross-compiler question To: cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com >>> I checked the Make file, it used this flag: >>> gcc -mno-cygwin -g -Wl,--add-stdcall-alias -Wl,--export-all-symbols ... >> >> replace gcc by gcc-3 >> gcc 4 is now the default on cygwin but the cross compiler is not >> supported for that version. >> Fr=E9d=E9ric > > What do you mean by not supported? =A0JonY maintains the cross compilers.= ... I meant that i686-w64-mingw32-gcc exists but not i686-w32-mingw32-gcc. I thought that w64 meant "built on win64" and mingw32 "run binary on win32". So it seems to me that with cygwin running on a 32 bit windows, it is not possible to cross compile to win32. However with a 64 bit windows you can produce win32 applications. However, I just tried to use i686-w64-mingw32-g++ on my win32 machine with a hello world program and it produces an binary that can be used from windows on that win32 machine. So my question to the list: what is the meaning of w64 in the name? Fr=E9d=E9ric -- 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