X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; q=dns; s=default; b=pq eTks0wQZq9SEmNmZLRGnw3uO0jIg17GC81fKaEitVcv89j4CPiBFW8s9W7tV/MYc IC9HhP32uLkPbVlB3vJATvLVTayEhiWTWsrb6aBn4O5Rqc7qawX1CKj1gARcHmBe 5p1Df131NC8HWErzw19CDNGBdAaOzhw/SDpkRjo34= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; s=default; bh=H77Jd/pq OQ9nrPBLmB8Q/KhsRpg=; b=NsUQ3FP0PIJBoPwNL97nplPuC1h3FN1XFCTRDKGe CiMgcVNQo83xWRykp6ssOs1ZLfqaSapJkgNqy5aKg30zEENxlBPpYCqBLpsg2TC9 BzTPIQ3B/nUU5/gR9jyEAvQxC4ekDiiEoLGxfZf32CvpbRRvpJPxBnLZ0IMDszwc Nyk= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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-Spam-SWARE-Status: No, score=-3.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,RDNS_NONE,SPF_PASS autolearn=ham version=3.3.1 MIME-Version: 1.0 X-Received: by 10.229.198.2 with SMTP id em2mr722537qcb.96.1373991909176; Tue, 16 Jul 2013 09:25:09 -0700 (PDT) In-Reply-To: <51E5693E.9090207@cwilson.fastmail.fm> References: <51E54596 DOT 5040400 AT cwilson DOT fastmail DOT fm> <20130716131044 DOT GJ2712 AT calimero DOT vinschen DOT de> <51E5693E DOT 9090207 AT cwilson DOT fastmail DOT fm> Date: Tue, 16 Jul 2013 12:25:09 -0400 Message-ID: Subject: Re: mingw.org cross compiler [Was: problem with cvs binary?] From: Earnie Boyd To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 On Tue, Jul 16, 2013 at 11:39 AM, Charles Wilson wrote: > On 7/16/2013 9:10 AM, Corinna Vinschen wrote: >> >> Are the mingw cross compilers still necessary, now that we have >> modern mingw-w64 toolchains? On Fedora they aren't shipped since >> F17, which already came with mingw-w64 toolchains either. > > > No, in the sense that you could use the mingw-w64 i686 toolchain to generate > 32bit "native" windows apps instead. > > Yes, because the two toolchains are not mutually compatible (different ABI, > different exception model, different threading library, different > w32api/runtime library). If you are using a cygwin $host to develop, > specifically, mingw.org-distribution compatible apps/libs...then you need > the mingw.org cross compiler. > > I don't know how many people that represents -- it might just be me and > Earnie -- but I'm not ready to declare mingw(.org)-gcc dead just yet. I at I'm not actually using mingw-gcc on Cygwin and have no opinion for the offering. > least want to update our current offering to something more current than > 4.5.x, AND it's necessary on i686 because recent gmp/mpfr/mpc library > updates have broken mingw-gcc. If, after this update, we want to declare > EOL on mingw(.org)-gcc, we could discuss that on cygwin-apps. Can you specify what the issues are for gmp/mpfr/mpc? I ask because I'm attempting to build 2.8.1. -- Earnie -- https://sites.google.com/site/earnieboyd -- 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